May 2025 - Wine-bugs - list.winehq.org

[Bug 50484] New: Far Manager 3 crashes when Shift+Enter Execute in separate window pressed
by WineHQ Bugzilla 05 Jul '25

05 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=50484 Bug ID: 50484 Summary: Far Manager 3 crashes when Shift+Enter Execute in separate window pressed Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: lanthruster(a)gmail.com Distribution: --- Far Manager 3 crashes when executing a file association. 1. Download and extract farmanager3 https://www.farmanager.com/download.php?l=en (zip archive) 2. Create a text file with no or arbitrary content test.txt 3. Select test.txt and press Shift + Enter Wine will crash. That bug was there for years, including Wine 2.3 and earlier releases. -- 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 57950] New: Debugger Found Error in Wine 10.3 - Unable to Run MT5 on Linux
by WineHQ Bugzilla 05 Jul '25

05 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=57950 Bug ID: 57950 Summary: Debugger Found Error in Wine 10.3 - Unable to Run MT5 on Linux Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zareisajad98(a)gmail.com Distribution: --- I'm encountering a persistent "a debugger has been found on your system, unload it from memory and restart your program" error while trying to run MetaTrader 5 using Wine on Arch 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 16

[Bug 39688] New: Crash in file browser dialog (probably because of > MAX_PATH)
by wine-bugs＠winehq.org 05 Jul '25

05 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=39688 Bug ID: 39688 Summary: Crash in file browser dialog (probably because of > MAX_PATH) Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: n296869(a)rtrtr.com Distribution: --- Wine's GetOpenFileNameW/GetSaveFileNameW seems to crash when encountering a very long path name (i.e. longer than MAX_PATH characters). -- 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 9

[Bug 53008] New: When playing civilizatin2, winevdm crash
by WineHQ Bugzilla 05 Jul '25

05 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=53008 Bug ID: 53008 Summary: When playing civilizatin2, winevdm crash 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: clabbe.montjoie(a)gmail.com Distribution: --- Created attachment 72378 --> https://bugs.winehq.org/attachment.cgi?id=72378 backtrace of winevdm When playing civilization 2, game menu start, but after some time, game crash. I am sure that it worked before, but i need some time digging backup to find which version of wine I used. -- 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 50872] New: Greenshot doesn't start
by WineHQ Bugzilla 05 Jul '25

05 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=50872 Bug ID: 50872 Summary: Greenshot doesn't start Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: t6zm3v62fkp7fe5(a)yandex.ru Distribution: --- Created attachment 69684 --> https://bugs.winehq.org/attachment.cgi?id=69684 Terminal output When running installed latest unstable Greenshot (https://github.com/greenshot/greenshot/releases/download/v1.3.178/Greenshot…) in terminal, it doesn't start and shows unhandled exception. Latest stable version (https://github.com/greenshot/greenshot/releases/download/Greenshot-RELEASE-…) works alright. Lubuntu 20.04.1, Wine 6.5 (official PPA). -- 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 57811] New: wikis/Building-Wine contains broken/obsolete link
by WineHQ Bugzilla 04 Jul '25

04 Jul '25

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 52999] New: Redout fails to detect visual c++ runtimes
by WineHQ Bugzilla 04 Jul '25

04 Jul '25

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 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 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