February 2016 - Wine-Bugs - list.winehq.org

[Bug 35291] New: setcap on wine-preloader makes Hearthstone fail to start
by wine-bugs＠winehq.org March 20, 2016

March 20, 2016

http://bugs.winehq.org/show_bug.cgi?id=35291 Bug ID: 35291 Summary: setcap on wine-preloader makes Hearthstone fail to start Product: Wine Version: 1.7.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yeled.nova(a)gmail.com Classification: Unclassified Hi, When a Linux capability is enabled for wine preloader, Hearthstone does not start. This bug at least affects ------------------------- Archlinux x64/Linux 3.12.6-1-ARCH/Wine 1.7.9/libcap 2.22 Ubuntu 13.10 x64/Linux 3.11.0-14-generic/Wine (PPA) 1.7.9/libcap 2.22 Steps to reproduce ------------------ # setcap 'cap_net_bind_service=+ep' /usr/bin/wine-preloader $ wine Hearthstone.exe -launch -uid hs_beta Get a message box that captions "Fatal error in gc" and says "GetThreadContext failed", click "OK" Another message box that captions "Wine program crash", and says "Internal errors - invalid parameters received", click "OK" The process turns to a zombie, kill it. Revert the capabilities, the program loads. # setcap '-r' /usr/bin/wine-preloader $ wine Hearthstone.exe -launch -uid hs_beta This issue persists over system reboots. It's not just setting CAP_NET_BIND_SERVICE causes the problem. From what I observed, this error occurs as long as any capablity is enabled. Note on getting debug trace --------------------------- Right now due to bug #33947, battle.net.exe requires dbghelp to be disabled, and Hearthstone.exe depends on it in order to play. However, directly running Hearthstone.exe is good enough to reproduce this bug. So I suggest anyone who wants to look into this problem to re-enable the debugger and run 'wine Hearthstone.exe -launch -uid hs_beta' to get a debug trace. -- 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 19286] New: puTTy connection manager: two UI bugs makes program unusable
by wine-bugs＠winehq.org March 19, 2016

March 19, 2016

http://bugs.winehq.org/show_bug.cgi?id=19286 Summary: puTTy connection manager: two UI bugs makes program unusable Product: Wine Version: 1.1.23 Platform: PC URL: http://appdb.winehq.org/objectManager.php?sClass=versi on&iId=17165 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gui4life(a)gmail.com Created an attachment (id=22324) --> (http://bugs.winehq.org/attachment.cgi?id=22324) output from wine puttycm.exe &> newputtylog.txt The user interface for PuTTy connection manager does not display correctly making it a broken application inside of wine. It is not displaying the far most right window called "Connection Manager" that displays the list of your saved connections. You should be able to click any of the connections of which you want to connect, and it would launch a tabbed putty window. Most importantly, the putty intergeneration itself is not being displayed inside of putty connection manager. In the middle of the application you should be able to have multiple putty windows open that are separated by tabs and you are able to move them around. (Stacking along side themselves if you like) To get a better idea what I mean, it is best to try the program out yourself in windows where it works flawlessly. I have tried many things to get this application to work. I installed net 2.0 and msxml6. I saw an xml error inside of the log, after installing msxml6 it went away, but program did not work any better. In the options of the program there are multiple interface designs you can use (more or less skins/themes) like office 2007, system, visual studio 2003, visual studio 2005. All of them have the same UI bug. I have tried the standalone app of putty connection manager where you don't have to install anything, and the installable version. See attached redirect files -- 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 15

[Bug 22146] New: 64bit compatibility issue with Wine's MCI string command parser
by wine-bugs＠winehq.org March 19, 2016

March 19, 2016

