wine-bugs June 2025

wine-bugs@winehq.org

1 participants
868 discussions

[Bug 58420] New: Wine crashes when running msys2 iff CPU's PKU/PKRU feature is enabled
by WineHQ Bugzilla 03 Jul '25

03 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58420 Bug ID: 58420 Summary: Wine crashes when running msys2 iff CPU's PKU/PKRU feature is enabled Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pipcet(a)protonmail.com Distribution: --- This is a heads-up about a bug in cygwin/msys2 which may be misreported as a wine bug. The Cygwin code assumes CPUID leaf 0x0d to indicate in EBX a 64-byte-aligned value. That may or may not be true on current Windows systems, but on current Linux systems running Wine, with recent CPUs, a CPU feature called "PKU" or "PKRU" (memory protection keys for userspace), enabled by default, indicates an additional 8-byte XSAVE area. This makes the Cygwin code attempt to xsave to a non-64-byte aligned area, which causes a segfault and abnormal program termination. While this is clearly a bug, it's a bug that apparently cannot be triggered by current Windows systems. This means Wine fails to be bug-for-bug compatible in this case. I don't think there's an easy way around that: we'd have to trap XGETBV and CPUID instructions to pretend that a feature that is enabled by Linux actually isn't available. It would have been nice if the Linux kernel had provided a way to disable the pku feature on a per-process basis, but AFAICT, it didn't. The nopku kernel command line argument makes things work, but requires a reboot and disables the very useful PKU feature for the entire system. So I don't think there's a good workaround here, but maybe we should suggest to the Linux kernel people to allow per-process activation of any future XCR0 features? -- 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 56761] New: So when I install Blizzard.net setup exe its crashes and gives me the backtrace log
by WineHQ Bugzilla 03 Jul '25

03 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=56761 Bug ID: 56761 Summary: So when I install Blizzard.net setup exe its crashes and gives me the backtrace log Product: Wine Version: 6.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adampigeons(a)gmail.com Distribution: --- Created attachment 76555 --> https://bugs.winehq.org/attachment.cgi?id=76555 the log of the error i launch battlenet exe setup then the window becomes unusable then i get the backtrace log -- 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 12

[Bug 55979] New: Blizzard Battle.net Launcher: New Version Released On 11/30/2023 Hangs During Installation
by WineHQ Bugzilla 03 Jul '25

03 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=55979 Bug ID: 55979 Summary: Blizzard Battle.net Launcher: New Version Released On 11/30/2023 Hangs During Installation Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: crashdance(a)charter.net Distribution: --- Created attachment 75569 --> https://bugs.winehq.org/attachment.cgi?id=75569 Terminal output when running the Battle.net client installer in a clean Wine prefix When attempting to install Battle.net in a clean 64-bit prefix on a clean install of Linux Mint 21.2 with all needed dependencies, I get the attached terminal output and the progress hangs at 45%. Also, I know the maintainers of Bugzilla encourage reporting only one problem per bug. That being said, the exact same time this started happening, my existing Wine prefix for Battle.net (and my Battle.net games) caused thread crashes when opening Battle.net after installing yesterday's update. The update was installed from within the Battle.net client by clicking the green icon to install the update. Prior to this update released yesterday on November 30, 2023, Battle.net and the games were running flawlessly. Because I can only add a single attachment, the Pastebin links below will give more detail on the related issue of thread crashes described above: Existing prefix terminal output when the thread crash occurs: https://pastebin.com/4UwxTsEP Here is my system information: https://pastebin.com/v3MVemgg Was able to save a crash report for the thread crash issue: https://pastebin.com/mYX68NrX -- 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 28

[Bug 58358] New: Dungeons & Dragons Online: No suitable graphics device was found. [122]
by WineHQ Bugzilla 02 Jul '25

