December 2017 - Wine-Bugs - list.winehq.org

[Bug 36849] New: eTax 2014 installation under Wine on Linux Mint 17 Qiana
by wine-bugs＠winehq.org Feb. 25, 2018

Feb. 25, 2018

http://bugs.winehq.org/show_bug.cgi?id=36849 Bug ID: 36849 Summary: eTax 2014 installation under Wine on Linux Mint 17 Qiana Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: davidcousens(a)bigpond.com Created attachment 48937 --> http://bugs.winehq.org/attachment.cgi?id=48937 Wine backtrace while trying to install Etax 2014 Hi, When trying to install the ATO eTax application under Wine on a Linux Mint 17 system the installation reported an an error with rundll32.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 17

[Bug 43654] New: Arx Fatalis: Candlelight / Porch light leaks through the walls
by wine-bugs＠winehq.org Feb. 25, 2018

Feb. 25, 2018

https://bugs.winehq.org/show_bug.cgi?id=43654 Bug ID: 43654 Summary: Arx Fatalis: Candlelight / Porch light leaks through the walls Product: Wine Version: 2.9 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 Distribution: --- Created attachment 59083 --> https://bugs.winehq.org/attachment.cgi?id=59083 lights through the wall Game works fine in wine-2.7. It's bit broken in wine-2.8 (some black frames with just porch light). Commit wine-2.8-212-g2ed609f15d fixes those black screens with porch light, but also intensifies those porch lights, that it leaks through the wall. Attachment shows that better. commit 2ed609f15da7c7f8bde54f6d4d895c72f96dd950 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Wed May 24 11:22:09 2017 +0200 wined3d: Add a conversion function for WINED3DFMT_X8D24_UNORM. Problems remain in current version (wine-2.16) -- 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 21085] New: Comctl32 status control uses tooltip window wrongly
by wine-bugs＠winehq.org Feb. 24, 2018

Feb. 24, 2018

http://bugs.winehq.org/show_bug.cgi?id=21085 Summary: Comctl32 status control uses tooltip window wrongly Product: Wine Version: 1.1.35 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: us(a)edmeades.me.uk I've been debugging a private application and tracked down the source of a trap to the way the status control initializes and uses the tooltip control. The application in question traps because it receives a WM_CREATE message for the tooltip window and calls GetWindowLong against an hwnd for a value it should have set earlier - this fails but the code doesnt notice, and results in a trap. On windows, the status control does not create the tooltip until the first WM_MOUSEMOVE event, and hence all application initialization would have finished in my case. You can clearly see this by use of a simple application with a statusbar control set to have a tooltip and text, and then use SPY++ to monitor the window creation messages. Note this also shows a 2nd problem which is that the status control passes the tooltip text to the tooltip window to manage. This is wrong, because using the status bar you can set and then get the tooltip text before the tooltip window is ever created. Additionally, SPY++ shows that the notify messages (NEEDTEXT type) are sent to the status window when the tooltip needs the text, both of which mean that the status control should manage the text. I have a simple application which has a button for get tip, set tip text, and using it you can see the behaviour above. It doesnt replicate the trap but you can see the behavious using it - you dont get a WM_CREATE for the tooltip until such time as you move the mouse into the statusbar area on windows. Simple workarounds for me: winetricks comctl32, or modifying the STATUSBAR_WMCreate method to something like "if (0 && dwStyle & SBT_TOOLTIPS) {" to prevent the tooltip altogether. JECC JECC -- 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 42049] New: VSphere install crashes with ntoskrnl.exe.KeWaitForMultipleObjects, " Failed to install the hcmon driver"
by wine-bugs＠winehq.org Feb. 24, 2018

Feb. 24, 2018

