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

[Bug 18378] New: NFS 4 Road Challenge: Installation of 4.50 patch fails
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

http://bugs.winehq.org/show_bug.cgi?id=18378 Summary: NFS 4 Road Challenge: Installation of 4.50 patch fails Product: Wine Version: 1.1.19 Platform: PC URL: ftp://ftp.physics.auth.gr/pub/mirrors/ftp.patches- scrolls.de/pub/pc-patches/3dcard-patches/nfs4v450.zip OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=20952) --> (http://bugs.winehq.org/attachment.cgi?id=20952) WINEDEBU=+relay,+advapi,+seh I'm using Wine 1.1.19 (compiled from source using gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) ) on Fedora 10 i386. I tried to patch (NFSHSpatch4_50.exe size 1.8 MB) NFS 4: Road Challenge and the problem is that patch 4.50 doesn't even want to 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 13

[Bug 35975] New: Comanche 3 shows only gray screen
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

http://bugs.winehq.org/show_bug.cgi?id=35975 Bug ID: 35975 Summary: Comanche 3 shows only gray screen Product: Wine Version: 1.7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: c_korn(a)gmx.de There is a regression in wine which leads to only a gray screen when starting Comanche 3. The Dolby Surround video plays fine. But then there is nothing to see but a gray screen (starting in wine desktop mode). Using wine-1.7.15 on Ubuntu 13.10 (NVIDIA GTX 460, driver 319.32). This is actually a regression: 4c4552c5a1910a9d5adf8eccff0ac62d89ffe376 is the first bad commit commit 4c4552c5a1910a9d5adf8eccff0ac62d89ffe376 Author: Ken Thomases <ken(a)codeweavers.com> Date: Wed Feb 19 16:14:53 2014 -0600 wined3d: Restore the pixel format of the window whose pixel format was actually changed. :040000 040000 952ab31d0408cbe5b261faf85e3c02c0febd3416 162b97adb27bd867c3729ff124025d51ac5b57a0 M dlls -- 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 15

[Bug 32006] New: Two Direct3D10 SDK samples abort with "Could not enumerate adapters. This application will now exit."
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

http://bugs.winehq.org/show_bug.cgi?id=32006 Bug #: 32006 Summary: Two Direct3D10 SDK samples abort with "Could not enumerate adapters. This application will now exit." Product: Wine Version: 1.5.15 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Install the DirectX SDK from June 2010, then look in c:/Program Files/Microsoft DirectX SDK (June 2010)/Samples/C++/Direct3D10/Bin/x86 and try running 10BitScanout10.exe or MultiMon10.exe. They both abort with a log like: fixme:dxgi:dxgi_output_GetDesc iface 0x1511c8, desc 0x33fbdc stub! and a MessageBox saying "Could not enumerate adapters. This application will now exit." -- 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 20

[Bug 25064] New: Solo on Keyboard 9.0.5: Clicking on HTML page no effect.
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

http://bugs.winehq.org/show_bug.cgi?id=25064 Summary: Solo on Keyboard 9.0.5: Clicking on HTML page no effect. Product: Wine Version: 1.3.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: newgarry(a)mail.ru Created an attachment (id=31782) --> (http://bugs.winehq.org/attachment.cgi?id=31782) Solo on Keyboard 9.0.5 debug log After launching application (Bug 25033) with help 'winetricks msxml6', exercise can't start, because application not react to left mouse button click on HTML frame hyperlink. Debug log included. $WINEPREFIX directory clean, but was used 'winetricks msxml6'. -- 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 28589] New: Poor performance in Diner Dash 5
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

http://bugs.winehq.org/show_bug.cgi?id=28589 Bug #: 28589 Summary: Poor performance in Diner Dash 5 Product: Wine Version: 1.3.29 Platform: x86-64 URL: http://www.playfirst.com/game/diner-dash-5-boom-collec tors OS/Version: Linux Status: NEW Keywords: download, performance Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Classification: Unclassified Performance in Diner Dash 5 significantly affects the game. Mouse clicks are often "missed" making the game almost totally unplayable. Things are much better in Wine 1.3.20, but a bisect may take a while. Very little in the console. fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:win:EnumDisplayDevicesW ((null),0,0x32e7fc,0x00000000), stub! fixme:ddraw:ddraw7_GetMonitorFrequency iface 0x168fe8, frequency 0x32f8c4 stub! fixme:atl:AtlAxWinInit semi-stub Note to self: Virtual desktop (800x600) needed or the system locks up (not a Wine bug). -- 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 4

[Bug 36970] New: running blue iris software opens then closes after 30 seconds
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

http://bugs.winehq.org/show_bug.cgi?id=36970 Bug ID: 36970 Summary: running blue iris software opens then closes after 30 seconds Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: shodge1122(a)verizon.net Created attachment 49092 --> http://bugs.winehq.org/attachment.cgi?id=49092 crash file for Blue Iris software I can open the application and view live feed from camera however it closes after maybe 30 seconds. it will open again but behavior is the same. -- 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 4

[Bug 37859] New: BOINC 6.x/7.x take a long time to "start" when launched from boincmgr
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

