September 2021 - Wine-bugs - list.winehq.org

[Bug 51120] New: MCC DAQ software setup crashes in vbscript exec_script function
by WineHQ Bugzilla 20 Sep '21

20 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51120 Bug ID: 51120 Summary: MCC DAQ software setup crashes in vbscript exec_script function Product: Wine Version: 6.8 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 69987 --> https://bugs.winehq.org/attachment.cgi?id=69987 WINEDEBUG=+vbscript The installer's self-extraction succeeds and the installation wizard starts, but it crashes during the actual install step. Since the crash happens inside of Wine's vbscript.dll, I am attaching a console log with WINEDEBUG=+vbscript. $ sha256sum mccdaq.exe 12eb3e9422e333155977bfd43cb87b3c27826847dfc85998a9c2a52906410312 -- 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 51497] New: Mouse cursors are broken in Photoshop CS2 and Photoshop 7.0
by WineHQ Bugzilla 20 Sep '21

20 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51497 Bug ID: 51497 Summary: Mouse cursors are broken in Photoshop CS2 and Photoshop 7.0 Product: Wine Version: 6.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 70338 --> https://bugs.winehq.org/attachment.cgi?id=70338 Photoshop CS2 in Wine 6.13 This has been an issue in at least Wine 6.12 and 6.13. Photoshop CS2 has been free for quite some time now, so you can test and see it yourself. -- 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 51771] New: XnView crashes when DefaultDepth is set to 30
by WineHQ Bugzilla 19 Sep '21

19 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51771 Bug ID: 51771 Summary: XnView crashes when DefaultDepth is set to 30 Product: Wine Version: 6.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Steps to reproduce: 1) Xorg: Section "Screen" DefaultDepth 30 EndSection 2) Download and run XnView 3) Crash -- 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 1

[Bug 51769] New: ClientSideGraphics=N with 30-bit color depth makes all graphical applications crash
by WineHQ Bugzilla 19 Sep '21

19 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51769 Bug ID: 51769 Summary: ClientSideGraphics=N with 30-bit color depth makes all graphical applications crash Product: Wine Version: 6.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- If ClientSideGraphics=N and Xorg->DefaultDepth=30 all graphical Windows applications crash on startup. BTW I enabled this option a long time ago and I've no idea why. Does anyone know if this option is still beneficial for anything in 2021? Or it's been deprecated a long time ago? wine: Unhandled page fault on read access to FFFF0000 at address FFFF0000 (thread 0024), starting debugger... winedbg: Internal crash at 0xffff0000 $ winedbg winecfg WineDbg starting on pid 011c 0x7bc7a9e1: ret Wine-dbg>cont Unhandled exception: page fault on execute access to 0xffff0000 in 32-bit code (0xffff0000). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:ffff0000 ESP:0021e7bc EBP:0021e828 EFLAGS:00010206( R- -- I - -P- ) EAX:7cd64490 EBX:0028ee90 ECX:0028f0d8 EDX:00000047 ESI:0028f0d8 EDI:00000000 Stack dump: 0x0021e7bc: 7cd21e26 7cd64490 00000000 00000021 0x0021e7cc: 00000047 0028f0f8 00000001 0021edfc 0x0021e7dc: 00000000 00000000 402a0000 0021e830 0x0021e7ec: 00000045 22000000 0000000d 0000000b 0x0021e7fc: 00000002 00000002 00000000 00000005 0x0021e80c: 00000015 00000190 00000000 00000060 Backtrace: =>0 0xffff0000 (0x0021e828) 1 0x7cd22005 (0x0021e8b8) 2 0x7cd25c16 (0x0021eab8) 3 0x7d731437 (0x0021ec78) 4 0x7d75f229 (0x0021ed08) 5 0x7def0424 in user32 (+0xa0423) (0x0021f658) 6 0x7def0ffc in user32 (+0xa0ffb) (0x0021f6d8) 7 0x7d34bd56 (0x0021f748) 8 0x7d34cba8 (0x0021f7e8) 9 0x7df0a91c in user32 (+0xba91b) (0x0021f828) 10 0x7df0b103 in user32 (+0xbb102) (0x0021f888) 11 0x7df0d416 in user32 (+0xbd415) (0x0021f8d8) 12 0x7dec5a61 in user32 (+0x75a60) (0x0021f988) 13 0x7de89ecb in user32 (+0x39eca) (0x0021fae8) 14 0x7de8a7b8 in user32 (+0x3a7b7) (0x0021fb28) 15 0x7d33a9d4 (0x0021fba8) 16 0x7d341b27 (0x0021fc08) 17 0x7eb1d921 in winecfg (+0xd920) (0x0021fe68) 18 0x7eb24d4e in winecfg (+0x14d4d) (0x0021fef8) 19 0x7eb24c86 in winecfg (+0x14c85) (0x0021ff30) 20 0x7b6520e0 in kernel32 (+0x320df) (0x0021ff48) 21 0x7bc7eba7 (0x0021ff5c) 22 0x7bc7f292 (0x0021ffec) 0xffff0000: -- no code accessible -- -- 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 0