http://bugs.winehq.org/show_bug.cgi?id=22146 Summary: 64bit compatibility issue with Wine's MCI string command parser Product: Wine Version: 1.0.0 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net Created an attachment (id=27005) --> (http://bugs.winehq.org/attachment.cgi?id=27005) work in progress MCI parser that knows about 64bit structures Hi, Wine's MCI string command parser is one reason why test.winehq.org shows failures with 64bit machines. I've created this issue so everybody can discuss and contribute patches until evolution leads to a correct one. The attached patch fixes part of what's currently in git, but it is still incomplete. Therefore I don't plan to submit it. I've run tests on WTB's 64bit machines that proove that MCI_STATUS_PARMS and MCI_GETDEVCAPS indeeed process differently sized dwReturn types on x64: DWORD_PTR and DWORD. That's what's missing from my patch. A solution that sounds ideal is to define something like MCI_INTEGER64 and change the resource files mciavi_res.rc and winmm_res.rc. Given that new type, the MCI string parser would compute the correct offset. I'd be very pleased if somebody could conform that MS does it this way and tell us the value of this constant. Another solution path is to special-case MCI_STATUS_PARMS in the parser, as it uses the only 64bit construct I knew until 5 minutes ago (beside dwCallback of course) that's not a LP(W)STR. HWND seems to be 32bit. 5 minutes later: What about HDC in MCI_DGV_UPDATE_PARMS? Wait, wtypes.h says void*! The MCI string command parser needs to handle this type as well: MCI_INTEGER as currently used in mciav_res.rc is not adequate on 64bit. In the meantime, I'll submit a patch that adds MCI_HDC and a few other missing defines I know to the includes. Regards, Jörg Höhle -- 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 21

[Bug 39718] New: d3d9.dll trick for Fallout 3 no longer working in Steam
by wine-bugs＠winehq.org March 18, 2016

March 18, 2016

https://bugs.winehq.org/show_bug.cgi?id=39718 Bug ID: 39718 Summary: d3d9.dll trick for Fallout 3 no longer working in Steam Product: Wine Version: 1.7.55 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: b.adamski(a)mac.com Created attachment 52967 --> https://bugs.winehq.org/attachment.cgi?id=52967 Crash Log File In order to get Fallout 3 work with Intel graphic boards, a modified d3d9.dll file needs to be installed in the game directory: /Program Files/Bethesda Softworks/Fallout 3/d3d9.dll for the standalone version of Fallout 3. /Program Files/Steam/SteamApps/common/Fallout 3 goty/d3d9.dll or /Program Files/Steam/SteamApps/common/Fallout 3/d3d9.dll for the Steam version of Fallout 3. In addition the modified d3d9.dll file needs to get registered in winecfg. Add "d3d9 (native, builtin)" in the 'Libraries' tab. The trick worked perfectly fine until Steam released an update on August 19th 2015. With the new Steam version the trick does no longer work. Fallout 3 crashes when starting a new game or loading a save game. Please find the crash log attached. This is a different crash then the typical "new game crash" that the d3d9 trick is supposed to solve. There seems no impact from OS X or Wine engine updates. The standalone version of Fallout 3 is not affected, the trick still works absolutely fine here. I did not find any similar reports about Fallout 3 in Steam on Wine under Linux or natively in Steam on Windows. You can download the standalone wrapper version for OS X here: http://portingteam.com/files/file/8182-fallout-3-goty/ You can download the Steam wrapper version for OS X here: http://portingteam.com/files/file/8213-fallout-3-and-fallout-new-vegas-on-s… You find a forum discussion about the problem here: http://portingteam.com/topic/10637-fallout-3-d3d9dll-trick-for-intel-gpus-n… -- 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 41

[Bug 37949] New: eLicenser Control Center needs msvcr80.dll.__CxxExceptionFilter
by wine-bugs＠winehq.org March 18, 2016

March 18, 2016

https://bugs.winehq.org/show_bug.cgi?id=37949 Bug ID: 37949 Summary: eLicenser Control Center needs msvcr80.dll.__CxxExceptionFilter Product: Wine Version: 1.7.34 Hardware: x86 URL: https://web.archive.org/web/20130226012410/http://down load.elicenser.net/downloads/Archive/eLC_6.0.2.7036/eL icenserControlSetup.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 00cpxxx(a)gmail.com Distribution: --- To reproduce: 1) winetricks -q dotnet20 2) download and install the application 3) run c:/Program Files/Syncrosoft/LCC/eLCC.exe 4) press "Enter Activation Code" 5) hold a keyboard key until after all mask input is completed. wine: Call from 0x7b83b705 to unimplemented function msvcr80.dll.__CxxExceptionFilter, aborting I see bug 34841 for msvcr90 and bug 35657 for msvcr110 so I understand that each dll should have its own bug. If this is not true the bug can be closed as duplicate. -- 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 39239] New: ole32:compobj fails if privileges not high enough
by wine-bugs＠winehq.org March 18, 2016

