December 2015 - Wine-bugs - list.winehq.org

[Bug 33259] New: UDK: antichamber crashes during startup in unsetup.exe after accepting EULA
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

http://bugs.winehq.org/show_bug.cgi?id=33259 Bug #: 33259 Summary: UDK: antichamber crashes during startup in unsetup.exe after accepting EULA Product: Wine Version: 1.5.26 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: peter.waller(a)gmail.com Classification: Unclassified Created attachment 43988 --> http://bugs.winehq.org/attachment.cgi?id=43988 crash log When starting antichamber through steam according to the instructions at http://appdb.winehq.org/objectManager.php?sClass=version&iId=27571 it crashes before the game can start. -- 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 34919] New: Quake Live standalone can't grab input correctly
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

http://bugs.winehq.org/show_bug.cgi?id=34919 Bug #: 34919 Summary: Quake Live standalone can't grab input correctly Product: Wine Version: 1.7.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winehq(a)lam.pl Classification: Unclassified Quake Live is moving out of the browser and becoming a standalone Windows executable, dropping support for Linux and Mac OS X. When testing the product preview in Wine, I have big issues related to the Alt key. 1. After pressing "Join Game", the game grabs input like I want it. Both Google and #winehq(a)freenode immediately suggest that window manager can grab alt-mouse click, hence I feel it's necessary to confirm: I can press Alt and click mouse and all works as intended (aka I can shoot and turn around while shooting, even with the Alt key pressed). There is no problem with mouse grab or window manager at this point. 2. After pressing a combination of Alt+Space, a Wine window menu appears, even though Wine is WM-managed and even though the same combo has no "system" effect on Windows (the key combo can be bound by game on Windows). The game is completely stopped until I click mouse. Pressing Alt or Esc to close the menu doesn't "unpause" game process. 3. After pressing Alt+any letter, mouse buttons (including mouse wheel scrolling) stop working. Keyboard works and moving mouse around still works, but mouse buttons are dead. To get back from this state, I need to open and close menu (Esc-Esc) or console (tilde-tilde). If I'm in window mode, there's a very short time window (like 50 ms?) when the mouse is un-grabbed and clicking the mouse in combination with alt+letter actually is captured by the WM (to start moving window). But that's only a side-effect of mouse un-grabbing. Again: to break mouse input, all I need is to press alt+any letter, which for sure isn't captured by anything else but Wine itself. 4. When I've tried Wine with non-WM-managed windows, there were more negative effects, including complete game hang on pressing Alt alone (and resuming with another Alt hit). So I went back to managed window. 5. I have thought about working around this by doing xmodmap -e "keycode 64 = something else" but this has other unintended consequences and is system-wide. I have tested it in Wine 1.6, 1.7.5 and 1.7.6 (I've built it with Fedora's spec, including PulseAudio patch which works nicely and surely isn't related to this problem). TL;DR: Alt+any letter forcibly breaks game's input grab which can only be regained by making the game release and re-grab input. As an interim solution, is there a way to make Wine completely deaf to Alt combos? -- 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 6

[Bug 34599] New: CD audio tracks are not played in WinQuake Demo
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

http://bugs.winehq.org/show_bug.cgi?id=34599 Bug #: 34599 Summary: CD audio tracks are not played in WinQuake Demo Product: Wine Version: 1.7.2 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winebugs140(a)gmail.com Classification: Unclassified Created attachment 46083 --> http://bugs.winehq.org/attachment.cgi?id=46083 WinQuake Demo Log CD audio tracks are not played in WinQuake Demo although in the game's console one can find that CD is initialized. You may use any audio CD to test that. QUAKE 1 DOS Demo (WinQuake needs its files): ftp://ftp.idsoftware.com/idstuff/quake/quake106.zip WinQuake: ftp://ftp.idsoftware.com/idstuff/quake/wq100.zip Tested with: Mac OS X 10.7.5, OPTIARC DVD RW AD-5630A, ATI HD 2600 Pro, Mac Driver/X11 -- 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 13

[Bug 30847] New: 2009 Decoder: crashes when being started
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

http://bugs.winehq.org/show_bug.cgi?id=30847 Bug #: 30847 Summary: 2009 Decoder: crashes when being started Product: Wine Version: 1.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jan_usa2000(a)web.de Classification: Unclassified Created attachment 40395 --> http://bugs.winehq.org/attachment.cgi?id=40395 2009 Decoder crash backtrace (page fault) Wine crashes when I try to run 2009 Decoder for OTR recordings (http://www.onlinetvrecorder.com/downloads/OTRDecoder_2.0.0.21.zip -> Extracted). -- 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 6

[Bug 31365] New: Shaiya FPS drop after ~1 min of game playing
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

http://bugs.winehq.org/show_bug.cgi?id=31365 Bug #: 31365 Summary: Shaiya FPS drop after ~1 min of game playing Product: Wine Version: 1.5.9 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: qbanin(a)gmail.com Classification: Unclassified For about 1 min after running Shaiya I have ~20-25 fps, but after this time (of doing nothing in the game) framerate drops to 5-10 fps. In the meantime console is spammed with: fixme:d3d:wined3d_buffer_preload Too many full buffer conversions, stopping converting. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. .... This bug affects all versions of Wine up to 1.5.9. -- 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 37656] New: Wine Crashes when Opening "Banda Ancha Movil" Application
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