[Bug 49641] New: Beneath a Steel Sky's Steam version crashes due to incomplete sapi implementation
by WineHQ Bugzilla 19 Sep '21

19 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=49641 Bug ID: 49641 Summary: Beneath a Steel Sky's Steam version crashes due to incomplete sapi implementation Product: Wine Version: 5.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: sapi Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)mail.com Distribution: --- Currently it uses ScummVM 2.1.2. The next version of ScummVM should in theory fix this crash due to https://github.com/scummvm/scummvm/commit/9a3e420bd20533e310e80058bcc63adeb… It currently crashes on: https://github.com/scummvm/scummvm/blob/branch-2-1-2/backends/text-to-speec… --- snip --- if (SUCCEEDED(hr)) { hr = cpEnum->GetCount(&ulCount); } _voice->SetVolume(0); // <-- here while (SUCCEEDED(hr) && ulCount--) { --- snip --- This is due to _voice not being initialized. It is supposed to be initialized here: https://github.com/scummvm/scummvm/blob/branch-2-1-2/backends/text-to-speec… --- snip --- // init voice hr = CoCreateInstance(CLSID_SpVoice, NULL, CLSCTX_ALL, IID_ISpVoice, (void **)&_voice); // <-- here if (FAILED(hr)) { warning("Could not initialize TTS voice"); return; } --- snip --- However, it fails earlier in the function: https://github.com/scummvm/scummvm/blob/branch-2-1-2/backends/text-to-speec… --- snip --- HRESULT hr = CoCreateInstance(CLSID_SpObjectTokenCategory, NULL, CLSCTX_ALL, IID_ISpObjectTokenCategory, (void **)&pTokenCategory); if (SUCCEEDED(hr)) { hr = pTokenCategory->SetId(SPCAT_AUDIOOUT, TRUE); // <-- here if (SUCCEEDED(hr)) { WCHAR *tokenId; hr = pTokenCategory->GetDefaultTokenId(&tokenId); if (SUCCEEDED(hr)) { --- snip --- It fails because it's unable to find the HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\AudioOutput registry key. If speechsdk is installed through winetricks (and the game is run), the registry key will be populated, allowing it to step further, but it will then crash right after on GetDefaultTokenId, as it returns E_NOTIMPL. -- 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 35186] New: X Error of failed request: BadAlloc (insufficient resources for operation)
by wine-bugs＠winehq.org 18 Sep '21

18 Sep '21

http://bugs.winehq.org/show_bug.cgi?id=35186 Bug ID: 35186 Summary: X Error of failed request: BadAlloc (insufficient resources for operation) Product: Wine Version: 1.7.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cigydd(a)gmail.com Classification: Unclassified Created attachment 46936 --> http://bugs.winehq.org/attachment.cgi?id=46936 A quote from the PlayOnLinux log Hello wine community, I have trouble running most of the Big Fish Games with wine (and also the client but that's another issue) (www.bigfishgames.com) I get errors similar to this: X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Serial number of failed request: 224 Current serial number in output stream: 228 I know this could be related to mesa and my mom's graphics card which is "Intel Corporation 82865G Integrated Graphics Controller (rev 02)". -- 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 6

[Bug 51762] New: Installing visual studio 2019 by manually extracting vs_installer.opc crashes wine
by WineHQ Bugzilla 18 Sep '21

