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

[Bug 35017] New: Rollercoaster Tycoon 3, steam version, no music
by wine-bugs＠winehq.org Jan. 29, 2021

Jan. 29, 2021

http://bugs.winehq.org/show_bug.cgi?id=35017 Bug #: 35017 Summary: Rollercoaster Tycoon 3, steam version, no music Product: Wine Version: 1.7.7 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: legluondunet(a)free.fr Classification: Unclassified Hello, Rollercoaster Tycoon 3 has no background music at all. On the WineHQ I did read there is a workaround for this: convert wma files from this directory: ".../drive_c/Program Files/Steam/SteamApps/common/Rollercoaster Tycoon 3 Gold/Music" to mp3. but it doesn't work. I tried to convert them to wav format too, but it doesn't run either. Finally I do a winetricks quartz...still no success. Thank you for your help. LGDN. -- 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.

2 20

[Bug 49327] New: Hearthstone Deck Tracker (with installed dotnet472) does not work with wine-staging 5.9 anymore
by WineHQ Bugzilla Jan. 29, 2021

Jan. 29, 2021

https://bugs.winehq.org/show_bug.cgi?id=49327 Bug ID: 49327 Summary: Hearthstone Deck Tracker (with installed dotnet472) does not work with wine-staging 5.9 anymore Product: Wine Version: 5.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: priit(a)ww.ee Distribution: --- Hearthstone Deck Tracker (with installed dotnet472 via winetricks) does not work with wine-staging 5.9-1 in Manjaro repos anymore. Does work perfectly enough with 5.8-1 wine-staging. Using winearch=win32 -- 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 21038] New: BlackLight: crash after accepting license agreement
by wine-bugs＠winehq.org Jan. 29, 2021

Jan. 29, 2021

http://bugs.winehq.org/show_bug.cgi?id=21038 Summary: BlackLight: crash after accepting license agreement Product: Wine Version: 1.1.34 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: alex(a)stanev.org Created an attachment (id=25234) --> (http://bugs.winehq.org/attachment.cgi?id=25234) BlackLight crash traces This standalone(no installer) application crashes on startup, right after accepting license agreement. Attaching traces. -- 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.

2 18

[Bug 42913] New: Wine is not able to run ACAT ( Assistive Context-Aware Toolkit)
by wine-bugs＠winehq.org Jan. 29, 2021

Jan. 29, 2021

https://bugs.winehq.org/show_bug.cgi?id=42913 Bug ID: 42913 Summary: Wine is not able to run ACAT (Assistive Context-Aware Toolkit) Product: Wine Version: 2.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rafaelrodrigues.machado(a)gmail.com Distribution: --- Hi everyone Most of you probably know Stephen Hawking, and also know that we has a computer that speaks for him. This software he uses is the ACAT (Assistive Context-Aware Toolkit), that was developed by Intel and was released as free software some time ago. My wife works with person with desabilities, and now I see that there s a lot of people that need to use this software, so they can communicate. I'd like to make ACAT works on a linux system so it'll be easier for everyone so they don't need to expend more money with windows. The setup consist of installing ACAT: https://github.com/01org/acat/releases/download/v1.00.0/ACATSetup.exe And after that, if needed, install a language package, for example: https://github.com/01org/acat/releases/download/v1.00.0/ACATPack-Portuguese… My OS is a Mint 18.1. When running Acat.exe within mint, the installation seems to be ok, but when I try to execute it I face this: rafael(a)HP-Notebook ~/Downloads $ wine ACAT wine: cannot find L"C:\\windows\\system32\\ACAT.exe" Wine version: rafael(a)HP-Notebook ~/Downloads $ wine --version wine-2.0.1 Please help me to make ACAT work at linux and let's help those that really need help. Any question I'll be here to help on everything I can. I don't have too much time because I'm working on my Mastering degree, but I'll do my best to feedback every time you need. Thanks for the amazing project! -- 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.

2 11

[Bug 50194] New: x64dbg snapshots >= 2020-11-12_05-12 crashes on unimplemented function ntdll.dll.NtCreateDebugObject when attaching to process
by WineHQ Bugzilla Jan. 29, 2021

Jan. 29, 2021