https://bugs.winehq.org/show_bug.cgi?id=37859 Bug ID: 37859 Summary: BOINC 6.x/7.x take a long time to "start" when launched from boincmgr Product: Wine Version: 1.7.33 Hardware: x86-64 URL: http://boinc.berkeley.edu/dl/boinc_7.4.36_windows_inte lx86.exe OS: Linux Status: NEW Keywords: download, performance, source Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 50421 --> https://bugs.winehq.org/attachment.cgi?id=50421 Wine 1.7.33 / BOINC 7 console output There are a number of ways to start BOINC on a system: 1. At system startup (daemon/service). 2. On its own (in a console). 3. By launching boincmgr.exe (BOINC Manager). As of BOINC 6.x, option 3 can take around 60 seconds to "start". In reality the BOINC client (boinc.exe) starts immediately, just as quickly as any other way, but boincmgr.exe struggles repeatedly to connect. However: A. If BOINC is already running, boincmgr.exe connects instantly. B. If a second boincmgr.exe is launched immediately after the first (giving the few seconds for boinc.exe to start) it can connect immediately. C. boincmgr.exe can connect to any other client without any issue. So it's *just* when boincmgr.exe first launches boinc.exe that seems to confuse things. >From stdoutgui.txt: [01/06/15 16:24:00] TRACE [9]: init_asynch() boinc_socket: 212 [01/06/15 16:24:00] TRACE [9]: init_asynch() connect: -1 [01/06/15 16:24:03] TRACE [9]: init_poll(): sock = 212 [01/06/15 16:24:04] TRACE [9]: init_poll(): sock = 212 [01/06/15 16:24:04] TRACE [9]: init_poll(): sock = 212 [...] [01/06/15 16:25:01] TRACE [9]: init_poll(): sock = 212 [01/06/15 16:25:01] TRACE [9]: asynch init timed out [01/06/15 16:25:01] TRACE [9]: init_asynch() boinc_socket: 212 [01/06/15 16:25:01] TRACE [9]: init_asynch() connect: -1 [01/06/15 16:25:01] TRACE [9]: init_poll(): sock = 212 [01/06/15 16:25:01] TRACE [9]: init_poll(): connected So it times out after 60 seconds and tries again with success. In comparison, scenario A gives: [01/06/15 16:41:13] TRACE [42]: init_asynch() boinc_socket: 216 [01/06/15 16:41:13] TRACE [42]: init_asynch() connect: -1 [01/06/15 16:41:14] TRACE [42]: init_poll(): sock = 216 [01/06/15 16:41:14] TRACE [42]: init_poll(): connected Tried both 32- and 64-bit binaries in both 32- and 64-bit WINEPREFIXes, same result each time. BOINC 5.8.16 does not have this problem. $ sha1sum boinc*.exe b4cdb23c8f51f33799c9d784ba38a9f69338fb68 boinc_5.8.16_windows_intelx86.exe c8dba7a184076240cdeef5032a9825a90244bb3f boinc_6.6.38_windows_intelx86.exe a67223afefb7072c82b366cab9d21e21ad2a719d boinc_7.0.64_windows_intelx86.exe 93f7a6639eca9bd7c8558146c2b23f954dffe9ef boinc_7.0.64_windows_x86_64.exe c86c17637d59ea12e78ed3fb56bb92beae897132 boinc_7.2.33_windows_intelx86.exe d761a1a57cf7836e2a33a5cd68ddb3bdd5e57af6 boinc_7.2.33_windows_x86_64.exe 277f9cf8007fe5f6901f6c04a4d3aa985fd172a9 boinc_7.2.42_windows_intelx86.exe d1f4f5de1ccef0977009800a9ff70321859b45b2 boinc_7.2.42_windows_x86_64.exe 2919cc9b6163019fc014a7fa4190bee8ead4b544 boinc_7.4.36_windows_intelx86.exe c2334aa9696f11a3f50dac07d1648c6b77ef9ae2 boinc_7.4.36_windows_x86_64.exe -- 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 35655] New: Wined3d performance drop
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

http://bugs.winehq.org/show_bug.cgi?id=35655 Bug ID: 35655 Summary: Wined3d performance drop Product: Wine Version: 1.7.13 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: wylda(a)volny.cz In between 1.7.13 and wine-1.7.13-27-ge610713 i noticed performace drop in 3Dmark 2000. In overall score it makes -14%, but as the CPU tests and MTexels/s & KTriangels/s remained cca the same, some FPS tests dropped to -20% ("8MB Texture Rendering Speed"). Since 1.7.13 there were not too much 3d changes, but anyway i bisected to: 4c4552c5a1910a9d5adf8eccff0ac62d89ffe376 is the first bad commit commit 4c4552c5a1910a9d5adf8eccff0ac62d89ffe376 Author: Ken Thomases <ken(a)codeweavers.com> Date: Wed Feb 19 16:14:53 2014 -0600 wined3d: Restore the pixel format of the window whose pixel format was actually changed. -- 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 24

[Bug 35418] New: some drawing operations in Mixcraft 6 are very slow with client-side graphics enabled
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

