wine-bugs April 2025

wine-bugs@winehq.org

1 participants
467 discussions

[Bug 58159] New: Forum user reports apt-update redirects to malformed URL for Ubuntu 24.04 since move to AWS server
by WineHQ Bugzilla 25 Apr '25

25 Apr '25

http://bugs.winehq.org/show_bug.cgi?id=58159 Bug ID: 58159 Summary: Forum user reports apt-update redirects to malformed URL for Ubuntu 24.04 since move to AWS server Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net Distribution: --- A user reported this on the forum, and also mentioned they were unable to file a bug because they were blocked by Cloudflare, so I'm reporting it here. https://forum.winehq.org/viewtopic.php?p=147056#p147056 -- 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 52811] New: Apps starting with wrong non-client area decoration
by WineHQ Bugzilla 25 Apr '25

25 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=52811 Bug ID: 52811 Summary: Apps starting with wrong non-client area decoration Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: leandrohr(a)riseup.net Distribution: --- Created attachment 72186 --> https://bugs.winehq.org/attachment.cgi?id=72186 Small client to reproduce the bug Arch Linux wine-6.0-rc1-11894-gafd7b319e56 --- # Bug description During the development of the Wine Wayland driver we've noticed a bug that also affects the X11 driver when using client-side decorations. Some applications start with the wrong decoration. It's a visual-only issue, as the application starts with focus and works nicely. But its non-client area starts with the decoration of inactive applications (greyed out). This is how it should start: https://share.collabora.com/index.php/s/tZQxBEaybgwGgpi But this is how it looks like: https://share.collabora.com/index.php/s/bQbASjTXg8oxg3W --- # How to reproduce You can easily reproduce this by running notepad with the X11 driver option "Decorated" set to "N". I wrote some small clients to debug this, and the simple program attached reproduces the issue. TLDR: it is a program that activates a window of a non-foreground thread and then tries to show it. --- # What I think is going on When we call SetActiveWindow(hwnd), hwnd does not become the foreground window, as the application thread is not the foreground thread yet (at this point the desktop window is the foreground window). SetActiveWindow() activates the non-client area only if the window is the foreground window, so we have activated the window but didn't activate its non-client area (which is correct AFAIU). Next we call ShowWindow(hwnd), and now the thread that owns hwnd should become foreground and SetActiveWindow(hwnd) is called. But as hwnd is already active it does nothing and returns, so the non-client area is draw as inactive. --- # Possible fix In order to fix this, we could change SetActiveWindow() behavior to the following: if (hwnd == current active window) if (hwnd == NtUserGetForegroundWindow() && non-client area of hwnd not active) activate non-client area of hwnd bail out I wrote a test for this, and I could see that this fix didn't break any other tests. I've decided to post here in order to know if the fix seems reasonable to you. Also, I had a question while debugging this and still couldn't figure out. I thought that focus was a global property related to the foreground window. But it seems that when a window is set to active the function to change the focus to it may also be called (even when the window does not belong to the foreground thread). So can a non-foreground window be active and have the focus? --- Thanks a lot! -- 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 6

[Bug 58158] New: Regression: Sacred Gold 2.28 ASE crashes when initialising multiplayer
by WineHQ Bugzilla 25 Apr '25

25 Apr '25

http://bugs.winehq.org/show_bug.cgi?id=58158 Bug ID: 58158 Summary: Regression: Sacred Gold 2.28 ASE crashes when initialising multiplayer Product: Wine Version: 7.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zergling.man42(a)gmail.com Distribution: --- Created attachment 78442 --> http://bugs.winehq.org/attachment.cgi?id=78442 git diff 3aa18cc5d01028bda126624ba5f5bfb11ebc4f77 8714eb2fef7182a9c73b9963493935decca89fdc Can be triggered by running Sacred.exe and navigating multiplayer -> any of the three options (local network, closed internet, open internet), or by running GameServer.exe. Causes an unhandled page fault on read access, probably in tincat2.dll. After two bisects, I believe it's caused by 3aa18cc5d01028bda126624ba5f5bfb11ebc4f77, but reverting it doesn't fix it. It's definitely somewhere between 7.2 and 7.3. -- 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 56431] New: Dotnet TreeView disappearing plus-sign
by WineHQ Bugzilla 25 Apr '25

25 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=56431 Bug ID: 56431 Summary: Dotnet TreeView disappearing plus-sign Product: Wine Version: 9.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Wagner.a18(a)yahoo.com Distribution: --- I try to get a dotnet application, which has a treeview element on board, running. If I expand a tree node to display the next level of child tree nodes with a press on the plus-sign and collapse the child tree node level with the minus-sign after that. The plus-sign disappears and I am not able to expand the tree node again. I have to restart the whole application to be able to expand the tree node again. I installed this packages - WINEPREFIX=~/.wine-32 winetricks vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2015 - WINEPREFIX=~/.wine-32 winetricks msxml3 - WINEPREFIX=~/.wine-32 winetricks msxml4 - WINEPREFIX=~/.wine-32 winetricks msxml6 - WINEPREFIX=~/.wine-32 winetricks mdac28 - WINEPREFIX=~/.wine-32 winetricks jet40 -- 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 32