March 18, 2016

https://bugs.winehq.org/show_bug.cgi?id=39239 Bug ID: 39239 Summary: ole32:compobj fails if privileges not high enough Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The following errors systematically happen when running the test without elevated privileges on a Windows 7 box such as the fg-win7u64-1spie9adm and fg-win7u64-1spie9usr WineTest boxes. compobj.c:1269: Test failed: RegCreateKeyEx returned 5 compobj.c:1272: Test failed: RegCreateKeyEx returned 6 compobj.c:1274: Test failed: RegSetValueEx returned 6 compobj.c:1278: Test failed: CoGetPSClsid failed with error 0x80040155 compobj.c:1279: Test failed: got clsid {00000000-0000-0000-0000-000000000000} compobj.c:1282: Test failed: RegDeleteKeyEx returned 6 compobj.c:1285: Test failed: RegDeleteKeyEx returned 2 The error code (ERROR_ACCESS_DENIED) clearly indicates a permissions issue. The tests regression was introduced by the following commit: commit fae8d9db5f3dcbec198d1a4cde6c9cfe8684b5cf Author: Akihiro Sagawa <sagawa.aki(a)gmail.com> Date: Tue Jul 15 19:34:38 2014 +0900 ole32/tests: Add CoGetPSClsid WOW64 registry tests. -- 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 40115] New: ole32:compobj regression (privilege issue)
by wine-bugs＠winehq.org March 18, 2016

March 18, 2016

https://bugs.winehq.org/show_bug.cgi?id=40115 Bug ID: 40115 Summary: ole32:compobj regression (privilege issue) Product: Wine Version: 1.9.3 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The commit below introduces 25 new failures when it is run without elevated privileges such as on the fg-win7u64-1spie9adm and fg-win7u64-1spie9usr VMs. New failures: compobj.c:2308: Test failed: failed to create a key 5, error 1008 compobj.c:2311: Test failed: got 6, error 1008 compobj.c:2314: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2322: Test failed: got 6, error 1008 compobj.c:2325: Test failed: got 6, error 1008 compobj.c:2331: Test failed: got 0x80040154 compobj.c:2332: Test failed: got (null) compobj.c:2337: Test failed: got 0x80040154 compobj.c:2338: Test failed: got (null) compobj.c:2343: Test failed: got 0x80040154 compobj.c:2344: Test failed: got (null) compobj.c:2349: Test failed: got 0x80040154 compobj.c:2350: Test failed: got (null) compobj.c:2355: Test failed: got 0x80040154 compobj.c:2356: Test failed: got (null) compobj.c:2361: Test failed: got 0x80040154 compobj.c:2362: Test failed: got (null) ole32:compobj results on test.winehq.org: https://test.winehq.org/data/tests/ole32:compobj.html commit 8fe18a16f7f5e0326d2fe6ab32ef2aad947b343d Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Wed Dec 30 23:48:38 2015 +0300 ole32: Properly implement OleRegGetUserType(). Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 22533] New: Half Life: loading screen rendering is wrong
by wine-bugs＠winehq.org March 18, 2016

March 18, 2016

http://bugs.winehq.org/show_bug.cgi?id=22533 Summary: Half Life: loading screen rendering is wrong Product: Wine Version: 1.1.43 Platform: x86-64 OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=27624) --> (http://bugs.winehq.org/attachment.cgi?id=27624) screenshot See attached screenshot. Terminal output is minimal: fixme:win:EnumDisplayDevicesW ((null),0,0x32e298,0x00000000), stub! fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 fixme:mci:MCI_Break (0102) vkey 001B stub ALSA lib ../../../src/pcm/pcm.c:7234:(snd_pcm_recover) underrun occured fixme:mci:MCI_Break (0102) vkey 001B stub ALSA lib ../../../src/pcm/pcm.c:7234:(snd_pcm_recover) underrun occured fixme:win:LockWindowUpdate (0x30052), partial stub! fixme:win:LockWindowUpdate ((nil)), partial stub! fixme:win:LockWindowUpdate (0x30052), partial stub! fixme:win:LockWindowUpdate ((nil)), partial stub! -- 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 29

