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

[Bug 57103] New: "opengl32.dll" failed to initialize with WOW64 on Wayland
by WineHQ Bugzilla 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=57103 Bug ID: 57103 Summary: "opengl32.dll" failed to initialize with WOW64 on Wayland Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: redwindwanderer(a)gmail.com Distribution: --- I know both WOW64 and pure Wayland are experimental, but I think this is very basic stuff that I believe should work even on early days. I build latest WINE gitlab code master branch with: ./configure --enable-win64 --without-x --with-wayland --enable-archs=x86_64,i386 ..which results on Wayland-only WOW64 Wine. Basic 32bit programs work, but programs requiring OpenGL produce this error: 0024:err:environ:init_peb starting L"Z:\\root\\sh2\\sh2pc.exe" in experimental wow64 mode 0024:err:opengl:DllMain Failed to load unixlib, status 0xc0000005 0024:err:module:loader_init "opengl32.dll" failed to initialize, aborting 0024:err:module:loader_init Initializing dlls for L"Z:\\root\\sh2\\sh2pc.exe" failed, status c0000142 The opengl32.dll was built and is installed in /usr/local/lib/wine/x86_64-windows/opengl32.dll, and EGL was correctly detected during configuration: checking for X... disabled checking for wayland-client.h... yes checking for wl_display_connect in -lwayland-client... yes checking for wayland-scanner... /usr/local/bin/wayland-scanner checking for xkbcommon/xkbcommon.h... yes checking for xkb_context_new in -lxkbcommon... yes checking for xkbcommon/xkbregistry.h... yes checking for rxkb_context_new in -lxkbregistry... yes checking for EGL/egl.h... (cached) yes checking for -lEGL... libEGL.so.1 checking for wayland-egl.h... yes checking for wl_egl_window_create in -lwayland-egl... yes So all in all, things should work and opengl32.dll should work correctly on WOW64+Wayland, I believe. -- 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 14

[Bug 55410] New: msi:package fails on w8adm
by WineHQ Bugzilla 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=55410 Bug ID: 55410 Summary: msi:package fails on w8adm Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com msi:package fails on w8adm: package.c:8054: Test failed: Expected ERROR_SUCCESS, got 1605 package.c:8055: Test failed: Expected a valid product handle package.c:8099: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8100: Test failed: Expected "", got "apple" package.c:8101: Test failed: Expected 0, got 260 package.c:8106: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8107: Test failed: Expected "", got L"apple" package.c:8108: Test failed: Expected 0, got 260 package.c:8114: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8115: Test failed: Expected "{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got "apple" package.c:8117: Test failed: Expected 38, got 260 package.c:8123: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8124: Test failed: Expected L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple" package.c:8126: Test failed: Expected 38, got 260 package.c:8132: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8133: Test failed: Expected 38, got 260 package.c:8138: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8139: Test failed: Expected 38, got 260 package.c:8149: Test failed: Expected 38, got 260 package.c:8158: Test failed: Expected 38, got 260 package.c:8165: Test failed: Expected ERROR_MORE_DATA, got 6 package.c:8166: Test failed: Expected first 3 chars of "{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got "apple" package.c:8168: Test failed: Expected 38, got 4 package.c:8174: Test failed: Expected ERROR_MORE_DATA, got 6 package.c:8175: Test failed: Expected first 3 chars of L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple" package.c:8177: Test failed: Expected 38, got 4 package.c:8184: Test failed: Expected ERROR_MORE_DATA, got 6 package.c:8185: Test failed: Expected first 37 chars of "{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got "apple" package.c:8193: Test failed: Expected ERROR_MORE_DATA, got 6 package.c:8194: Test failed: Expected first 37 chars of L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple" package.c:8203: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8204: Test failed: Expected "{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got "apple" package.c:8206: Test failed: Expected 38, got 39 package.c:8212: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8213: Test failed: Expected L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple" package.c:8215: Test failed: Expected 38, got 39 package.c:8222: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8223: Test failed: Expected "", got "apple" package.c:8224: Test failed: Expected 0, got 260 package.c:8229: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8230: Test failed: Expected "", got L"apple" package.c:8231: Test failed: Expected 0, got 260 package.c:8234: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8240: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8241: Test failed: Expected "", got "apple" package.c:8242: Test failed: Expected 0, got 260 package.c:8247: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8248: Test failed: Expected "", got L"apple" package.c:8249: Test failed: Expected 0, got 260 package.c:8252: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8258: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8259: Test failed: Expected "{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got "apple" package.c:8261: Test failed: Expected 38, got 260 package.c:8267: Test failed: Expected ERROR_SUCCESS, got 6 package.c:8268: Test failed: Expected L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple" package.c:8270: Test failed: Expected 38, got 260 See https://test.winehq.org/data/patterns.html#msi:package These failures started on 2023-07-27 which is when the w8 VM's memory was increased to 4GB, and older WineTest builds still produce the failures. So the 2023-07-27 VM change is the cause of these failures but it's not clear why. Also note that, unlike msi:msi and msi:source, msi:package fails even if run on its own (see bug 55396). -- 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 57096] New: regression: Hogia Hemekonomi wont start anymore
by WineHQ Bugzilla 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=57096 Bug ID: 57096 Summary: regression: Hogia Hemekonomi wont start anymore Product: Wine Version: 9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)jonass.user.lysator.liu.se Distribution: --- After updating from 9.15 to 9.16 Hogia Hemekonomi wont start anymore. The console shows only a single line: 01dc:err:sync:RtlpWaitForCriticalSection section 757739E0 "dlls/krnl386.exe16/syslevel.c: Win16Mutex" wait timed out in thread 01dc, blocked by 01fc, retrying (60 sec) That line is repeated every 60 secs until I kill it. This is very similar to bug 52511, but at start of application and not at shutdown of application. -- 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

