wine-bugs July 2025

wine-bugs@winehq.org

1 participants
609 discussions

[Bug 58388] New: the application krita is what i was trying to draw but the programme just wont open.
by WineHQ Bugzilla 05 Jul '25

05 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58388 Bug ID: 58388 Summary: the application krita is what i was trying to draw but the programme just wont open. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ntsrkr(a)duck.com Distribution: --- it doesn't want to open. as soon as I try to open it wine crashes download link https://krita.org/en/post-download/ version is krita-x64-5.2.9-setup.exe -- 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 58303] New: make install for arm-linux-gnueabihf on aarch64-linux-gnu host fails at libaclui.a
by WineHQ Bugzilla 05 Jul '25

05 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58303 Bug ID: 58303 Summary: make install for arm-linux-gnueabihf on aarch64-linux-gnu host fails at libaclui.a Product: Wine Version: 10.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alex(a)alexrp.com Distribution: --- I did the following: git clone https://gitlab.winehq.org/wine/wine.git cd wine mkdir build32 build64 cd build64 ../configure --enable-win64 make -j$(nproc) cd ../build32 PKG_CONFIG_PATH=/usr/lib/arm-linux-gnueabihf ../configure --with-wine64=../build64 --host=arm-linux-gnueabihf make -j$(nproc) That all succeeds. However, when I try to `make install` in `build32`, I eventually get: ../build64/tools/winebuild/winebuild -w --implib -o dlls/aclui/libaclui.a -b arm-linux-gnueabihf --export \ ../dlls/aclui/aclui.spec tmp68634c48/libaclui-00000000.s: Assembler messages: tmp68634c48/libaclui-00000000.s:2: Error: unrecognized symbol type "" tmp68634c48/libaclui-00000000.s:9: Error: junk at end of line, first unrecognized character is `,' winebuild: /usr/bin/arm-linux-gnueabihf-as failed with status 1 make: *** [Makefile:1602: dlls/aclui/libaclui.a] Error 1 Unfortunately, I'm not familiar enough with the build system to know how to get at that temporary file to try to diagnose the problem. This is on a Ubuntu 25.04 machine, FWIW. -- 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 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 58451] New: rpcrt4: Fix 'FIXME: should use CreateTimerQueueTimer when implemented'
by WineHQ Bugzilla 04 Jul '25

04 Jul '25

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 58450] New: Total Annihilation (GOG, demo) – Wayland black screen on startup.
by WineHQ Bugzilla 04 Jul '25

04 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58450 Bug ID: 58450 Summary: Total Annihilation (GOG, demo) – Wayland black screen on startup. 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: karol23145(a)gmail.com Distribution: --- Created attachment 78901 --> http://bugs.winehq.org/attachment.cgi?id=78901 WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`. ### Summary Total Annihilation (GOG version and demo) shows a black screen on native Wayland (Mutter 48.3). On X11 it works perfectly, and on XWayland the game has a minor fullscreen issue (see Bug 57482). ### Steps to reproduce 1. Download the Total Annihilation demo (or use the GOG version). GAME DEMO CAN BE DOWNLOADED FROM: https://archive.org/details/TotalAnnihilation_201405 2. Launch the game executable (`TotalA.exe`) under Wine on a native Wayland session (No XWayland). ### Current behavior The game process starts, sound can be heard, and keyboard input works (buttons can be pressed), but the entire game window is black. The window is also not fullscreen. ### Expected behavior The game's intro videos should play, followed by the main menu, which should be visible and interactive. ### Relevant logs, screenshots, screencasts etc. *Attached are the following files:* 1. `TA.log`: Full Wine debug log captured with `WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`. 2. `system_info.txt`: Output of `inxi -Fxxxza`. ### System Details - **Wine Version:** Custom build from source (also tested with Wine development branch, same result) - **Windowing System:** Mutter 48.3 (Wayland session) - **Distribution:** Fedora 42 - **Graphics Driver:** Mesa 25.0.7 - **Kernel version:** 6.15.4 -- 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 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

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