[Bug 39674] New: 3Dmark03, 05, 06 not started "Systen Info Error" (double regression)
by wine-bugs＠winehq.org March 18, 2016

March 18, 2016

https://bugs.winehq.org/show_bug.cgi?id=39674 Bug ID: 39674 Summary: 3Dmark03, 05, 06 not started "Systen Info Error" (double regression) Product: Wine Version: 1.7.55 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Created attachment 52897 --> https://bugs.winehq.org/attachment.cgi?id=52897 how the stop looks Since wine-1.7.55 the Futuremark applications 3DMark03, 3DMark05, 3DMark06 stop working with messages "System Info error" or "unhandled exception". With wine 1.7.54 they are working. Regression test give the follow ~~~ quote ~~~ $ git bisect bad f91a7b2cfe5b44fea333ed70b9fc38a509b7798a is the first bad commit commit f91a7b2cfe5b44fea333ed70b9fc38a509b7798a Author: Austin English <austinenglish(a)gmail.com> Date: Wed Nov 4 10:46:50 2015 -0800 fltmgr.sys: Add FltInitializePushLock stub. Signed-off-by: Austin English <austinenglish(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 9a8f22f1f54f0af7b77216ea29b6360699eacb7e 5185e955c2cb2fe5ca9fa65034af095a9137d23a M dlls :040000 040000 a04028464398c6fceebbbe76e03446a3c2b8cb35 637e2081747c7c533f27d2a0f4ab1258d53bf9fa M include ~~~ quote ~~~ Meanwhile there is double regression as I notice in bug 36548. First regression was 1.7.54 working 1.7.54-140-7fbf33f hang at start. This regression reported and bisecting in 36548. commit 8cc5b07e9d0aedffd4251d2e8942cb8368920bf8 Second regression 1.7.54-134-gd4664c1 works but hang on exit 1.7.55 not working with the message. See attached screenshot. This regression I bisecting here. Strange to see this commit as regression. Analysis. Then I found a key difference in logs. Working log contains: ---- fixme:process:GetLogicalProcessorInformationEx (65535,0x9f6048,0x8beb54): stub ---- Non-working ---- fixme:process:GetLogicalProcessorInformationEx (65535,0x0,0x5203e8): stub ---- Note: second argument is ZERO. 3DMark application works in conjunction with Futuremarks SystemInfo (called by OLE?) and I may propose the SystemInfo calls the function but in second case it will not allocate buffer for CPU info. BOOL WINAPI GetLogicalProcessorInformationEx(LOGICAL_PROCESSOR_RELATIONSHIP relationship, PSYSTEM_LOGICAL_PROCESSOR_INFORMATION_EX buffer, PDWORD pBufLen) Why? Because there are new stubs? This procedure should return false if no buffer? Or this procedure should allocate this buffer? -- 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 40

[Bug 32314] New: Pikachu Volleyball (English version) crashes on restart
by wine-bugs＠winehq.org March 18, 2016

March 18, 2016

http://bugs.winehq.org/show_bug.cgi?id=32314 Bug #: 32314 Summary: Pikachu Volleyball (English version) crashes on restart Product: Wine Version: 1.5.18 Platform: x86-64 URL: http://games.hotut.com/post/pikachu-volleyball/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Classification: Unclassified Regression SHA1: 010019df064cfe1e9efee5ac6ee9e1e0954bd4f8 Created attachment 42654 --> http://bugs.winehq.org/attachment.cgi?id=42654 Terminal output The English version of Pikachu Volleyball crashes if restarted after the beginning of a round. (No problem with the original Japanese version.) To reproduce: - Start a game with either option at the title screen - Click Game -> Restart It also restarts (and crashes) automatically at the end of the round. Regression testing indicated: 010019df064cfe1e9efee5ac6ee9e1e0954bd4f8 is the first bad commit commit 010019df064cfe1e9efee5ac6ee9e1e0954bd4f8 Author: Jörg Höhle <Joerg-Cyril.Hoehle(a)t-systems.com> Date: Thu Oct 4 12:34:07 2012 +0200 mciseq: Create player thread in the synchronous case too. :040000 040000 4fecac2de61d692b36b829591062060ce25e861b 66bc6ddfb6dd3eddd0179ac2c98e887a3046dd31 M dlls Reverting that patch prevented the crash. -- 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