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

[Bug 50083] New: ASCOM Platform 6.5 - Installation failed
by WineHQ Bugzilla 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=50083 Bug ID: 50083 Summary: ASCOM Platform 6.5 - Installation failed Product: Wine Version: 5.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bammzilla(a)astronomy.com.ph Distribution: --- Created attachment 68544 --> https://bugs.winehq.org/attachment.cgi?id=68544 Screenshots of popup error screens during install The ASCOM Platform allows windows desktop planetarium programs to control astronomical hardware such as telescopes, domes, and cameras. The software is freely distributable and open source, released under the Creative Commons Attribution-ShareAlike 3.0 License, but written under the .NET Platform. The latest version is ASCOM Platform 6.5, written under .NET Framework 4.8 and Visual Studio 2019. To prepare the installation, I ran winetricks -q vcrun2019 dotnet35sp1 dotnet452 dotnet472 dotnet48. No errors were reported in the installation of dotnet. I then launched the installer with the following command: WINEDEBUG=+nls wine ASCOMPlatform65.exe >> ASCOMPlatform65.log 2>&1 The installation went smoothly but popped up several error screens and ended with an installation failed. Screenshots of the error screens are attached. The WINEDEBUG log file is gzipped and attached. ASCOMPlatform installer log files are zipped and attached. Download the installer from the following link: https://github.com/ASCOMInitiative/ASCOMPlatform/releases/download/v6.5Rele… Full source code of ASCOM Platform is available here: https://github.com/ASCOMInitiative/ASCOMPlatform ASCOMPlatform License file: https://github.com/ASCOMInitiative/ASCOMPlatform/blob/master/LICENSE.txt Information about ASCOM can be found here: https://ascom-standards.org/Community/ -- 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 57457] New: Mathcad 15 crashes when enter trace tab
by WineHQ Bugzilla 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=57457 Bug ID: 57457 Summary: Mathcad 15 crashes when enter trace tab Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: unitu696(a)gmail.com Distribution: --- Created attachment 77454 --> https://bugs.winehq.org/attachment.cgi?id=77454 Program Error Details (backtrace) When I am trying to edit plot and open trace tab in Mathcad 15 Application crashes with error: Application has generated an exception that could not be handled Process ID=0x20 (32), Thread ID=0x24 (36) -- 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 57437] New: PStart isn't showing a menu in the tray bar
by WineHQ Bugzilla 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=57437 Bug ID: 57437 Summary: PStart isn't showing a menu in the tray bar Product: Wine Version: 9.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mywine(a)schiermeier-it.de Distribution: --- This is a regression: PStart is a 32-bit application that shows a button in the tray bar. Inside, it shows some important Windows applications that can be started from there. It is intended for starting applications from a removable disk device like the "Portable Apps" app collection. Now in the latest versions of wine it stopped working: the button is there but the menu isn't there. -- 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 57064] New: Bloodrayne 2 (legacy and Terminal Cut): graphical issue (foggy screen)
by WineHQ Bugzilla 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=57064 Bug ID: 57064 Summary: Bloodrayne 2 (legacy and Terminal Cut): graphical issue (foggy screen) Product: Wine Version: 9.5 Hardware: x86-64 URL: https://archive.org/download/BloodRayne2Demo/BloodRayn e2Demo.rar OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: awesie(a)gmail.com, z.figura12(a)gmail.com Regression SHA1: f6a1844dbed91b441ad69e7b15b5be242d063e87 Distribution: ArchLinux Created attachment 76927 --> https://bugs.winehq.org/attachment.cgi?id=76927 terminal output This bug affects both the legacy version of Bloodrayne 2 (2005) and the Terminal Cut version (2020). I made only a cursory test with the game, but the issue is immediately obvious: The screen looks as if it was covered with haze. If I turn off these graphics options in the game launcher, the problem still occurs: bump mapping, dynamic shadows, reflections. The result of the regression test: commit f6a1844dbed91b441ad69e7b15b5be242d063e87 wined3d: Use bindless textures for GLSL shaders if possible. Can be reproduced with Bloodrayne 2 demo version. BloodRayne2Demo.rar (477M) md5: 226a09d5f5ce2c4e0b7319627c75e69d Still present in Wine-9.15. Tested with NVIDIA 550.40.67. -- 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 57401] New: Dragon Unpacker crashes on both wine devel and staging
by WineHQ Bugzilla 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=57401 Bug ID: 57401 Summary: Dragon Unpacker crashes on both wine devel and staging Product: Wine Version: 9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yurnerolinux(a)yandex.com Distribution: --- App is this. https://github.com/elbereth/DragonUnPACKer Version that i tried are 5.6.2 and 5.7.0 beta. Both yields to same result. What does that app do? It converts custom formatted audio streams to known formats. https://www.elberethzone.net/en/dragon-unpacker-supported-games.html List of supported games, i tried with Freedom Fighters. How to repro? - Open the app - Press Ctrl+H or click HyperFile via File option in GUI - Click to Formats, tick "Audio" in that menu - Click to Search entry, select the path where game files resides, afterwards click Search below - See how it finds files, when it is done click "Ok" - You will see bunch of entries that says "streams-wav" etc, click to one of them, see how app crashes. Terminal output is this, now i don't know which Wine debug channel should be used for that. 007c:fixme:wineusb:query_id Unhandled ID query type 0x5. 007c:fixme:wineusb:query_id Unhandled ID query type 0x5. 007c:fixme:wineusb:query_id Unhandled ID query type 0x5. 007c:fixme:wineusb:query_id Unhandled ID query type 0x5. 0024:fixme:explorerframe:taskbar_list_SetProgressState iface 017B9B18, hwnd 00010086, flags 0 stub! 0024:fixme:explorerframe:taskbar_list_SetProgressValue iface 017B9B18, hwnd 00010086, ullCompleted 0, ullTotal 64 stub! 0024:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. -- 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 2

