June 2010 - Wine-bugs - list.winehq.org

[Bug 20669] New: Certain objects found in game cause EQ2 to crash.
by wine-bugs＠winehq.org 10 Jul '10

10 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=20669 Summary: Certain objects found in game cause EQ2 to crash. Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben(a)walkingriver.com While wandering around through the game, it will suddenly crash. Almost every time, it happens when an item comes into view. The objects that cause these crashes are unknown, but include crafting stations and the ykeshan bear mount. -- 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.

1 17

[Bug 19659] New: EverQuest 2: EQ2 Crashed shortly after entering game.
by wine-bugs＠winehq.org 10 Jul '10

10 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=19659 Summary: EverQuest 2: EQ2 Crashed shortly after entering game. Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jonilh(a)gmail.com This problem seams pressent in the 1.1.2* versions of Wine 1.1.18 is not a problem. Latest tested 1.1.27 where the crashes still remains. In 1.1.18 and earlyer, pets wont move, doors dont show as open when you open them. This for the first few minutes everytime I start the game. In 1.1.18 and earlyer this just corrects itself afer a few minutes and after that works fine for that session. But in the later versions of wine when it used to correct itself the game insted crashes with a errormessage from Wine saying it might be a bug in wine. I hope this will give some hint to where the problem can be. -- 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.

1 42

[Bug 23386] New: TF2 throws pixel shader 1.1 error when started with -dxlevel 9
by wine-bugs＠winehq.org 09 Jul '10

09 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=23386 Summary: TF2 throws pixel shader 1.1 error when started with -dxlevel 9 Product: Wine Version: 1.2-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: cookiecaper(a)gmail.com If I start TF2 with the option -dxlevel 9, the splash screen renders, and then the game closes and an error message that says something like "Your graphics hardware must support pixel shader 1.1 to play this game!" occurs. It works completely fine with -dxlevel 81. I've had this error for years, but I've been hearing more and more people talk about playing with dxlevel 9 recently, claiming it runs great or even better than dxlevel 81. I have tried a new prefix, a new Steam directory, running inside and outside my 32-bit chroot, and none of these things have changed anything. I am running ArchLinux with kernel 2.6.34, nvidia 256.35, GeForce GTX 285, but as I said, I've had this trouble for years, even when using different nvidia cards (previously had a 7900GTO). Through all the WINE updates, everything, this has stayed constant. I'm currently running a version from git compiled yesterday. I'll attach a couple of snippets from a Steam run for your examination. Thanks for looking, and thanks to everyone in IRC who helped, especially kevlarman. -- 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.

1 7

[Bug 23417] New: EverQuest II: Crashes immediately after hitting "Play" at character select screen
by wine-bugs＠winehq.org 09 Jul '10

09 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=23417 Summary: EverQuest II: Crashes immediately after hitting "Play" at character select screen Product: Wine Version: 1.2-rc5 Platform: x86 URL: http://www.everquest2.com/en/freeTrial.vm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: cww(a)denterprises.org Selecting "Play" to enter the game from the character select screen in EQ2 crashes the game. It appears to be a null pointer reference. I am currently on my last few compiles of a git bisect, so I'll post more information soon-ish. -- 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.

1 16

[Bug 22944] New: Goldwave dialog windows drawn behind parent window
by wine-bugs＠winehq.org 09 Jul '10

09 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=22944 Summary: Goldwave dialog windows drawn behind parent window Product: Wine Version: 1.2-rc2 Platform: x86 URL: http://www.goldwave.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: billstei(a)hbci.com In Goldwave 5.56 and Wine 1.2-rc2 and Gnome 2.30.0 dialog windows like those invoked by File->Open or File->New appear behind the parent window (which also produces the illusion that the program has locked up, even though it has not). -- 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.

1 5

[Bug 22215] New: Goldwave - Window Close event freezes application
by wine-bugs＠winehq.org 09 Jul '10

09 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=22215 Summary: Goldwave - Window Close event freezes application Product: Wine Version: 1.1.41 Platform: x86 URL: http://www.goldwave.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: billstei(a)hbci.com In Goldwave 5.55, Gnome 2.28.1, and Wine 1.1.41, when clicking the Close Window button the program locks up. Sometimes the program unfreezes after a few minutes (but does not close). Closing the program with menu File->Exit works normally. Winecfg has "Allow the window manager to ..." both "decorate" and "control" checked. -- 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.

1 7

[Bug 21422] New: winedbg cannot find local symbols in EXE.
by wine-bugs＠winehq.org 09 Jul '10

09 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=21422 Summary: winedbg cannot find local symbols in EXE. Product: Wine Version: 1.1.36 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg AssignedTo: wine-bugs(a)winehq.org ReportedBy: donpedro(a)tdcadsl.dk While trying to debug: http://bugs.winehq.org/show_bug.cgi?id=21388 (test.exe - attachment #1). ,i found this bug in winedbg. winedump finds all of the symbols, but winedbg cannot do the same. so: "break __do_global_dtors" cannot find the symbol. I tried to debug winedbg/dbghelp.dll a bit to find the problem and found some hints (i am not sure if all of it is correct): 1) Module_get_container() does not return the correct module. It returns "/lib/libc" as the container for "test.exe". This does not seem right. If i hack myself around this i get to: 2) It would seem that winedbg/debughlp.dll only loads "export" symbols? As the EXE has no exports then no symbols are found.... is this right? What about all of the other symbols? Furthermore, if i force the debugger to break at the correct place, the debugger seems to show the wrong disassembly. Not sure if that is the same bug or a different one. -- 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.

1 8

[Bug 22213] New: The game "The Witcher, Enhanced edition" can`t run on wine 1.1.41
by wine-bugs＠winehq.org 09 Jul '10

09 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=22213 Summary: The game "The Witcher, Enhanced edition" can`t run on wine 1.1.41 Product: Wine Version: 1.1.41 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: alxhook(a)gmail.com Created an attachment (id=27106) --> (http://bugs.winehq.org/attachment.cgi?id=27106) Crash log Wine 1.1.41 have a regression, the game "The Witcher, Enhanced edition" can`t run. On Wine 1.1.40 it`s works. -- 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.

1 11

[Bug 20650] New: Wargames crashes instantly if choosing hardware mode (rather than Software Rasterizer)
by wine-bugs＠winehq.org 09 Jul '10

09 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=20650 Summary: Wargames crashes instantly if choosing hardware mode (rather than Software Rasterizer) Product: Wine Version: 1.1.32 Platform: PC URL: http://www.kazade.co.uk/downloads/wargames.zip OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kazade(a)gmail.com When Wargames initially starts you are given the option of choosing from "Software Rasterizer" or "DirectDraw HAL". Choosing the latter causes a crash when you OK the dialog: "Unhandled exception: page fault on read access to 0x00000600 in 32-bit code (0x00000600)." Choosing Software Rasterizer gets you further but that crashes later (see bug 20629) -- 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.

1 5

[Bug 18475] New: Fallout 3: No sound device detected. Fallout 3 cannot run.
by wine-bugs＠winehq.org 09 Jul '10

09 Jul '10

http://bugs.winehq.org/show_bug.cgi?id=18475 Summary: Fallout 3: No sound device detected. Fallout 3 cannot run. Product: Wine Version: 1.1.20 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: directx-dsound AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=21097) --> (http://bugs.winehq.org/attachment.cgi?id=21097) Error message I'm using Wine 1.1.21 (compiled from source using gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) ) on Fedora 10 i386. When I launch FalloutLauncher.exe and click Play the Error message is displayed as in attachment. The music is played in this launcher though. Sound Driver: ALSA -- 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.

1 11