[Bug 58155] New: Use space-saving APFS clones instead of copying file data blocks to each WINEPREFIX on macOS
by WineHQ Bugzilla 25 Apr '25

25 Apr '25

http://bugs.winehq.org/show_bug.cgi?id=58155 Bug ID: 58155 Summary: Use space-saving APFS clones instead of copying file data blocks to each WINEPREFIX on macOS Product: Packaging Version: unspecified Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com CC: dimesio(a)earthlink.net When a WINEPREFIX is created using Wine on macOS, files from the Wine .app are copied using actual copying of data blocks, instead of the space-saving Copy-on-Write cloning mechanism of APFS (Apple File System), which only references the already existing data blocks. When using Gcenx's macOS package builds, the data blocks of files are copied (from I believe Wine.app/Contents/Resources/wine/lib/wine/) to $WINEPREFIX/drive_c/windows/. This wastes over 300 MB of space for each WINEPREFIX created, which can add up, especially as it's recommended to install each Windows app in its own WINEPREFIX. They should instead use APFS CoW clones (similar to Linux btrfs reflinks). Solution: use APFS Copy-on-Write when creating WINEPREFIXes, so it is faster and saves space How?: using the macOS terminal command `cp -c` uses CoW see macOS's man pages for `cp(1)` and `clonefile(2)` macOS 10.14 Mojave man pages online: https://www.unix.com/man_page/mojave/1/cp https://www.unix.com/man_page/mojave/2/clonefile/ A Stack Exchange answer mentioning that macOS's "`cp -c` is equivalent to [Linux] `cp --reflink=always` (not `auto`), and will fail when copy-on-write is not possible": https://unix.stackexchange.com/a/504330 APFS was released for macOS devices on September 25, 2017, with the release of macOS 10.13 High Sierra. (https://en.wikipedia.org/wiki/Apple_File_System#History) Gcenx's Wine 10.0 and later package releases for macOS (https://github.com/Gcenx/macOS_Wine_builds/releases) only support macOS 10.15 Catalina and later. (macOS 10.12 Sierra though macOS 10.14 Mojave can be installed via MacPorts). How to test that Wine is not currently using APFS CoW clones: open Disk Utility before creating a new WINEPREFIX, click on your Container disk and look at the free space. Now create a new WINEPREFIX, the free space will decrease by about 300 MB. Delete the WINEPREFIX and empty the trash, watch the free space grow back -- 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 40994] New: Exits only from pull-down menu, then reports error.
by wine-bugs＠winehq.org 25 Apr '25

25 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=40994 Bug ID: 40994 Summary: Exits only from pull-down menu, then reports error. Product: Wine Version: 1.9.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: leslarkin(a)aim.com Distribution: --- Created attachment 55155 --> https://bugs.winehq.org/attachment.cgi?id=55155 Program error dump after program exit I can't exit by clicking on the 'x' in the red circle in the upper left corner of the app window. I also can't exit by right-clicking on the Wine icon in my Launcher bar, and clicking 'Quit'. The only way to exit is by clicking the app's 'Settings' pull-down menu, then clicking 'Exit'. After an apparently successful exit, I get an error window with the attached bactrace.txt file. -- 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 14738] New: Sacred Underworld crashes when opening a lan game
by wine-bugs＠winehq.org 25 Apr '25

25 Apr '25

http://bugs.winehq.org/show_bug.cgi?id=14738 Summary: Sacred Underworld crashes when opening a lan game Product: Wine Version: CVS/GIT Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kgbricola(a)web.de Created an attachment (id=15232) --> (http://bugs.winehq.org/attachment.cgi?id=15232) Sacred Underworld crash output when opening a lan game Sacred Underworld crashes when clicking "Multiplayer" -> "Local Network". The game version is 2.28. System: - Fedora 9 x86_64 (2.6.25.11-97.fc9.x86_64) - NVIDIA Geforce 8800GTS, proprietary driver 173.14.09 - Firewall disabled The game runs fine in single player mode. There is a demo version available but I think it doesn't have the multiplayer part. -- 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 16

[Bug 58157] New: Lollipop Chainsaw dont use all virtual desktop area (1024x768)
by WineHQ Bugzilla 24 Apr '25

24 Apr '25

