http://bugs.winehq.org/show_bug.cgi?id=27326
Summary: DiRT 3 fails to launch (exits silently)
Product: Wine
Version: 1.3.21
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nwarrenfl(a)gmail.com
When running DiRT 3 nothing happens and the process quits.
This is the output when running the executable:
wine: Unhandled page fault on read access to 0x00000000 at address (nil)
(thread 0020), starting debugger...
I did a relay log to find the cause but I'm not experienced enough to find it.
The relay log is attached in the hope someone will find the problem.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=20281
Summary: Adobe Photoshop CS4 installer unusable
Product: Wine
Version: 1.1.30
Platform: PC
URL: http://trials.adobe.com/Applications/Photoshop/CS4/Win
/ADBEPHSPCS4_LS1.7z
OS/Version: Linux
Status: NEW
Keywords: download, Installer, regression
Severity: normal
Priority: P2
Component: mshtml
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
CC: jacek(a)codeweavers.com
Created an attachment (id=23956)
--> (http://bugs.winehq.org/attachment.cgi?id=23956)
Screenshot
The Adobe Photoshop CS4 installer is currently unusable, see screenshots for
details.
Probably affects other CS4 installers too, but I have not tested them.
df90f665bb11e2d01ff3e061d6f989ce2589cadb is first bad commit
commit df90f665bb11e2d01ff3e061d6f989ce2589cadb
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Fri Oct 2 13:51:19 2009 +0200
mshtml: Added HTMLAnchorElement dispex data.
:040000 040000 1e962f09f4793df3ac56a123fd68e7d8dc07d33e
07fbe0ed134096e9e663b4722f97f57140bc431a M dlls
To get this far, have to work around Bug 18070.
It appears that all the possible fields are shown at once, and none of them are
accessible.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26423
Summary: Wine should use MS-DOS (8.3) file names when
interacting with Dosbox
Product: Wine
Version: 1.3.15
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: spammis(a)spam.la
This depends on bug 26422.
Let's assume that the current directory is "C:\Program Files"
(~/.wine/drive_c/Program Files). I type "wine dosprog" where "dosprog" is some
MS-DOS program. Wine starts Dosbox and runs the following commands:
mount c /home/username/.wine/dosdevices/c:
mount d /home/username/.wine/dosdevices/d:
C:
cd \Program Files
C:\Program Files\dosprog.exe
exit
Dosbox does not recognise long file names (Program Files); Dosbox requires
short names (PROGRA~1). The "cd" call and the program call will both fail
because of this.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=23334
Summary: SimCity 3000: after install regedit shows
Product: Wine
Version: 1.2-rc4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: felipemoraesbr(a)gmail.com
This is the single game I tested where it happens
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=11239
Summary: Steam Games No Longer Start - bisected the cause to
ntdll
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: philcostin(a)hotmail.com
The following patch, introduced on Jan 15th 2008 has resulted in Steam games
being unable to start.
bd352bcd1c98ed91bdb337e73cddfd8ceac095d6
err:seh:setup_exception nested exception on signal stack in thread 004f eip
7efc20b3 esp 7ffdb770 stack 0x241000-0x350000
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=14390
Summary: Gmax 1.2: Fatal Error on Install - Ended Prematurely.
Product: Wine
Version: 1.1.0
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P1
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gaming4jc2(a)yahoo.com
Created an attachment (id=14701)
--> (http://bugs.winehq.org/attachment.cgi?id=14701)
Fatal Error on install.
When installing GMAX 1.2 on WINE 1.1.0 I receive the following errors which are
attached.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=23675
Summary: Portable Apps Platform (beta 5) works under Vista,
Win7, but not Wine’s emulation
Product: Wine
Version: 1.2-rc7
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: joelcsalomon(a)gmail.com
Portable Apps Platform (beta 5, see <http://portableapps.com/node/24258>) gives
me the error “The program PortableAppsPlatform.exe has encountered a serious
problem and needs to close. We are sorry for the inconvenience.” Telling Wine
to mimic Windows XP for this program avoids the crash, but the Platform runs
fine under (real) Windows Vista & 7.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=18777
Summary: Wine 1.1.22+ resets customized FontLink when switching
locales
Product: Wine
Version: 1.1.22
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: gdi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: matthewsage(a)live.com
CC: Paul.Hampson(a)Pobox.com
Created an attachment (id=21546)
--> (http://bugs.winehq.org/attachment.cgi?id=21546)
Regression test that shows the patch that broke the desired functionality
Whenever you switch locales (using the latest Wine dev. version -1.1.22-),
whatever custom Font Linking you have made in the FontLink/SystemLink register
key will be wiped out.
This was tested on Wine 1.1.22, after wiping out ~/.wine
I tested it with the Ubuntu x86_64 binary package from the budgetdedicated
servers, AND after building from source.
Steps to reproduce:
1) Run "regedit"
2) Set some System Font Linking replacements in the
HKLM/Software/Microsoft/Windows NT/CurrentVersion/FontLink/SystemLink register
key (in my case: Tahoma -> VL Gothic, Microsoft Sans Serif -> VLGothic, MS Sans
Serif -> VL Gothic)
3) Run any Win32 application with LANG set to a different locale (in my case,
LANG=ja_JP.UTF-8)
Expected results:
The application is executed, whatever Font Linking you made is visible (which
means that the custom Font Linking I made is respected by Wine).
Actual Results:
The application is executed, whatever Font Linking you made is not visible. If
you run "regedit" again, you'll see that the FontLink/SystemLink key is now
empty.
Workaround:
Always run Wine apps with the same locale (LANG=ja_JP.UTF-8 in my case) - That
would include regedit itself, so that the Font Linking you set up is not wiped
as soon as you run another app with a different locale.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10273
Summary: satisfy SafeDisc 2.x heuristic API analyzer by
"adjusting" API exports/entry statistics of wine
builtins
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-kernel
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=8924)
--> (http://bugs.winehq.org/attachment.cgi?id=8924)
Patch which should fix SafeDisc 2.x copy protection api analyzer issue
Hello,
if not interested in technical details goto (2) ;-)
I made this a separate bug report like
http://bugs.winehq.org/show_bug.cgi?id=9925 (SafeDisc 1.x stopper) because
SafeDisc has many flavors that differ in various technical ways and can't be
discussed/handled in a single SafeDisc "metabug" like
http://bugs.winehq.org/show_bug.cgi?id=219
SafeDisc Major version based separation allows better tracking of "completion"
state (1.x/2.x/3.x/4.x).
-----------
(1)
It took me a couple of days to get an idea what SafeDisc 2.x really does with
the API exports and to find a way to cope with it...
Various anti-debugging techniques and nasty runtime code obfuscation made this
journey somewhat challenging.
Parts of SafeDisc 2.x analyze the API code of the following system libraries:
kernel32.dll (wine builtin)
user32.dll (wine builtin)
gdi32.dll (wine builtin)
cdasdtst.dll (developer backdoor?)
The latter one is probably a "developer backdoor", used to verify their
code/algorithms (not needed to be present).
For each of these libraries all named exports are taken into account.
A number of API entry opcode sequences are read and used for statistical
analysis (number depends on type of encountered opcodes).
>From what I've seen there is some kind of "behavioural probability" of each API
entry calculated, with typical opcode sequences having a "weighting".
Just think of advanced heuristic detection methods of antivirus scanners and
you get the idea ;-).
Anyway, wine's builtin libraries differ in their signatures from windows entry
code and to make things worse, wine's +relay/+snoop feature heavily interferes
with the analyzer results. :-(
First I made some experiments with additional (dummy) function exports, small
__asm__ wrappers with opcode sequences to see how the distribution of opcodes
influences the analyzer results.
The result was rather disappointing.
I needed a large number of exports to gain some results but not significantly
enough to get below the "bad" threshold.
Then I came across the magic "0" value. As soon as I used this value either as
first .byte on API entry or init value for data export, the entry scan was
short circuited.
This value seemed to have the highest influence of all code/data sequences
used.
I added quite a number of data exports - aliased to initialized "0" value -
safe enough to let even wine's +relay work (remember: relay code influences
analyzer).
If you look at the patch don't get mad ;-)
You will see a crapload of named "__wine_safedisc2" data exports/aliases added
to wine builtin kernel32, user32 and gdi32.
For the record: http://bugs.winehq.org/show_bug.cgi?id=9926 which talks about
"problematic" gdi32 data exports (pfnPalette stuff) in SafeDisc 3.x.
SafeDisc 2.x code triggers SEH upon exported function pointers too but this is
gracefully handled. No harm at all.
I wonder if this is really a problem in SafeDisc 3.x ...
I thought about other possible solutions but found no one easier to implement
to prove my findings without hurting wine too much :-)
Making wrappers of the whole kernel32, user32, gdi32 named exports API just to
please the entry analyzer is not an option to me.
Another way could be the relocation of export table upon module loading,
expanding it at runtime by adding the required number of "statistics fakers"
(data exports with zero init).
This requires modifying the ntdll loader .. though i'm not sure if this
approach breaks other applications/braindamaged PE protection stuff which
expect certain conditions to be met (tables present at specific sections/memory
areas).
------------------------------
(2)
Well, take it as proof of concept. Play with it.
I tested my patch with a few SafeDisc 2.x games I have original media.
No cracks/no-cd patches were used.
Only official game patches were used.
Battlefield 1924 (1.6x) - SafeDisc 2.6/2.8
Road To Rome (BF1942 expansion) - SafeDisc 2.8
Battlefield Vietnam - SafeDisc 2.9
All of these work fine for me with the patch applied.
Please test this patch on many SafeDisc 2.x games as possible and report your
results (works or works not).
Make sure you have original media mounted and drive/data is visible within
wine.
If it fails for first time, the media might not ready yet, try again then (I
experienced this sometimes).
Use this link to verify what SafeDisc Version is used:
http://www.120search.net/ (alcohol software copy protection database)
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9798
Summary: bioshock demo needs glsl enabled
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=8240)
--> (http://bugs.winehq.org/attachment.cgi?id=8240)
crash log with glsl disabled
Hello,
Bioshock demo crashes if glsl is not enabled.
Attached are relevant traces made with:
WINEDEBUG=+seh,+tid,+d3d,+d3d_shader wine ./Bioshock.exe -dx9
Using following registry settings enables bioshock demo to run:
--- snip ---
HKEY_CURRENT_USER/Software/Wine/Direct3D
UseGLSL = "enabled"
--- snip ---
Optional: OffscreenRenderingMode = "fbo"
==================
Addendum:
wine --version
wine-0.9.45-406-g2ba3247
Currently uses secuROM hack (http://bugs.winehq.org/attachment.cgi?id=8235
) to run, see http://bugs.winehq.org/show_bug.cgi?id=7065
Be sure to include "-dx9" command line to work around directx 10 issue.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.