- Wine-Bugs - list.winehq.org

[Bug 57811] New: wikis/Building-Wine contains broken/obsolete link
by WineHQ Bugzilla July 4, 2025

July 4, 2025

https://bugs.winehq.org/show_bug.cgi?id=57811 Bug ID: 57811 Summary: wikis/Building-Wine contains broken/obsolete link Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: depaoli.renzo(a)gmail.com Distribution: --- As per instruction on the 404 website "If you followed a link from a WineHQ.org page and reached this page in error, please report it to the WineHQ.org Bugzilla.": The link on the Wine Wiki https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine https://www.winehq.org/pipermail/wine-devel/2016-January/111245.html is broken resulting in 404. -- 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 58451] New: rpcrt4: Fix 'FIXME: should use CreateTimerQueueTimer when implemented'
by WineHQ Bugzilla July 4, 2025

July 4, 2025

http://bugs.winehq.org/show_bug.cgi?id=58451 Bug ID: 58451 Summary: rpcrt4: Fix 'FIXME: should use CreateTimerQueueTimer when implemented' Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: winehq-bugs_serge_180716(a)gautherie.fr Distribution: --- wine-1.1.18 https://gitlab.winehq.org/wine/wine/-/commit/5f6ae94ad0163341c2cd79a89f29b2… added { /* FIXME: should use CreateTimerQueueTimer when implemented */ thread = CreateThread(NULL, 0, rpcrt4_http_timer_thread, timer_data, 0, NULL); } although CreateTimerQueueTimer() was already implemented, by wine-1.1.2 https://gitlab.winehq.org/wine/wine/-/commit/d343f2baf76413eb690cbc44a0d56e… { NTSTATUS status = RtlCreateTimer(phNewTimer, TimerQueue, Callback, Parameter, DueTime, Period, Flags); } Check and fix that FIXME. -- 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 52999] New: Redout fails to detect visual c++ runtimes
by WineHQ Bugzilla July 4, 2025

July 4, 2025

https://bugs.winehq.org/show_bug.cgi?id=52999 Bug ID: 52999 Summary: Redout fails to detect visual c++ runtimes Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 72366 --> https://bugs.winehq.org/attachment.cgi?id=72366 Logfile When i try to run Redout, it says you need to install the c++ runtime. The log does not indicate anything going wrong: 002c:fixme:winediag:LdrInitializeThunk wine-staging 7.8 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0118:fixme:imm:ImeSetActiveContext (0000000000CDB7F0, 1): stub 0118:fixme:imm:ImmReleaseContext (000000000001006C, 0000000000CDB7F0): stub 007c:fixme:imm:ImeSetActiveContext (0000000000356C10, 0): stub 007c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000356C10): stub 0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 0000000000B9FD70 -- 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 56761] New: So when I install Blizzard.net setup exe its crashes and gives me the backtrace log
by WineHQ Bugzilla July 3, 2025

July 3, 2025

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 July 3, 2025

July 3, 2025

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 58446] New: Shift + Click to draw straight line using tablet pen not working in CLIP STUDIO PAINT version 2
by WineHQ Bugzilla July 3, 2025

July 3, 2025

http://bugs.winehq.org/show_bug.cgi?id=58446 Bug ID: 58446 Summary: Shift + Click to draw straight line using tablet pen not working in CLIP STUDIO PAINT version 2 Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kas23997(a)gmail.com Distribution: --- I am using a Wacom Intuous PT S2, for reference. I've tried to toggle mouse mode in CSP's settings, but neither works. The pen will just draw separate dots instead of making a straight line. It works if using a mouse, however. Nothing appeared in the Terminal after the wine command, so let me know if there's any other info I should provide. -- 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 58440] New: Dance eJay 6 and dance eJay 7 crash with advapi32 error
by WineHQ Bugzilla July 2, 2025

July 2, 2025

http://bugs.winehq.org/show_bug.cgi?id=58440 Bug ID: 58440 Summary: Dance eJay 6 and dance eJay 7 crash with advapi32 error Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: rave002(a)o2.pl Distribution: --- Created attachment 78891 --> http://bugs.winehq.org/attachment.cgi?id=78891 Dance ejay 6 Reloaded crash log Both applications used to run fine on the older versions of wine. I'm attaching the logs for Dance eJay 6.0, but the one for Dance 7 is pretty much the same. Tried winetricks to maybe install a "proper" version of advapi32, however winetricks doesn't provide it. I will try to add Dance eJay 7.0 crash log in a following comment if I'm able to. -- 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 58417] New: Failure to compile: Undeclared KW_ object
by WineHQ Bugzilla July 1, 2025

July 1, 2025

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 58416] New: Cloudflare is blocking patches and code snippets
by WineHQ Bugzilla July 1, 2025

July 1, 2025

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 58126] New: Display enumeration differs from winex11
by WineHQ Bugzilla July 1, 2025

July 1, 2025

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