https://bugs.winehq.org/show_bug.cgi?id=42049 Bug ID: 42049 Summary: VSphere install crashes with ntoskrnl.exe.KeWaitForMultipleObjects, "Failed to install the hcmon driver" Product: Wine Version: 2.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com Distribution: --- As stated. The VSphere 6.0.0 installation crashes about halfway through with a popup titled "VMInstallHcmon" saying "Failed to install the hcmon driver". However, the console output reveals wine crashed due to an unimplemented "ntoskrnl.exe.KeWaitForMultipleObjects". The last few lines of output: regsvr32: Successfully registered DLL 'C:\Program Files (x86)\Common Files\VMware\VMware Remote Console Plug-in 5.5\Internet Explorer\vmwareRemoteConsole.dll' fixme:msvcrt:__clean_type_info_names_internal (0x11072b4c) stub fixme:heap:RtlSetHeapInformation 0x250000 0 0x23fdf0 4 stub fixme:heap:RtlSetHeapInformation 0x250000 0 0x23fdf0 4 stub fixme:heap:RtlSetHeapInformation 0x250000 0 0x23fdf0 4 stub fixme:ntoskrnl:IoWMIRegistrationControl (0x64a880 2147549185) stub fixme:ntoskrnl:IoCsqInitialize (0x156a8 0x64730c 0x64735c 0x647394 0x6473ec 0x647410 0x647424) stub fixme:ntoskrnl:KeInitializeEvent stub: 0x15630 0 0 fixme:ntoskrnl:KeInitializeEvent stub: 0x15648 0 0 fixme:ntoskrnl:KeInitializeEvent stub: 0x15660 0 0 fixme:ntoskrnl:IoRegisterPlugPlayNotification (2 0 0x649310 0x12fe0 0x6468e4 0x151c8 0x15698) stub fixme:ntoskrnl:IoRegisterPlugPlayNotification (2 1 0x6492b0 0x12fe0 0x646cf0 0x151c8 0x156a0) stub fixme:ntoskrnl:ObReferenceObjectByHandle stub: 0x3c 1f03ff 0x0 0 0x15678 0x0 wine: Call from 0x7b430d32 to unimplemented function ntoskrnl.exe.KeWaitForMultipleObjects, aborting wine: Unimplemented function ntoskrnl.exe.KeWaitForMultipleObjects called at address 0x7b430d32 (thread 00a0), starting debugger... -- 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 3

[Bug 43948] New: d3dx9 effects - pixel shader 2.0 does not render well
by wine-bugs＠winehq.org Feb. 22, 2018

Feb. 22, 2018

https://bugs.winehq.org/show_bug.cgi?id=43948 Bug ID: 43948 Summary: d3dx9 effects - pixel shader 2.0 does not render well Product: Wine Version: 2.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: havran.jan(a)email.cz Distribution: ArchLinux Created attachment 59587 --> https://bugs.winehq.org/attachment.cgi?id=59587 d3dx9 effects I have strange behaviour of effects in d3dx9 application where I have access to source code. I tried to reduce code size to the minimum where this bug is still reproduciable. The problem is, when I apply attached shaders.fx effects (VS + PS) on some objects (triangle for example), then the object is black in Wine, while in Windows or Gallium Nine it is grey. Here is list of configuration where it works as expected (expected = how it works on native Windows): Windows 7 + D3D9 + AMD graphics Windows 7 + D3D9 + Intel graphics Linux + Wine + Gallium Nine + AMD graphics (Mesa) Here is list of configuration where it does not work (renders black objects): Windows 7 + WineD3D + AMD graphics Windows 7 + WineD3D + Intel graphics Linux + Wine + WineD3D + AMD graphics (Mesa) Linux + Wine + WineD3D + Intel graphics (Mesa) There are possibly two issues in attached pixel shader: 1) uninitialized IN.lightVec 2) usage of normalize() function (and possible division by zero) But here is the strange behaviour: 1) when I set IN.lightVec red, green or blue to 0.0 (one or two of them, but not all of them, because it cause crash), then it is rendered black in Windows and in Wine as well. 2) when I set IN.lightVec.r (for example) to "IN.lightVec.r + 0.0f", then it has no effect. >From point 2 it looks like IN.lightVec default values are 0.0f, but from point 1 it looks opposite. So I have no idea what are values of uninitialized vector. I thought that it could be related to bug #34266 [1], but: 1) created patch did not work for me 2) when I set IN.lightVec to zero, the bug disappears I can upload simple d3d app which use these effect and also binary file (exe). I have no D3D (and D3D shaders) deep knowledge, so maybe I something understand wrong. I also used native d3dcompiler_43 so Wine could compile these shaders. [1] https://bugs.winehq.org/show_bug.cgi?id=34266 -- 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 39148] New: Guild Wars 2: Hangs on Close
by wine-bugs＠winehq.org Feb. 20, 2018

Feb. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=39148 Bug ID: 39148 Summary: Guild Wars 2: Hangs on Close Product: Wine Version: 1.7.50 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: soulhuntor(a)gmail.com Distribution: --- Guild Wars 2: Hangs on Close Starting with 1.7.50 when trying to close Guild Wars 2 the program looks like it closes but the Gw2.exe is still running. -- 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 24099] New: wine symbol font causes wrong pdf rendering in gnome and kde
by wine-bugs＠winehq.org Feb. 20, 2018

Feb. 20, 2018