[Bug 53154] New: Crash of EpicOnlineServicesUserHelper.exe" --setup
by WineHQ Bugzilla 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=53154 Bug ID: 53154 Summary: Crash of EpicOnlineServicesUserHelper.exe" --setup Product: Wine Version: 7.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: me(a)janryll.de Distribution: --- Created attachment 72586 --> https://bugs.winehq.org/attachment.cgi?id=72586 Unhandled exception: page fault on read access. 1. Start "Epic Games Lauchner" 2. Goto Settings 3. Click on Install Epic Online Services 4. Crash after some seconds Epic Games Launcher displays Error EOS-ERR-1603. -- 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 55804] New: DICOM Viewer (eFilm Workstation 2.x/3.x) aborts because libxml2 doesn't like "ISO8859-1" (builtin msxml6).
by WineHQ Bugzilla 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=55804 Bug ID: 55804 Summary: DICOM Viewer (eFilm Workstation 2.x/3.x) aborts because libxml2 doesn't like "ISO8859-1" (builtin msxml6). Product: Wine Version: 8.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 75294 --> https://bugs.winehq.org/attachment.cgi?id=75294 xml2: Allow encoding="ISO8859-1". Bug #13340 is for the same application but with native msxml6. This bug is about the nearly same error message when using builtin msxml6: > XML Parser Error > LoadXMLFile 'C:\efilmlite_dvd\eFilmLite\Profiles > \Default\ToolBarMiniCfg.xml': > Error: > Code = 0x80004005 > Source = Line: 0; Char: 0 > Error Description = error But this seems to be caused by the bundled libxml2 not accepting as encoding "ISO8859-1", just "ISO-8859-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 8

[Bug 43472] New: R-Link 2 Toolbox crashes on startup
by wine-bugs＠winehq.org 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=43472 Bug ID: 43472 Summary: R-Link 2 Toolbox crashes on startup Product: Wine Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sb(a)monkey-mind.net Distribution: --- Created attachment 58852 --> https://bugs.winehq.org/attachment.cgi?id=58852 R-Link 2 Toolbox Backtrace The Renault R-Link 2 Toolbox application crashes upon launch. The installer manages to install just fine, but when trying to launch the actual application, the crash dialog pops up. See attached backtrace. The shell window from which the application was started says: wine: Unhandled page fault on execute access to 0x00000000 at address (nil) (thread 0009), starting debugger... Tried with emulation set to Windows 10, Windows 7, Windows Server 2003; all failed with the same error. SELinux is in permissive mode. -- 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 15