https://bugs.winehq.org/show_bug.cgi?id=50194 Bug ID: 50194 Summary: x64dbg snapshots >= 2020-11-12_05-12 crashes on unimplemented function ntdll.dll.NtCreateDebugObject when attaching to process Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. I've reported it to x64dbg project as well since they switched the debug engine implementation to use native API for attaching to processes. https://github.com/x64dbg/x64dbg/issues/2525 Copy/pasta from there: ... Symptom: attaching to any 32-bit or 64-bit process results in x32dbg/x64dbg crash. If x32dbg/x64dbg is registered as default crash handler you get a nice debugger crash "fork" bomb ;-) It crashes on unimplemented NtCreateDebugObject() which is native API. https://source.winehq.org/git/wine.git/blob/40d4fbe45997a1820296e7909ba2212… --- snip --- 162 # @ stub NtCreateDebugObject --- snip --- Even with a small stub it wouldn't work because NtDebugActiveProcess is a stub as well. https://source.winehq.org/git/wine.git/blob/40d4fbe45997a1820296e7909ba2212… The native API used to implement remote breakin: https://github.com/x64dbg/TitanEngine/blob/91f57815c886d6bef94f1b512d60c5e2… --- snip --- static NTSTATUS NTAPI DbgUiConnectToDbg_() { if(NtCurrentTeb()->DbgSsReserved[1] != NULL) return STATUS_SUCCESS; OBJECT_ATTRIBUTES ObjectAttributes; InitializeObjectAttributes(&ObjectAttributes, NULL, 0, NULL, NULL); return NtCreateDebugObject(&NtCurrentTeb()->DbgSsReserved[1], DEBUG_ALL_ACCESS, &ObjectAttributes, 0); } // Source: https://github.com/mirror/reactos/blob/c6d2b35ffc91e09f50dfb214ea5823750932… BOOL WINAPI DebugActiveProcess_(IN DWORD dwProcessId) { /* Connect to the debugger */ NTSTATUS Status = DbgUiConnectToDbg_(); if(!NT_SUCCESS(Status)) { BaseSetLastNTError(Status); return FALSE; } /* Get the process handle */ HANDLE Handle = ProcessIdToHandle(dwProcessId); if(!Handle) { return FALSE; } /* Now debug the process */ Status = DbgUiDebugActiveProcess_(Handle); /* Close the handle since we're done */ NtClose(Handle); /* Check if debugging worked */ if(!NT_SUCCESS(Status)) { /* Fail */ BaseSetLastNTError(Status); return FALSE; } /* Success */ return TRUE; } --- snip --- Apparently this debugging functionality which makes use of native API was switched to being a debug engine default here: https://github.com/x64dbg/TitanEngine/commit/0a1c3236b84ab1e6022116e38df1cc… ("Make SafeAttach the default") Previously it could be controlled by *SafeAttach* config setting which is still there but now no longer usable: https://github.com/x64dbg/x64dbg/blob/dad16543c320640fe681b8d897235bf8d6c30… --- snip --- SetEngineVariable(UE_ENGINE_SAFE_ATTACH, settingboolget("Engine", "SafeAttach")); --- snip --- A workaround exists: use the last snapshot before the breaking change: https://sourceforge.net/projects/x64dbg/files/snapshots/snapshot_2020-11-05… As already mentioned a simple stub prevents the crash but doesn't make debugging work. --- snip --- $ wine ./x32dbg.exe ... 0144:fixme:process:NtCreateDebugObject (0x7ff72f24 1f000f 0x614fe78 0), stub! 0144:fixme:process:NtDebugActiveProcess (0x214 (nil)), stub! --- snip --- I will create follow-up bug(s) to cover the missing functionality. $ sha1sum snapshot_2020-11-12_05-12.zip 6e88d4ce8fb967d08b381084f9ab805e5bcc4f18 snapshot_2020-11-12_05-12.zip $ du -sh snapshot_2020-11-12_05-12.zip 32M snapshot_2020-11-12_05-12.zip $ wine --version wine-5.22-96-g4957599bbf5 Regards -- 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 50229] New: Battle.net launcher sometimes crashes after login (wine-5.22)
by WineHQ Bugzilla Jan. 29, 2021

Jan. 29, 2021