[Bug 57472] New: Systray support is broken in Wine 9.22
by WineHQ Bugzilla 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=57472 Bug ID: 57472 Summary: Systray support is broken in Wine 9.22 Product: Wine Version: 9.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Steps to reproduce: 1. Download and run WinRAR 7.01 https://www.rarlab.com/ 2. Install and launch 3. Press Alt + B (tools -> benchmark) and click "Background" 4. A systray icon/entry will appear and immediately disappear Using Xorg/X11/XFCE4. No Wayland. This is a regression. It used to work a couple of releases ago. -- 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 13

[Bug 57463] New: winebus always crashing with unknown since 8b41c2cfddba1f9973246f61e39d4a4d92912da5
by WineHQ Bugzilla 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=57463 Bug ID: 57463 Summary: winebus always crashing with unknown since 8b41c2cfddba1f9973246f61e39d4a4d92912da5 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436.tw(a)gmail.com Distribution: --- Created attachment 77463 --> https://bugs.winehq.org/attachment.cgi?id=77463 crash log of winebus.sys It will crash at winedevice.exe even execute winecfg I revert de265dfa0bc41fefec3525cd6a1db5d1e1d57029 and 8b41c2cfddba1f9973246f61e39d4a4d92912da5 in previous version of wine will fix this 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 9

[Bug 57411] New: Heroes of the Storm: screen sporadically flickers black
by WineHQ Bugzilla 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=57411 Bug ID: 57411 Summary: Heroes of the Storm: screen sporadically flickers black Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: matteo.mystral(a)gmail.com Distribution: --- You can already notice it in the login screen you get by running the game directly (.../Support64/HeroesSwitcher_x64.exe). Regression test blames: 46c8a637525d0f1cf67830295fb460c819b800b6 is the first bad commit commit 46c8a637525d0f1cf67830295fb460c819b800b6 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Fri Jan 20 16:23:42 2023 -0600 winex11: Separately store the internal pixel format set by WGL_WINE_pixel_format_passthrough. dlls/d3d8/tests/device.c | 6 +++--- dlls/d3d9/tests/device.c | 6 +++--- dlls/ddraw/tests/ddraw1.c | 6 +++--- dlls/ddraw/tests/ddraw2.c | 6 +++--- dlls/ddraw/tests/ddraw4.c | 6 +++--- dlls/ddraw/tests/ddraw7.c | 6 +++--- dlls/winex11.drv/opengl.c | 26 +++++++++++--------------- 7 files changed, 29 insertions(+), 33 deletions(-) Although effectively it seems to be kind of a bad interaction with my commit 72597b170e814599ef2be4b19dc4b9de0932a30f "wined3d: Don't use separate GL contexts for different swapchains." compounded with wined3d being a bit overeager with switching window for GL contexts. The game uses D3D11CreateDeviceAndSwapChain() to initialize the device and (AFAICS) always uses the returned swapchain to do all its work. Except, every now and then (about once every ~4 frames?) it clears the implicit swapchain's back buffer. At the moment, wined3d_context_gl_acquire() never attempts to reuse the current context if it has NULL target (e.g. because the texture that was used for the original activation of the context was released in the meantime, which is always the case when this bug triggers). What effectively happens for such (offscreen) clears is that wined3d activates the GL context on the implicit swapchain, on a different window, and that resets internal_format_set (see wined3d_context_gl_update_window()) which leads to resetting the pixel format on it. Soon afterwards the game will do some operation that requires the "real" swapchain (e.g. Present()) and wined3d will reactivate the context on the explicit swapchain, bouncing back and forth between the two swapchains / windows and resetting pixel format every time. I guess one way to fix this in general would be to keep per-window values for the current pixel format / internal format set flag in struct wined3d_context_gl, so that we avoid spurious pixel format resets when flipping through multiple windows. In this case though, it's enough to always allow reusing the current context if we don't need to access any on-screen resource. I'm going to open an MR that does just that in a bit. -- 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 57308] New: Cannot load split debug symbols under /usr/lib/debug
by WineHQ Bugzilla 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=57308 Bug ID: 57308 Summary: Cannot load split debug symbols under /usr/lib/debug Product: Wine Version: 9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: pq2sx44teeigl7za(a)chyen.cc Distribution: --- We're discussing splitting PE debug symbols into a separate Arch Linux package to reduce disk usage for users that don't need it: https://gitlab.archlinux.org/archlinux/packaging/packages/wine/-/issues/16. Typically, split debug symbol files are placed under /usr/lib/debug. Apparently, wine tries to find them but something wrong happens. If I run strace on the UNIX process for winedbg.exe, I got this when a crash happens in msvcrt.dll: 16423 newfstatat(AT_FDCWD, "/usr/lib/debug/\\??\\Z:\\usr\\lib\\wine\\x86_64-windows\\msvcrt.dll.debug", 0x7ffffe0ff8e0, 0) = -1 ENOENT The path should be /usr/lib/debug/usr/lib/wine/x86_64-windows/msvcrt.dll.debug. It seems Windows paths are not correctly converted to UNIX paths. -- 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 16

[Bug 43172] New: IDirectPlay4:: EnumConnections needs to support wide string in DPNAME structure
by wine-bugs＠winehq.org 06 Dec '24

06 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=43172 Bug ID: 43172 Summary: IDirectPlay4::EnumConnections needs to support wide string in DPNAME structure Product: Wine Version: 2.10 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-dplay Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- IDirectPlay4::EnumConnections needs to support wide strings in DPNAME returned in EnumConnections. Currently it just forwards to the ascii version. -- 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 3