July 2018 - Wine-bugs - list.winehq.org

[Bug 40965] New: Necropolis has messed up graphics when ran in DirectX 9 mode
by wine-bugs＠winehq.org 10 Nov '18

10 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=40965 Bug ID: 40965 Summary: Necropolis has messed up graphics when ran in DirectX 9 mode Product: Wine Version: 1.9.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- Created attachment 55114 --> https://bugs.winehq.org/attachment.cgi?id=55114 Terminal output wine-1.9.14-112-gfec0b69 I have made a clean 32-bit Windows 7 prefix with d3d11 disabled and the xinput1_3.dll installed as native to work around this bug: https://bugs.winehq.org/show_bug.cgi?id=40953 After loading, the game goes to the main menu and the graphics are completely off. I have tried installing native DirectX 9 via winetricks to see if that would help with the graphical issues but when I try to start the game I receive the following terminal output: wine Necropolis.exe err:module:import_dll Library DNSAPI.dll (which is needed by L"C:\\GOG Games\\Necropolis\\Necropolis.exe") not found err:module:LdrInitializeThunk Main exe initialization for L"C:\\GOG Games\\Necropolis\\Necropolis.exe" failed, status c0000135 The attached terminal output is from before I installed DX9 via winetricks. -- 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 31493] New: Dota 2: hero tooltip text is not rendered apprropriately
by wine-bugs＠winehq.org 10 Nov '18

10 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=31493 Bug #: 31493 Summary: Dota 2: hero tooltip text is not rendered apprropriately Product: Wine Version: 1.5.11 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: phoenix(a)mail.ru Classification: Unclassified Created attachment 41401 --> http://bugs.winehq.org/attachment.cgi?id=41401 Corrupted tooltip above Mirana Repro: 1. Start/watch dota 2 game 2. Hover cursor over hero 3. Observe tooltip which appears above it Result: Tooltip text is not shown, see screenshot. As you play game, some letters may randomly appear there (correct letters in correct positions, but they don't appear one-by-one from left to right or all together). Expected: Tooltip should show hero class and hero level. -- 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 24518] New: Civilization V start menu has style issues
by wine-bugs＠winehq.org 10 Nov '18

10 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=24518 Summary: Civilization V start menu has style issues Product: Wine Version: 1.3.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: adys.wh(a)gmail.com Created an attachment (id=30950) --> (http://bugs.winehq.org/attachment.cgi?id=30950) Wine screenshot See attached screenshots. -- 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 30064] New: readbook.exe crash on exit
by wine-bugs＠winehq.org 10 Nov '18

10 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=30064 Bug #: 30064 Summary: readbook.exe crash on exit Product: Wine Version: 1.4-rc6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Classification: Unclassified 1. Download readbook http://dl-sh-ocn-1.pchome.net/03/um/RB_Setup_Plus1.51.zip 2. unzip and install $ wine RB_Setup_Plus1.51.exe always select "next"/"下一步" 3. Start readbook $ cd .wine/drive_c/ReadBOOK $ wine ReadBook.exe A configure wizard dialog will popup in the first time starting readbook.exe click "Cancel"/"取消" to workaroudn Bug 30063 4. click "知道了"/"I know" 5. click file -> exit Readbook.exe crash on exit. However, I'm not sure if this is really a wine bug. On my winxp box, it crash on exit as well. Maybe it doesn't crash on some version of Windows? It will be great if somebody double checks. Thanks. -- 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 38179] New: directdraw game can be lanched, but hangs after click "new game" button from main menu
by wine-bugs＠winehq.org 10 Nov '18

10 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=38179 Bug ID: 38179 Summary: directdraw game can be lanched, but hangs after click "new game" button from main menu Product: Wine Version: 1.7.37 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gamiljydcome(a)gmail.com Distribution: --- directdraw game can be lanched, but hangs after click "new game" button from main menu i try to play a old arpg game 三国赵云传 in virtual desktop. after i click "new game" button from main menu, the game show some intro messages, then, long waiting, it hangs. i have to terminate it by alt-f4. it is not complete hangs, i can still hear music, but keybord/mouse gone. i can confirm this app stopped peek keybord message, until game show intro messages over. this is wrong, it should be interruped by enter ESC key, then show next scene. but, hangs. i think this game use some old ddraw way to render, but go into some kind of infinite loop or something, cause keybord/mosue gone, noting render to screen. i have tested this game with wine version 1.6~1.7.37, the issue is same. maybe it is a wine bug. -- 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 16265] New: ActiveX Control Pad installer hangs sometimes on exit; deadlock between LdrShutdownThread and TASK_ExitTask?
by wine-bugs＠winehq.org 10 Nov '18