http://bugs.winehq.org/show_bug.cgi?id=58157 Bug ID: 58157 Summary: Lollipop Chainsaw dont use all virtual desktop area (1024x768) Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Lollipop Chainsaw dont use all virtual desktop area (1024x768 in my case) In wine 10.0 and before work correctly using all virtual desktop area but in lastest wine dont use all area like wine 10.0 I leave some screenshots showing this problem Seeking some commits i think could have a relation with this commits: https://gitlab.winehq.org/wine/wine/-/merge_requests/7354 https://gitlab.winehq.org/wine/wine/-/merge_requests/6947 Thanks -- 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 6

[Bug 57925] New: winewayland.drv: Games are not filled to my monitor's resolution
by WineHQ Bugzilla 24 Apr '25

24 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=57925 Bug ID: 57925 Summary: winewayland.drv: Games are not filled to my monitor's resolution Product: Wine Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: daniel.penalized(a)proton.me Distribution: ArchLinux Created attachment 78178 --> https://bugs.winehq.org/attachment.cgi?id=78178 SWAT 4 output log (in this log I opened the settings and tried to set the maximum resolution that the game supports) Old games (specifically Ghost Recon, Splinter Cell 1, Splinter Cell 2 and SWAT 4) won't fill to my monitor's resolution, even if I switch to a higher resolution in the game settings. This MR (https://gitlab.winehq.org/wine/wine/-/merge_requests/6804) was supposed to work with winewayland.drv and fix this issue, but it doesn't work or fix it. However, this MR (https://gitlab.winehq.org/wine/wine/-/merge_requests/5057) does work and fixes that issue. There is a workaround (at least for SWAT 4): which is to take the game window out of fullscreen, then toggle the maximization state of the game window and put the game window back into fullscreen (In labwc/openbox terms: ToggleFullscreen > ToggleMaximize > ToggleFullscreen). I think it also works for Ghost Recon. Splinter Cell 1 even supports 16:9 resolutions, but only in game (in the menus, loadings and cut-scenes are still not filled in for my monitor's resolution) and Splinter Cell 2 is worse, there's no support for 16:9 resolutions or even a workaround. - I use labwc/wlroots as WM. - I'm using the new WoW64 mode. I did some tests with normal wine, but it's been a few weeks or months, so I'm not sure if the new WoW64 mode has any impact here, but I don't think so. (Sorry if the paraphrases seem disconnected from each other, if I'm not very clear or if I'm giving too little information. I've been doing a lot of testing over the last few hours and my mind isn't in a good place to come up with a good text here :/) -- 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 6

[Bug 58156] New: Star Wars: Jedi Knight - Dark Forces II Demo: won't launch, "smackw32.DLL" failed to initialize
by WineHQ Bugzilla 24 Apr '25

24 Apr '25

http://bugs.winehq.org/show_bug.cgi?id=58156 Bug ID: 58156 Summary: Star Wars: Jedi Knight - Dark Forces II Demo: won't launch, "smackw32.DLL" failed to initialize Product: Wine Version: 10.6 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78437 --> http://bugs.winehq.org/attachment.cgi?id=78437 Wine-devel 10.6 log for "wine jkdemo.exe -windowgui" the Star Wars: Jedi Knight - Dark Forces II Demo: won't launch, it says "smackw32.DLL" failed to initialize. This is a Windows 95 game demo I tried setting the Windows Version to Windows 10, Windows 95, and Windows 98 in winecfg. I also tried launching the demo with and without the windowgui flag: `wine jkdemo.exe -windowgui` as mentioned in AppDB HowTo section. This is a regression because a lot of users report this game demo as Gold in AppDB, including on macOS (https://appdb.winehq.org/objectManager.php?sClass=version&iId=10948) The jedi.exe file is a launcher GUI which works fine, but when clicking "Play Jedi Knight Demo" it fails with the error: `file` command info for: jkdemo.exe PE32 executable (GUI) Intel 80386, for MS Windows Unable to start the Jedi Knight Demo game program. Try running JK.EXE where you installed the Demo directly. Also make sure you have the latest DirectX drivers installed on your system. The macOS terminal shows this error as one of the last things in the log: "err:module:loader_init "smackw32.DLL" failed to initialize, aborting" (the module is normally unzipped next to the jkdemo.exe executable) tested with Gcenx's Wine-devel 10.6 (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.6) on macOS 11 and Wine-devel 9.21 (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/9.21) and Gcenx's Wine CrossOverFOSS 23.7.1-1 based on Wine 8.0.1 (https://github.com/Gcenx/winecx/releases/tag/crossover-wine-23.7.1-1) download page (choose Download this File > Agree > Jedi Knight Demo.zip): https://community.pcgamingwiki.com/files/file/1308-jedi-knight-dark-forces-… sha256: 7bc013918cf79879a086a10c27306f2f3511852726f4b4a9fec09668ed221d18 -- 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

← Newer
1
...
4
5
6
7
8
9
10
...
47
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 April 2025