http://bugs.winehq.org/show_bug.cgi?id=24099 Summary: wine symbol font causes wrong pdf rendering in gnome and kde Product: Wine Version: 1.3.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: fonts AssignedTo: wine-bugs(a)winehq.org ReportedBy: leighmanthegreat(a)hotmail.com from https://bugs.launchpad.net/ubuntu/+source/wine1.2/+bug/461233 When I open this pdf (attached) with evince, some formulas are rendered incorrectly (eg. p. 71). This also happens in Okular. Confirmed here wine 1.3. see also https://bugs.edge.launchpad.net/ubuntu/+source/wine1.2/+bug/605670 -- 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 36014] New: secur32/{negotiate,ntlm} tests fail with debian's samba/winbind 4
by wine-bugs＠winehq.org Feb. 19, 2018

Feb. 19, 2018

https://bugs.winehq.org/show_bug.cgi?id=36014 Bug ID: 36014 Summary: secur32/{negotiate,ntlm} tests fail with debian's samba/winbind 4 Product: Wine Version: 1.7.16 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Follow up to bug 35965. The secur32 tests fail on a default installation of samba/winbind4 on Debian 7 (wheezy): ../../../tools/runtest -q -P wine -T ../../.. -M secur32.dll -p secur32_test.exe.so negotiate && touch negotiate.ok WARNING: gnome-keyring:: couldn't connect to: /home/austin/.cache/keyring-mD4V6F/pkcs11: No such file or directory ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so) fixme:secur32:nego_AcquireCredentialsHandleW forwarding to NTLM fixme:secur32:nego_AcquireCredentialsHandleW forwarding to NTLM ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so) ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so) Unable to setup messaging listener for '/var/lib/samba/private/smbd.tmp/msg/msg.10803.179872511':NT_STATUS_OBJECT_NAME_NOT_FOUND negotiate.c:295: Test failed: server returned 80090304, more tests will fail negotiate.c:305: Tests skipped: authentication failed, skipping remaining tests negotiate.c:349: Test failed: DeleteSecurityContext returned 80090301 make: *** [negotiate.ok] Error 2 that lack of version information message seems bad, and makes the tests fail even worse later (in ntlm.c): ../../../tools/runtest -q -P wine -T ../../.. -M secur32.dll -p secur32_test.exe.so ntlm && touch ntlm.ok WARNING: gnome-keyring:: couldn't connect to: /home/austin/.cache/keyring-mD4V6F/pkcs11: No such file or directory ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so) .. ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so) =============================================================== INTERNAL ERROR: Signal 11 in pid 10826 (4.0.0beta2) Please read the Trouble-Shooting section of the Samba HOWTO =============================================================== PANIC: internal error but, as Dmitry points out in https://bugs.winehq.org/show_bug.cgi?id=35965#c9, the wiki says that only ntlm_auth needs to be available, nothing is said about the configuration: "To get access to all the features while using NtlmSigningAndSealing, you need an up-to-date version of ntlm_auth. Samba 3.0.26 or later will do. In some distributions, you need to install the "winbind" package to get ntlm_auth. If you want client mode NTLM for Wine, e.g. reading your email using Outlook over a connection with NTLM encryption, that's all you need. " -- 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 31393] New: Nvidia force antialiasing no longer works
by wine-bugs＠winehq.org Feb. 18, 2018

Feb. 18, 2018

http://bugs.winehq.org/show_bug.cgi?id=31393 Bug #: 31393 Summary: Nvidia force antialiasing no longer works Product: Wine Version: 1.5.10 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: b7.10110111(a)gmail.com Classification: Unclassified Regression SHA1: 09443f14e75e134328643b5d33aff61bdf4dca32 After AlwaysOffscreen has become enabled by default, games such as GTAIII and GTAVC (which are unaware of FSAA) can't benefit from nvidia antialiasing settings out of the box. I'm not sure if it's intended result, but despite it being possible to disable it back, new default seems no good to me as e.g. on Windows it's enough to set antialiasing in the driver utility and there's no need to change D3D configuration. Maybe wine should check whether default render target is multisampled and toggle the default? -- 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 43679] New: PDF-XChange's typewriter tool works only once
by wine-bugs＠winehq.org Feb. 18, 2018

Feb. 18, 2018

https://bugs.winehq.org/show_bug.cgi?id=43679 Bug ID: 43679 Summary: PDF-XChange's typewriter tool works only once Product: Wine Version: 2.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matteo.guglielmi(a)gmail.com Distribution: --- When using the 'typewriter' tool of pdf-xchange, which is used to add text on pdf pages, it works only the first time it is used (typewriter box appears and text can be typed in). >From the second time on, the typewriter box appears but it is not possible to type in any text. Also editing the first typewriter box does not work either. -- 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 19