https://bugs.winehq.org/show_bug.cgi?id=50229 Bug ID: 50229 Summary: Battle.net launcher sometimes crashes after login (wine-5.22) Product: Wine-staging Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68736 --> https://bugs.winehq.org/attachment.cgi?id=68736 STDOUT / STDERR log Since upgrading from wine-staging-5.21*, the Battle.net launcher crashes after login in about 1 of 3 times. After the crash, the Blizzard crash reporter comes up. I've enabled the virtual desktop via winecfg and I'm running Battle.net by executing: explorer.exe /desktop=shell,1920x1080 "C:\\Program Files (x86)\\StarCraft II\\StarCraft II.exe" I'm using a dual monitor setup. And I think the crash might only happen if I move the mouse out of the virtual desktop to my second monitor AFTER entering my password in the Battle.net login dialog. Sadly the bug isn't completely deterministic. So I need some more time for detailed testing. Wine version: wine-staging-5.22** I've attached the STDOUT / STDERR log, created with: WINEDEBUG=+pid,+loaddll,+timestamp,+seh *including patches for: https://bugs.winehq.org/show_bug.cgi?id=49782 https://bugs.winehq.org/show_bug.cgi?id=50110 **including patches for: https://bugs.winehq.org/show_bug.cgi?id=49782 -- 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 18

[Bug 49484] New: test_query_process_image_info() test is broken on a not PE build
by WineHQ Bugzilla Jan. 29, 2021

Jan. 29, 2021

https://bugs.winehq.org/show_bug.cgi?id=49484 Bug ID: 49484 Summary: test_query_process_image_info() test is broken on a not PE build Product: Wine Version: 5.11 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dmitry(a)baikal.ru Distribution: --- Steps to reproduce: cd wine/dlls/ntdll/tests make info.ok info.c:1843: Test failed: got c0000019 info.c:1846: Test failed: wrong major version cccc/4 info.c:1848: Test failed: wrong minor version cccc/0 In fact it never worked from the point when it was added: commit 54a7e592e44622ecd61160498fb5148a46b2e8db Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue May 26 13:23:21 2020 +0200 ntdll: Implement ProcessImageInformation class in NtQueryInformationProcess(). It looks like in a not PE build process->views on the server side is always empty, and as a result mapping.c,find_mapped_view() returns NOT_MAPPED_VIEW. There's no a single DLL in the process->views, and that's a real regression, probably caused by the movement to PE/ntdll unixlib introduction. -- 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 48790] New: mfplat:mfplat crashes on Windows 7
by WineHQ Bugzilla Jan. 29, 2021

Jan. 29, 2021

https://bugs.winehq.org/show_bug.cgi?id=48790 Bug ID: 48790 Summary: mfplat:mfplat crashes on Windows 7 Product: Wine Version: 5.2 Hardware: x86 OS: Linux Status: NEW Keywords: regression, source, testcase Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: dereklesho52(a)Gmail.com Regression SHA1: b7047b5ae9fc84a6414db9bb80c4264b1550c7a0 Distribution: --- mfplat.c:1444: Tests skipped: Cannot retrieve IMFAttributes interface from IMFByteStream mfplat.c:527: this is the last test seen before the exception 03f8:mfplat: unhandled exception c0000005 at 70BF7243 -- 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 17848] New: Windows Print Preview: Lines drawn have incorrect width
by wine-bugs＠winehq.org Jan. 29, 2021

Jan. 29, 2021

http://bugs.winehq.org/show_bug.cgi?id=17848 Summary: Windows Print Preview: Lines drawn have incorrect width Product: Wine Version: 1.1.17 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: olsentest(a)comcast.net In Windows print preview, drawing commands embedded between BeginPath and EndPath have line widths that are way too wide. It appears that the same width (in pixels) is used in the print preview as was used for the main application window. Also, if you use the print preview zoom button, the line width remains the same, suggesting that it is not being adjusted for the changes in scale. If drawing commands are not embedded between BeginPath and EndPath, then the print preview appears to work correctly. I am attaching a screen capture of the main window and the print preview window. Also, I am attaching a simple Windows program that can be used for debug purposes. Also attached is a code snippet from the Windows program. -- 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.

2 14

[Bug 30469] New: crash in segflex
by wine-bugs＠winehq.org Jan. 29, 2021

Jan. 29, 2021

http://bugs.winehq.org/show_bug.cgi?id=30469 Bug #: 30469 Summary: crash in segflex Product: Wine Version: 1.5.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: daduck10(a)gmail.com Classification: Unclassified Created attachment 39845 --> http://bugs.winehq.org/attachment.cgi?id=39845 crash file and debug mode files The program segflex is crashing when I initialize it. I installed framework, because it needs to run. -- 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.

2 5