[Bug 56102] New: Comdlg32/Color - Out of bound value is used
by WineHQ Bugzilla 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=56102 Bug ID: 56102 Summary: Comdlg32/Color - Out of bound value is used Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- - Set HSV to max value by typing 999 - Automatically sets to 239, 240, 240 Scenario 1 : - Click on the 2D spectrum - Lum gets to 999 => should stay to 240 Scenario 2 : - Click on right ribbon - H & S gets to 999 and ribbon gets crazy > Faulty code is CC_CheckDigitsInEdit where the raw value is returned even when exceeding max value if (value > maxval) /* build a new string */ { sprintf(buffer, "%d", maxval); result = 2; } should be replaced by if (value > maxval) /* build a new string */ { value = maxval; sprintf(buffer, "%d", maxval); result = 2; } -- 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 57117] New: BsgLauncher cannot launch due to unhandled exception in System.Security.Cryptography (.NET48)
by WineHQ Bugzilla 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=57117 Bug ID: 57117 Summary: BsgLauncher cannot launch due to unhandled exception in System.Security.Cryptography (.NET48) Product: Wine Version: 9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madbyte(a)tuta.io Distribution: --- Created attachment 77009 --> https://bugs.winehq.org/attachment.cgi?id=77009 error log, used WINEDEBUG=+seh+debugstr Upon launch, the BsgLauncher used to play Escape from Tarkov / Escape from Tarkov: Arena, crashes early on (no window actually appears), stating an error that might be related to the following err line: System.Security.Cryptography.Utils._DecryptData(System.Security.Cryptography.SafeKeyHandle, Byte[], Int32, Int32, Byte[] ByRef, Int32, System.Security.Cryptography.PaddingMode, Boolean)\n" See attached log file for more details. - This issue has been introduced with Wine 9.15. - Earlier versions using the same dependencies won't fail with that error (working state) - Switching between different wine version (win81, win10, win11) had no effect for me BsgLauncher: https://prod.escapefromtarkov.com/launcher/download Prefix dependencies: arial times vcrun2019 dotnet48 -- 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 11

[Bug 56352] New: comctl32: Handle progress bar state messages
by WineHQ Bugzilla 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=56352 Bug ID: 56352 Summary: comctl32: Handle progress bar state messages Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: rikul(a)inbox.ru Distribution: --- PBM_SETSTATE, PBM_GETSTATE messages are not handled for Progress Bar control. -- 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 50365] New: Starcraft Remastered black screen on launch or window only mode
by WineHQ Bugzilla 06 Sep '24

06 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=50365 Bug ID: 50365 Summary: Starcraft Remastered black screen on launch or window only mode Product: Wine-staging Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: darinsmiller(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- 2 display issues appeared a few releases prior to the 6.0 rc's and are still present: 1st issue: Starcraft Remaster fails to set proper video mode by launching with black screen. Starcraft cursor is visible and underlying menu items react with hover sound, but screen remains black even after clicking on invisible menu items. Alt-tabbing from/to the game refreshes the screen to normal display mode. 2nd issue: Running dual monitors: primary 4K, secondary 2K scaled to 4K. Starcraft Rem. launches in window mode on the 4K screen even though settings specify full-screen mode. Alt-enter fails to scale to full screen. If the secondary 2K monitor is set to native (non-scaled resolution) before the game is launched, the game launches to the black fullscreen mode on the primary display as described above. Lutris with wine version 5.7.10-x86_64 correctly runs Starcraft Remastered on the primarly 4K display. Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-33-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1080/PCIe/SSE2 NVidia Driver: 455.45.01 wine version: wine-6.0-rc3 (Staging) -- 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