10 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=16265 Summary: ActiveX Control Pad installer hangs sometimes on exit; deadlock between LdrShutdownThread and TASK_ExitTask? Product: Wine Version: 1.1.9 Platform: Other URL: http://msdn.microsoft.com/en-us/library/ms968493.aspx OS/Version: other Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com A user said that ConvWPT ran in Wine, but gave a very complicated recipe, so I tried simplifying it. Along the way, I noticed that Microsoft's ActiveX Control Pad installer hangs sometimes on exit. Here's how to reproduce: 1) Do "winetricks wsh56", else "winetricks fm20" will fail with dialog "Setup has determined that Microsoft Internet Explorer 3.0 was not detected." 2) Do "winetricks fm20". This will complain "Setup was unable to start DDE communication with the desktop". Click Ignore. (This is probably bug 9159.) When the installer is done, it sometimes hangs with err:ntdll:RtlpWaitForCriticalSection section 0x7ef2b3c0 "syslevel.c: Win16Mutex" wait timed out in thread 002f, blocked by 002e, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x7efec5e4 "loader.c: loader_section" wait timed out in thread 002e, blocked by 002f, retrying (60 sec) Using winedbg, I was able to get a backtrace of those threads by pressing ^C and then using the bt command: Wine-dbg>bt 0x2e Backtrace: =>1 RtlpWaitForCriticalSection+0x2fd(crit=0x7efec5e4) [dlls/ntdll/critsection.c:64] in ntdll 2 RtlEnterCriticalSection+0x4a(crit=<?>) [dlls/ntdll/critsection.c:553] in ntdll 3 LdrShutdownThread+0x49() [dlls/ntdll/loader.c:2160] in ntdll 4 RtlExitUserThread+0x67(status=<?>) [dlls/ntdll/thread.c:628] in ntdll 5 in kernel32 (+0x74ca6) 6 DOSVM_Int21Handler+0x9a17(context=0x7e56638c) [dlls/winedos/int21.c:3192] in winedos 7 DOSVM_CallBuiltinHandler+0x17(context=0x7e56638c, intnum=<?>) [dlls/winedos/interrupts.c:712] in winedos 8 INSTR_CallBuiltinHandler+0x3c(context=0x7e56638c, intnum=<?>) [dlls/kernel32/instr.c:901] in kernel32 9 DOS3Call+0x25(context=0x7e56638c) [dlls/kernel32/instr.c:911] in kernel32 ... Wine-dbg>bt 0x2f Backtrace: =>1 RtlpWaitForCriticalSection+0x2fd(crit=0x7ef2b3c0) [dlls/ntdll/critsection.c:64] in ntdll 2 RtlEnterCriticalSection+0x4a(crit=<?>) [dlls/ntdll/critsection.c:553] in ntdll 3 _EnterSysLevel+0x7b(lock=0x7ef2b3c0) [dlls/kernel32/syslevel.c:106] in kernel32 4 _EnterWin16Lock+0x20() [dlls/kernel32/syslevel.c:187] in kernel32 5 TASK_ExitTask+0x19() [dlls/kernel32/task.c:564] in kernel32 6 DllMain+0x75(hinst=0x7ee10000, reason=3, reserved=(nil)) [dlls/kernel32/kernel_main.c:212] in kernel32 7 __wine_spec_dll_entry+0x3e(inst=0x7ee10000, reason=<?>, reserved=<?>) [dlls/winecrt0/dll_entry.c:40] in kernel32 8 call_dll_entry_point+0x15() in ntdll 9 MODULE_InitDLL+0xe3(wm=<?>, reason=3, lpReserved=(nil)) [dlls/ntdll/loader.c:912] in ntdll 10 LdrShutdownThread+0x96() [dlls/ntdll/loader.c:2163] in ntdll 11 RtlExitUserThread+0x67(status=<?>) [dlls/ntdll/thread.c:628] in ntdll 12 in kernel32 (+0x74ca6) 13 WINOLDAP_EntryPoint+0x1a2(context=0x7d7b138c) [dlls/kernel32/kernel16.c:207] in kernel32 ... -- 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 39249] New: AMD and Intel problem O2Jam Black Screen problem
by wine-bugs＠winehq.org 09 Nov '18

09 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=39249 Bug ID: 39249 Summary: AMD and Intel problem O2Jam Black Screen problem Product: Wine Version: 1.7.51 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: onte_jc(a)yahoo.com AMD and Intel problem O2Jam Black Screen problem http://o2jam.intgamerz.net Running O2Jam in AMD or Intel Graphics will stuck the game, black screen, not runnable anymore Nvidia is working fine w/o any problems at all -- 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 10

[Bug 41269] New: MSI uninstaller does not clean up Registry's UpgradeCode, ProductCode
by wine-bugs＠winehq.org 09 Nov '18