18 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51762 Bug ID: 51762 Summary: Installing visual studio 2019 by manually extracting vs_installer.opc crashes wine Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 70664 --> https://bugs.winehq.org/attachment.cgi?id=70664 Backtrace after running the extracted vs2019 installer I'm trying to install visual studio 2019. Running the installer on a vanilla wineprefix does not work it also does not work after installing corefonts and dotnet462 See https://bugs.winehq.org/show_bug.cgi?id=51761 I found a possible workaround in this script: https://bugs.winehq.org/attachment.cgi?id=65524 mentioned in this bugreport: https://bugs.winehq.org/show_bug.cgi?id=47626 The workaround crashes wine. To reproduce: $ rm -rf ~/.wine $ wineboot $ winetricks -q corefonts dotnet462 $ wget https://aka.ms/vs/16/release/installer -O vs_installer.opc $ md5sum vs_installer.opc 8bcc6fd057a5f066185fb287d7fff99e vs_installer.opc $ mkdir -p opc $ unzip -d opc vs_installer.opc $ wine opc/Contents/vs_installer.exe install --channelId VisualStudio.16.Release --channelUri "https://aka.ms/vs/16/release/channel" --productId Microsoft.VisualStudio.Product.BuildTools Now wine crashes, and gives me the opportunity to save a backtrace (attached). -- 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 51088] New: Wine doesn't find (builtin?) wineasio.dll.so
by WineHQ Bugzilla 16 Sep '21

16 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51088 Bug ID: 51088 Summary: Wine doesn't find (builtin?) wineasio.dll.so Product: Wine Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: michaelwigard(a)arcor.de Distribution: --- WineASIO provides an ASIO to JACK driver for WINE. (https://github.com/wineasio/wineasio) Since this commit: https://source.winehq.org/git/wine.git/commit/bb065801a693e1cd305d2a507c206… (ntdll: Map the builtin or fake dll from the Wine dirs if it's missing from the prefix.) Wine doesn't seem to find wineasio.dll.so any more: $ wine regsvr32 wineasio.dll regsvr32: Failed to load DLL 'wineasio.dll' Before that commit, load_builtin_dll would eventually be called and load wineasio.dll.so. After that commit, it seems find_builtin_without_file is called, but doesn't load it. With this workaround it works again: $ cp /usr/lib/wine/wineasio.dll.so ~/.wine/drive_c/windows/system/wineasio.dll I'm not too familiar with the internals of Wine, but I suspect it might have something to do with the absence of a fake dll. I was able to get it to work by copying and renaming one of the other fake dlls to wineasio.dll, but only when also setting WINEDLLPATH. It seems to me that this should be a bug in Wine, since it worked the way it was before and doesn't since that commit, but if the solution is something else, please let me know. -- 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 51736] New: World of Warcraft TBC Classic crashed upon killing in world PVP
by WineHQ Bugzilla 15 Sep '21

15 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51736 Bug ID: 51736 Summary: World of Warcraft TBC Classic crashed upon killing in world PVP Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: borgoneohone(a)yahoo.com Distribution: --- Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.13-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4690 CPU @ 3.50GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2 In World of Warcraft The Burning Crusade Classic edition, the game hangs then crashes every time I am close, in distance, to a world PvP target and said target is near death and I am engaged in the PvP. This has only happened in this specific distrobution of Linux. It did not happen in the Gnome variant of Manjaro, nor did it happen in Ubuntu. This is my first bug filing, so please tell me if I did anything incorrectly. I am unsure how to generate a bug report in Wine, though I will attempt to look further into it if it happens when I have some time to look into it instead of needing to reopen and log back into the game client. -- 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 51756] New: Blockattack gives a black screen after changing from windowed to full screen or vice versa
by WineHQ Bugzilla 15 Sep '21

15 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51756 Bug ID: 51756 Summary: Blockattack gives a black screen after changing from windowed to full screen or vice versa Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 70651 --> https://bugs.winehq.org/attachment.cgi?id=70651 Console messages running under wine-6.15-123-gbe8501ac6f1 Blockattack gives a black screen after changing from windowed to full screen or vice versa Note, I'm running a version of wine between 6.15 and 6.16: $ wine --version wine-6.15-123-gbe8501ac6f1 To reproduce: # pacman -Suy # reboot $ rm -rf ~/.wine $ wineboot $ wget https://github.com/blockattack/blockattack-game/releases/download/v2.6.0/bl… $ md5sum blockattack-installer-2.6.0.exe 2c9b37b7794f549271b6dae6865af687 blockattack-installer-2.6.0.exe $ wine blockattack-installer-2.6.0.exe (accept the defaults, and let it run blockattack) Now blockattack starts playing. Go to configure, and click on "fullscreen off" or click on "fullscreen on". Now the game goes from colorfull windowed to a completely black fullscreen, or it goes from colorfull fullscreen to black windowed. Press alt-tab to return to the desktop manager, right-click on blockattack in the task bar, and choose "close window". The game will now exit. My versions: $ wine --version wine-6.15-123-gbe8501ac6f1 [cedric(a)cedric ~]$ uname -a Linux cedric 5.14.3-arch1-1 #1 SMP PREEMPT Sun, 12 Sep 2021 20:51:34 +0000 x86_64 GNU/Linux -- 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