wine-bugs

wine-bugs@winehq.org

1 participants
158853 discussions

[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 58228] New: Move child object page unable to fully load because it is too long
by WineHQ Bugzilla 04 Jul '25

04 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58228 Bug ID: 58228 Summary: Move child object page unable to fully load because it is too long Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net Distribution: --- When merging entries, the page that shows the entries to move the child objects to displays as one long list in alphabetical order. That list is now so long that the page cannot fully load: Ooops! Something has gone terribly wrong! Our monkey train has derailed! Worry not, a webmaster gopher help army has been dispatched and is on the way. If this error continues to be a problem, please report it to us on our Forums error details: Error Message: Maximum execution time of 60 seconds exceeded File: query.php:119 Discovered while trying to merge 千千静听 (TTPlayer) https://appdb.winehq.org/objectManager.php?sClass=application&iId=11003 with TTPlayer https://appdb.winehq.org/objectManager.php?sClass=application&iId=6077. The move child objects page only got as far as the H's before timing out. -- 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 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 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 32342] New: PlanetSide2 Error message and bugreport.txt and debug.log in Steam.
by wine-bugs＠winehq.org 03 Jul '25

03 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=32342 Bug #: 32342 Summary: PlanetSide2 Error message and bugreport.txt and debug.log in Steam. Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: linards.liepins(a)gmail.com Classification: Unclassified Created attachment 42683 --> http://bugs.winehq.org/attachment.cgi?id=42683 PlanetSide2 bugreport.txt Cannot run PlanetSide 2 on x64 Fedora 17. Popuing up three similar error log message with attached bugreport. Also attached debug.log is generated in Steam install dir. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 144

[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 58443] New: x11 'minimized' windows not re-fullscreening (fallout 3 / new vegas)
by WineHQ Bugzilla 03 Jul '25

03 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58443 Bug ID: 58443 Summary: x11 'minimized' windows not re-fullscreening (fallout 3 / new vegas) Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- c67bfdbeba1860c891e53c64379f5e86d8e8b664 / https://gitlab.winehq.org/wine/wine/-/commit/c67bfdbeba1860c891e53c64379f5e… reading the title of the mr makes sense, however this completely breaks fullscreen for fallout 3 and new vegas, and im sure other older games as mentioned https://bugs.winehq.org/show_bug.cgi?id=58442 - there have been a lot of fullscreen/focus/window bugs so it's hard to tell what all is what i spent a bunch of time to just bisect so i'll have to look for what is going on tomorrow -- 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 58167] New: Pegasus Mail immediately restores window
by WineHQ Bugzilla 03 Jul '25

03 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58167 Bug ID: 58167 Summary: Pegasus Mail immediately restores window Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)jonass.user.lysator.liu.se Distribution: --- After upgrading from 10.5 to 10.6 I can't minimize Pegasus Mail. When I click minimize the window only flashes, seems like it minimizes but immediately restores to open window with the same size as before. No error messages in console. git bisect suggests it may be related to commit 6b04bdf25796c9c76815588bf7bdc36ff44b9e13 OS: XUbuntu 24.04.2 LTS NVIDIA Driver Version: 535.183.01 Using X11 (not 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 15

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