09 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=41269 Bug ID: 41269 Summary: MSI uninstaller does not clean up Registry's UpgradeCode, ProductCode Product: Wine Version: 1.9.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: reinhold.hoffmann(a)hotmail.com Distribution: --- Created attachment 55569 --> https://bugs.winehq.org/attachment.cgi?id=55569 What needs to be deleted in the Registry when de-installing When uninstalling an installed Wine app the uninstaller de-installs the app accurately but it does not clean up the UgradeCode and ProductCode in the Registry. In an subsequent installation when the same app (same UpgradeCode, different ProductCode, higher version number) is installed, the MSI option "RemoveExistingProducts" fails. "RemoveExistingProducts" should automatically de-install a former version before the new version is installed. As a consequence always the former version needs to be manually de-install BEFORE the new version otherwise the next installation fails. In addition the Windows call "MsiEnumRelatedProducts" finds a product which does not exist anymore. De-installing with "MsiConfigureProduct (parameter=ProductCode, INSTALLLEVEL_DEFAULT, INSTALLSTATE_ABSENT)" does not work either. Because the MSI uninstaller leaves all ProductCodes of former installations in place forever, the Registry get screwed and is not in sync to what really is installed. This is a big issue for almost every our customer when installing updates or upgrade. Always, the former installation has to be manually de-installed because "RemoveExistingProducts" always fails. We have detected this issue in a deep dive and see this bug to be the biggest issue for our customers for a broader use of our software on Wine. Therefore set this bug to be critical. Please find attached what needs to be deleted in the Registry when the uninstaller de-installs a software. The bug happens for Ubuntu, openSuSE, Mac OS X Reinhold -- 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 52

[Bug 42550] New: Photoshop CC 2017: Installation Error
by wine-bugs＠winehq.org 09 Nov '18

09 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=42550 Bug ID: 42550 Summary: Photoshop CC 2017: Installation Error Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jf(a)grafik-service.info Distribution: --- Created attachment 57454 --> https://bugs.winehq.org/attachment.cgi?id=57454 Install Log Using this Installer: https://download-esd.adobeoobe.com/AdobeProducts/eca60e6c-1f05-41de-bf6b-ae… sha1: 329402f2358b8db7c01c405993a1e5d75ea6a468 it gets to about 30 %, then throws an 'unknown error' with code 1. -- 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 9

[Bug 44620] New: `Nt{WaitFor,Release}KeyedEvent()` don' t accept null handles, while Windows 7 does.
by wine-bugs＠winehq.org 09 Nov '18

09 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=44620 Bug ID: 44620 Summary: `Nt{WaitFor,Release}KeyedEvent()` don't accept null handles, while Windows 7 does. Product: Wine Version: 3.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: lh_mouse(a)126.com Distribution: --- Created attachment 60609 --> https://bugs.winehq.org/attachment.cgi?id=60609 testcase Testcase (also attached as 'ntwaitforkeyedevent.c'): ------ #include <winternl.h> #include <winnt.h> #include <stdio.h> __attribute__((__dllimport__, __stdcall__)) extern NTSTATUS NtWaitForKeyedEvent(HANDLE hKeyedEvent, void *pKey, BOOLEAN bAlertable, const LARGE_INTEGER *pliTimeout); int main(void){ LARGE_INTEGER liTimeout; NTSTATUS lStatus; liTimeout.QuadPart = -10000000; printf("Waiting...\n"); lStatus = NtWaitForKeyedEvent(NULL, &lStatus, FALSE, &liTimeout); printf("NtWaitForKeyedEvent() returned %08lx\n", lStatus); return 0; } ------ Compiling and running this program on Linux Mint 18.3 results in the following output: ------ lh_mouse(a)lhmouse-ideapad-720S ~/桌面 $ x86_64-w64-mingw32-gcc ntwaitforkeyedevent.c -Wall -Wextra -Wpedantic -lntdll && ./a.exe Waiting... NtWaitForKeyedEvent() returned c0000008 lh_mouse(a)lhmouse-ideapad-720S ~/桌面 $ wine --version wine-3.0 lh_mouse(a)lhmouse-ideapad-720S ~/桌面 $ ------ On Windows 7 `NtWaitForKeyedEvent()` returns `STATUS_TIMEOUT` i.e. it succeeds: ------ E:\Desktop>x86_64-w64-mingw32-gcc ntwaitforkeyedevent.c -Wall -Wextra -Wpedantic -lntdll && a.exe Waiting... NtWaitForKeyedEvent() returned 00000102 ------ Passing null handles to `Nt{WaitFor,Release}KeyedEvent()` is how SRW locks and condition variables are implemented on Windows 7. I presume that a handle to the preallocated global keyed event with the name '\KernelObjects\CritSecOutOfMemoryEvent' is used in this case. At the moment <https://github.com/lhmouse/mcfgthread> expects the Windows behavior and fails in Wine. -- 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