http://bugs.winehq.org/show_bug.cgi?id=35418 Bug ID: 35418 Summary: some drawing operations in Mixcraft 6 are very slow with client-side graphics enabled Product: Wine Version: 1.7.11 Hardware: x86 URL: http://acoustica.com/mixcraft/download.htm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: s_chriscollins(a)hotmail.com Classification: Unclassified Regression SHA1: 33ac850c80634c891b0c157bbffa612f70954a40 According to my git bisect, this bug appeared after the following commit: -------- winex11: Use window surfaces for rendering top-level windows. It can be disabled by setting "ClientSideGraphics"="n". commit: 33ac850c80634c891b0c157bbffa612f70954a40 -------- After the above commit, the following operations in Mixcraft 6 are very slow/laggy: 1) Scrolling vertically in the track view when there are lots of tracks present 2) Scrolling horizontally in piano roll view. 3) Resizing the workspace between the top and bottom view. 4) Adjusting the knobs and sliders of certain FX plugins. Steps to Reproduce: 1) Download and setup the Mixcraft trial (http://acoustica.com/mixcraft/download.htm) 2) If you are opening Mixcraft for the first time, it will auto-load and play a demo project. After this happens, click the "Open Project" icon (looks like a folder), and open "Callisteia.mx6". If it isn't showing in the file picker by default, you can find it in: "C:\Program Files\Acoustica Mixcraft 6\Example Projects". Go to step 4. 3) If you are opening Mixcraft after having already opened it before, it will start instead with a "New Project" dialog. Simply click the "Browse..." button here to find and open the file mentioned in step 2. 4) With "Callisteia.mx6" now opened, use the scrollbar to the right to scroll up and down through all the tracks in the project. 5) Double-click on the instrument clip for track #8 (Sweet Flute). This will bring up the clip in notation view at the bottom half of the screen. Near the bottom-left, change Editor Type from "Notation" to "Piano Roll". Use the scrollbar to scroll right and left in the piano roll view. 6) Position your cursor just below the playback controls near the middle of the screen; it should turn into a resize handle. Hold down the mouse button and move the mouse up and down to resize the split between the top and bottom screen areas. Result: The tests done in steps 4-6 are responsive and reasonably smooth in Wine versions prior to the aforementioned commit. In versions after the commit, these tests give very choppy and laggy results. I had mentioned that some FX plugins were also choppy/laggy, but this only affects some of the plugins that are bundled with Mixcraft Pro Studio 6, which is not available as a free trial download. Just in case anybody wants to know, the plugins are: FAT+, Ferox Tape Emulator, all "Mid-Side" plugins, TB Gate, and TimeMachine. If you want to test a free plugin that exhibits the slowness, and you know how to bring up a VST's GUI within Mixcraft, you can download L3V3LL3R: http://www.platinumears.com/l3v3ll3r.html. Be sure to copy the .dll file to "C:\Program Files\VST". -- 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 30

[Bug 39039] New: Popup tooltips missing and buttons don't work on mageia.org/en/downloads/
by wine-bugs＠winehq.org 27 Nov '15

27 Nov '15

https://bugs.winehq.org/show_bug.cgi?id=39039 Bug ID: 39039 Summary: Popup tooltips missing and buttons don't work on mageia.org/en/downloads/ Product: Wine Version: 1.5.1 Hardware: x86 OS: Linux Status: NEW Keywords: download, regression, source Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 6c6744f80066f0aa46939a2d4c0af9c34f932e8b Distribution: --- Created attachment 52001 --> https://bugs.winehq.org/attachment.cgi?id=52001 terminal output If you visit the download page for Mageia Linux distribution wine iexplore https://www.mageia.org/en/downloads/ you can see 3 big buttons at the bottom of the page titled 'Classic', 'Live' 'Network installation'. Place the mouse pointer over the buttons >> nothing happens. Normally, a popup tooltip should appear giving you a short description of the selected installation flavour. Click on one of those buttons >> nothing happens, again. Normally another button should appear below, allowing you to choose PC architecture and download method. Popup tooltips as well as those buttons used work until commit 6c6744f80066f0aa46939a2d4c0af9c34f932e8b Author: Jacek Caban <jacek(a)codeweavers.com> Date: Tue Mar 27 13:40:01 2012 +0200 mshtml: Use jscript.dll for JavaScript for all zones except untrusted. Reverting the patch on current git fixes the problem. Firefox when installed in Wine also can handle those buttons properly. In the terminal I'm getting these fixmes when clicking on a button on the download page: fixme:mshtml:HTMLEventObj_get_toElement (0xbdde08)->(0x33dc10) fixme:mshtml:HTMLEventObj_get_offsetY (0xbdde08)->(0x33dc10) fixme:mshtml:HTMLEventObj_get_offsetX (0xbdde08)->(0x33dc10) fixme:mshtml:HTMLEventObj_get_fromElement (0xbdde08)->(0x33dc10) fixme:mshtml:HTMLEventObj_get_fromElement (0xbdde08)->(0x33d7e0) Tested with wine-1.7.48-100-ge3c6777 + Wine Gecko 2.36 installed -- 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