https://bugs.winehq.org/show_bug.cgi?id=37656 Bug ID: 37656 Summary: Wine Crashes when Opening "Banda Ancha Movil" Application Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adalberto.toledo(a)gmail.com Distribution: --- Created attachment 50113 --> https://bugs.winehq.org/attachment.cgi?id=50113 Thi is the log trace that it shows I installed a software for my usb modem ZTE VTR, and when I try to open the software it crashes... The name of thw software is "Banda Ancha Movil" -- 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 39490] New: Wine 1.7.53 crashes when starting StarCraft 2 (Wine 1.7.52 works fine)
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

https://bugs.winehq.org/show_bug.cgi?id=39490 Bug ID: 39490 Summary: Wine 1.7.53 crashes when starting StarCraft 2 (Wine 1.7.52 works fine) Product: Wine Version: 1.7.53 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de Distribution: --- Compiled Wine-1.7.52 (and all the versions before) myself. Works completely fine with StarCraft 2! Today compiled Wine-1.7.53 and it always crashes immediately and gives me the attached error on the shell. When reverting back to Wine-1.7.52, everything is OK again. The command I use to start StarCraft 2 and what happened: $ env LD_LIBRARY_PATH=~/opt/mesa3d/lib vblank_mode=0 WINEDLLOVERRIDES=winemenubuilder.exe=d force_s3tc_enable=true WINEARCH=win32 WINEPREFIX=~/wines/starcraft2/ ~/opt/wine/bin/wine ~/"wines/starcraft2/drive_c/Program Files/StarCraft II/StarCraft II.exe" err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2) fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub wine: Unhandled page fault on read access to 0x00000010 at address 0x7eab8a9a (thread 0029), starting debugger... X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 1 (X_CreateWindow) Resource id in failed request: 0x8200007 Serial number of failed request: 78 Current serial number in output stream: 82 Note: Compiled Mesa3D myself to (version 11.0.0). Tried running something simple with my standard system Mesa3D library. But that's also crashing... env WINEDLLOVERRIDES=winemenubuilder.exe=d WINEARCH=win32 WINEPREFIX=~/wines/starcraft2/ /home/moritz/opt/wine/bin/wine notepad wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe" err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2) wine: Unhandled page fault on read access to 0x00000010 at address 0x7eab8a9a (thread 0022), starting debugger... wine: Unhandled page fault on read access to 0x00000010 at address 0x7e7e3a9a (thread 0009), starting debugger... winedbg: Internal crash at 0x7bc5828d Interestingly Wine-1.7.53 is running fine with other WINEPREFIX'es. Guess it's maybe one of the following registry settings I made for the StarCraft 2 WINEPREFIX. I already compared the registry-settings in HKEY_CURRENT_USER\Software\Wine\Direct3D but they are the same in both WINEPREFIX'es. OS: openSUSE 13.2 (x86_64) CPU+GPU: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz -- 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 32070] New: Pepakura Designer and Viewer crash on startup
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

http://bugs.winehq.org/show_bug.cgi?id=32070 Bug #: 32070 Summary: Pepakura Designer and Viewer crash on startup Product: Wine Version: 1.5.16 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jarrodbagwell(a)gmail.com Classification: Unclassified Created attachment 42276 --> http://bugs.winehq.org/attachment.cgi?id=42276 Pepakura Crash Dump Pepakura Designer and Viewer both crash with the same errors upon startup. The errors are "DIB Init Failed" and "Rendering Context Create Failed". These two error messages flash a few times and then the programs crash. I have looked at bug 30703, and I don't think it's the same issue, at least from what I can understand. This issue only started when I upgraded to wine 1.5.15. The curious thing is that Pepakura Designer and Viewer both still work fine on a different computer that I have running wine 1.15.15. The video cards are different, but another difference that I have been thinking about is that the other computer is 32 bit, while my home computer is 64 bit. I don't know if that makes any sort of difference, but something I thought about. Crash dump is attached below. To recreate the error: 1. Have wine 1.5.15 or up installed 2. Install the latest version of Pepakura Viewer or Designer (http://www.tamasoft.co.jp/pepakura-en/) 3. Attempt to run it. -- 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 12

[Bug 21264] New: Colin McRae Rally 2.0 doesn't allow to skip intro movie
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

http://bugs.winehq.org/show_bug.cgi?id=21264 Summary: Colin McRae Rally 2.0 doesn't allow to skip intro movie Product: Wine Version: 1.1.33 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: atiitto(a)luukku.com Colin McRae Rally 2.0 doesn't allow to skip intro movie after launching the game. -- 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 32064] New: Star Wars: Empire At War - Could not initialize Direct3D
by wine-bugs＠winehq.org 02 Dec '15

02 Dec '15

http://bugs.winehq.org/show_bug.cgi?id=32064 Bug #: 32064 Summary: Star Wars: Empire At War - Could not initialize Direct3D Product: Wine Version: 1.4.1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dj.houba(a)email.cz CC: wine-bugs(a)winehq.org Classification: Unclassified Created attachment 42262 --> http://bugs.winehq.org/attachment.cgi?id=42262 sweaw.exe Please help. When I want to run Star Wars Empire at War, I get error: "Could not initialize Direct3D" Full message is: "Could not initialize Direct3D. You may want to check that the latest version of DirectX is correctly installed on your system. Also make sure that this program was compiled with header files that match the installed DirectX DLLs. This application will now exit." I tried more Wine versions (gold from AppDB) but no success. I have installed d3dx9_27.dll in wine(system32) folder. My SW: Linux Debian Wheezy, Wine 1.4.1 My HW: Intel i5, GeForce GTX 560 Ti(3D Acceleration working) I added log from wine (after crash). Thank you -- 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 14