02 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58358 Bug ID: 58358 Summary: Dungeons & Dragons Online: No suitable graphics device was found. [122] Product: Wine Version: 10.9 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ccooksey(a)mindspring.com Created attachment 78747 --> http://bugs.winehq.org/attachment.cgi?id=78747 Logs showing the video driver failures in Wine 10.0_1 and higher On macOS Sequoia, using Apple Silicon on a MacBook Pro, running Dungeons and Dragons online and entering the game world on any version of Wine *after* 10.0 will stop with a message: "No suitable graphics device was found. Are you running through a remote session or a VM? If not, please check your video hardware capabilities. [122]" The game terminates and cannot be played. Note that the Game Launcher works fine. It is the game client that fails -the bit that uses DX9 and above. If the original Wine 10.0 is installed (prior to 10.0_1), it works fine. To recreate: Working case (Wine 10.0): - Register a free account at: https://www.ddo.com/register - Download the game installer here: https://www.ddo.com/download - Install wine 10.0, (not wine-stable - see instructions below). - Install the game to a standard wine prefix. - Run "C:/Program Files (x86)/StandingStoneGames/Dungeons & Dragons Online/DNDLauncher.exe" to enter the launcher. Use your free account. - Enter the world "Orien". - Observe that the character creation screen in the game client appears. Non working case (Wine 10.0_1 and higher): - Install any higher version of Wine, i.e. wine-stable (10.0_2), wine@staging or wine@devel. - Install the game to a standard wine prefix (if you didn't already). - Run "C:/Program Files (x86)/StandingStoneGames/Dungeons & Dragons Online/DNDLauncher.exe" to enter the launcher. Use your free account. - Enter the world "Orien". - The game client will stop with error [122] as it tries to connect to DX9. My observation: 10.0 uses: [mvk-info] MoltenVK version 1.2.10, supporting Vulkan version 1.2.290. 10.0_1 and higher all use: [mvk-info] MoltenVK version 1.3.0, supporting Vulkan version 1.3.313. There are literally no code changes in Wine from 10.0 to 10.0_1. But these graphics libs did change and now there appears to be no video driver. I have been using brew to install. Here is a speedy way to get the original Wine 10.0 installed on a machine: brew uninstall wine-stable # or wine@staging or wine@devel, as needed curl -o wine-stable.rb https://raw.githubusercontent.com/Homebrew/homebrew-cask/3b6f8acd9c1f8aad56… sed -i '' 's/wine64/msidb/g' wine-stable.rb # Implements an important change from the 10.0_1 brew cask. brew install --no-quarantine wine-stable.rb # Note the '.rb' suffix. # If you are on Apple Silicon, install Apple's x86 emulator. Ignore any errors. /usr/sbin/softwareupdate --install-rosetta --agree-to-license For the breaking case, you can just "brew install --no-quarantine [wine-stable | wine@staging | wine@devel]". No need to use older casks. Note that the current gstreamer is not compatible with wine-stable. Optionally add these commands to prevent gstreamer from being noisy and slowing things down: export GST_PLUGIN_PATH=/dev/null export GST_PLUGIN_SYSTEM_PATH=/dev/null I have attached logs from 10.0 (working) and 10.9 (not working). I used WINEDEBUG="+seh,+tid,+d3d,+vulkan,+dxvk,+d3d12". Please let me know if you need any additional info from me. Thanks, Chris. -- 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 58417] New: Failure to compile: Undeclared KW_ object
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58417 Bug ID: 58417 Summary: Failure to compile: Undeclared KW_ object Product: vkd3d Version: 1.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: johngodman006(a)gmail.com Distribution: --- Created attachment 78834 --> http://bugs.winehq.org/attachment.cgi?id=78834 Compilation log I am trying to compile wine in shared WoW64 mode, and ran into the attached error during compilation of the 64 bit binary. I have to imagine, given the compilation error is an undeclared identifier, that I am missing some headers. However, I'm not sure what exactly I am missing. I have packages spirv-headers-devel, vulkan-headers, and libvkd3d-devel installed at their latest versions from Fedora. For reference, I'm on Fedora 42 kernel 6.15.3. I must be making a simple mistake, right? If someone could give me a hand, I'd greatly appreciate it. -- 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 58229] New: _SH_SECURE sharing flag is not supported and causing _wfsopen to fail
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58229 Bug ID: 58229 Summary: _SH_SECURE sharing flag is not supported and causing _wfsopen to fail Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: bruvzg13(a)proton.me Distribution: --- Calling _wfsopen with _SH_SECURE sharing flag result in failure and "012c:err:msvcrt:_wsopen_dispatch Unhandled shflags 0x80" error in the terminal. 0x80 value correspond to _SH_SECURE Discovered while debugging Godot Engine - https://github.com/godotengine/godot/pull/106392 Seems like the case for this flag is missing: https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/msvcrt/file.c?ref_ty… The flag is documented as "shared read, exclusive write access" (https://learn.microsoft.com/en-us/cpp/c-runtime-library/sharing-constants?v…), and the issue can be worked around by substituting it with "(mode_flags == READ) ? _SH_DENYWR : _SH_DENYRW", which result in the same behavior as on Windows (at least in our use case). -- 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 58416] New: Cloudflare is blocking patches and code snippets
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58416 Bug ID: 58416 Summary: Cloudflare is blocking patches and code snippets Product: WineHQ Bugzilla Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com CC: austinenglish(a)gmail.com Distribution: --- Cloudflare stops me from attaching patches to bug reports unless I compress them in a format that Cloudflare won't check. It also blocks me if I paste some code into the comments. Seems to get upset with C and PHP. I haven't tested much else but it's pretty obviously not desirable behaviour for a Bugzilla. Been happening for a while, probably anti-spam, anti-bot protection. -- 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 58271] New: Window decoration issues in Wine with Wayland driver
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58271 Bug ID: 58271 Summary: Window decoration issues in Wine with Wayland driver Product: Wine Version: 10.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: mexano222(a)gmail.com Distribution: --- Created attachment 78617 --> http://bugs.winehq.org/attachment.cgi?id=78617 default decorations When running applications through Wine using the native Wayland driver, windowed applications are not receiving proper window decorations (e.g., titlebars, borders) from the system window manager. Instead, Wine's default, minimal, and visually unappealing decorations are displayed. I have enabled option "Allow the window manager to decorate the windows" in winecfg and it's working fine on Xwayland. But this option does not appear to have any effect under native Wayland. -- 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 58126] New: Display enumeration differs from winex11
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58126 Bug ID: 58126 Summary: Display enumeration differs from winex11 Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: oleg(a)np880.ru Distribution: --- Created attachment 78389 --> http://bugs.winehq.org/attachment.cgi?id=78389 Display enumeration in winewayland driver. Enumeration of displays in winewayland driver differs from winex11 and doesn't even follow order of reported wl_outputs. I have 3 displays: with middle one (1440p, primary) being the first display. My other displays are 1080p. In winex11 it's indeed the first, and it also reported as first wl_output by my compositor (KWin). But winewayland driver reports it the second and the leftmost display reported as the first. It causes problem in old games that don't have display selection and enumerate video modes only for primary (first) display, so I can't get resolution higher than 1080p on my 1440p display that is supposed to be primary. Although we don't have a way to determine primary screen on Wayland we can at least follow order of reported wl_outputs. Here is what my compositor is reporting and it doesn't correlate with order of winewayland driver. interface: 'wl_output', version: 4, name: 61 name: DP-1 description: Xiaomi Corporation Mi monitor x: 1920, y: 0, scale: 2, physical_width: 598 mm, physical_height: 336 mm, make: 'Xiaomi Corporation', model: 'Mi monitor', subpixel_orientation: unknown, output_transform: normal, mode: width: 2560 px, height: 1440 px, refresh: 180.000 Hz, flags: current interface: 'wl_output', version: 4, name: 62 name: DP-2 description: Philips Consumer Electronics Company Philips 226V4 x: 0, y: 0, scale: 1, physical_width: 477 mm, physical_height: 268 mm, make: 'Philips Consumer Electronics Company', model: 'Philips 226V4', subpixel_orientation: unknown, output_transform: normal, mode: width: 1920 px, height: 1080 px, refresh: 60.000 Hz, flags: current interface: 'wl_output', version: 4, name: 63 name: HDMI-A-1 description: Philips Consumer Electronics Company Philips 235PL x: 3968, y: 0, scale: 1, physical_width: 510 mm, physical_height: 287 mm, make: 'Philips Consumer Electronics Company', model: 'Philips 235PL', subpixel_orientation: unknown, output_transform: 90°, mode: width: 1920 px, height: 1080 px, refresh: 60.000 Hz, flags: current -- 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 57980] New: Adobe Creative Cloud requires unimplemented function KERNEL32.dll.SetThreadpoolTimerEx
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=57980 Bug ID: 57980 Summary: Adobe Creative Cloud requires unimplemented function KERNEL32.dll.SetThreadpoolTimerEx Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: asdfghrbljzmkd(a)outlook.com Distribution: --- Every so often I test installing Adobe CC on Wine to see if it will work. With the recent fixes relating to libcef/edge/chromium sandboxing, I gave it another go. Seems like this is now an issue: ``` wine: Call from 00006FFFFFC75D38 to unimplemented function KERNEL32.dll.SetThreadpoolTimerEx, aborting ``` -- 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

← Newer
1
...
34
35
36
37
38
39
40
...
87
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs June 2025