wine-bugs September 2025

wine-bugs@winehq.org

1 participants
332 discussions

[Bug 58439] New: REGRESSION: trying to edit a text field immediately causes the previous content to be completely erased
by WineHQ Bugzilla 17 Sep '25

17 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58439 Bug ID: 58439 Summary: REGRESSION: trying to edit a text field immediately causes the previous content to be completely erased Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: scallegari(a)arces.unibo.it Distribution: --- Hi, I am recently experimenting a regression and even if I cannot say in which version it was introduced, I am almost sure it is not the last one (but before) and that it is indeed a regression (a few month ago the behavior was different). I am working with a software called LTspice (that is closed source but free, which surely helps repro) and available from https://www.analog.com/en/resources/design-tools-and-calculators/ltspice-si…. Incidentally, the developers of this code have traditionally been wine-friendly (even if they do not offer a linux version of their code, neither they provide support for running it in wine, they have tried to ensure that it could be used with wine). This software is a circuit simulator with a schematic capture component. You can pick and place components and edit the values of their parameters using some dialog boxes. Often there are multiple things that can be tuned and the dialog box is arranged as a sort of a table, where some cells are editable. In order to adjust things, until some simulation results are satisfactory, it is common to modify some parameters multiple times and in doing so it is good to be able to edit the previous value. Unfortunately, in recent times it has become impossible to do so when running the software with wine. As soon as you try to modify a value, the value disappears and you remain with an empty field to be filled from scratch. -- 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 58708] New: Internet Download Manager: Right-clicking in empty list of downloads displays context menu in wrong position
by WineHQ Bugzilla 17 Sep '25

17 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58708 Bug ID: 58708 Summary: Internet Download Manager: Right-clicking in empty list of downloads displays context menu in wrong position Product: Wine Version: 10.14 Hardware: x86-64 URL: https://mirror2.internetdownloadmanager.com/idman642bu ild43.exe OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tobbi.bugs(a)googlemail.com I cannot tell if this is a problem with Internet Download Manager or with Wine. Anyway: Steps to reproduce: 1. Download and install "Internet Download Manager". 2. Open IDM and right-click inside the empty list of downloads. Expected results: Context menu opens near the mouse pointer. Actual results: Context menu opens in the center of the list. % openssl sha256 idman642build43.exe SHA2-256(idman642build43.exe)= 3f79c4f6451e76bfad0236c9523bb827b14d3ce87c589f2b8aca58210ecf9a2c -- 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 58702] New: Update to 10.15 breaks Bricklink Studio
by WineHQ Bugzilla 17 Sep '25

17 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58702 Bug ID: 58702 Summary: Update to 10.15 breaks Bricklink Studio Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bonizak(a)gmail.com Distribution: --- Created attachment 79304 --> http://bugs.winehq.org/attachment.cgi?id=79304 wine backtrace file Bricklink's Studio Version 2.25.8_1, was running fine under 10.14 dev but the update to 10.15 last night has broken Studio. Studio window will open copying the focus window image but otherwise is blank. -- 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 58704] New: io_uring support for Wine
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58704 Bug ID: 58704 Summary: io_uring support for Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: k.kahurani(a)gmail.com Distribution: --- This issue mostly relates to the server(for filesystem operations), it seems like the networking implementation could be done outside the server. Just throwing this out there, it's highly unlikely I will work on it for various reasons. Wine still doesn't have io_uring support though, quite a few projects have already implemented io_uring support. Wine would also do with any performance benefits. io_uring is at least promoted as performance oriented, this makes it very interesting. io_uring offers performance benefits in multiple fronts. -> The first and probably the simplest is where operations on file might not have to make calls to 'fget'; typically when an operation is executed on files in Linux, it will involve some call to 'fget' one way or the other. With io_uring, it's possible to register files so that this 'fget' call is avoided. I am not sure how much performance benefit that could achieve. But, still an optimization nonetheless. Similarly, you could register buffers for opcodes(which translate to syscalls) so they're validated, mapped and so on so forth beforehand. When the actual operations/syscall are being executed, this boilerplate is not called. That is also an optimization. -> io_uring allows submitting a batch of syscalls(opcode operations) via one single syscall. This is an optimization, because, of course, without io_uring, you'd have to make multiple syscalls to achieve the same. However, it only seems like this optimization would only be applicable when making very many syscalls and making them very fast otherwise when making singular syscalls, they have to wait until the batch is full and hence would introduce some latency in low throughput situations. -> There might be other optimizations that I have not considered. What interests me most, though, is the syscall/request polling feature which allows applications to submit syscalls(opcode) via zero syscalls. io_uring sets up a kernel thread which polls the io ring and hence when submissions are made, the thread will discover them without any syscalls been made. This is very interesting and would be a straightforward mega-optimization were it not for that fact that the created kernel thread does pin a CPU. Would this work well with other work that's competing for CPU? It's consequently not very clear whether this would be an improvement to Wine, which makes syscalls alongside and in the midst of doing other heavy work. Any thoughts? -- 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 58582] New: Rainmeter 4.5.23: crashes on X11 after refreshing default skin Clock.ini
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58582 Bug ID: 58582 Summary: Rainmeter 4.5.23: crashes on X11 after refreshing default skin Clock.ini Product: Wine Version: unspecified Hardware: x86-64 URL: https://github.com/rainmeter/rainmeter/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: castelei(a)yahoo.com Regression SHA1: 980a2e3c65bee1422adbe06fead768669835e3e1 Distribution: --- Created attachment 79106 --> http://bugs.winehq.org/attachment.cgi?id=79106 WINEDEBUG=+synchronous,+seh Rainmeter 4.5.23 Reproduction: 1) Click on the Rainmeter icon on the system tray to open the 'Manage Rainmeter' window. 2) Click on the 'Active skins' drop-down list and select illustro\Clock\Clock.ini 3) Click the 'Refresh' button to the right. This X11 error prints as the application crashes if run without +synchronous: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 139 (RENDER) Minor opcode of failed request: 4 (RenderCreatePicture) Serial number of failed request: 15285 Current serial number in output stream: 15292 Found this regression on a merged patch newer than 10.12 (the newest development release at this time) while working on an unrelated bug. -- 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 57806] New: visual and response lags in Guitar Pro v8.1.3 (build 121)
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57806 Bug ID: 57806 Summary: visual and response lags in Guitar Pro v8.1.3 (build 121) Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: acidbong(a)tilde.club Distribution: --- Created attachment 78013 --> https://bugs.winehq.org/attachment.cgi?id=78013 Guitar Pro in Wine-9.20 I've been using Wine-staging for running Guitar Pro on Linux (Gentoo, then NixOS), and it's been smooth until 9.20 -> 9.22 update (https://github.com/NixOS/nixpkgs/pull/359908, nixpkgs maintainers skipped v9.21). Then visual lags (constant, as if the program runs at 5 FPS) started to happen. Welp, they aren't solely visual, responsiveness also suffers. Audio, however, doesn't lag and is still smooth. The lag is also present on Wine10. Regression also confirmed on Wine-development v9.22 and with a demo version of the program and on different PCs (first on an Intel-based laptop (Core i3-7100), then on an AMD-based one (AMD Ryzen 5 5500U)), both with integrated GPUs. Camera recording (not screen capture, because `simplescreenrecorder` (haven't tried other tools) for some reason reduced these lags): https://0x0.st/8KNw.mp4 Logs are attached below. -- 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 58703] New: Fedora 42: Suddenly getting checksum errors
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58703 Bug ID: 58703 Summary: Fedora 42: Suddenly getting checksum errors Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: johnny.jy.ooi(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- Recently, while trying to do the standard "dnf upgrade", my system sees updates for wine-staging and winehq-staging, but upon triggering the upgrade, I get checksum errors Total size of inbound packages is 226 MiB. Need to download 226 MiB. After this operation, 6 MiB extra will be used (install 1 GiB, remove 1 GiB). [1/2] winehq-staging-1:10.15-1.1.x86_64 100% | 144.6 KiB/s | 75.0 KiB | 00m01s >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc [2/2] wine-staging-1:10.15-1.1.x86_64 0% | 3.3 MiB/s | 1.7 MiB | 00m01s >>> Not finished - interrupted by error: Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bd ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [2/2] Total 100% | 3.4 MiB/s | 1.8 MiB | 00m01s Failed to download packages Librepo error: Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfcbfea6(sha256) I've tried removing the winehq.repo, reimporting the repo key (https://dl.winehq.org/wine-builds/winehq.key), readding the repo according to the instructions, and doing "dnf clean" and it keep failing the checksum checks. I know there's been some issues with the repo in the past, do we have another similar issue? -- 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 50242] New: Lotus Approach crashes on start up
by WineHQ Bugzilla 15 Sep '25

15 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=50242 Bug ID: 50242 Summary: Lotus Approach crashes on start up Product: Wine-staging Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68752 --> https://bugs.winehq.org/attachment.cgi?id=68752 Approach crash on start up Dear Wine Staging Maintainers, Fedora 33 wine-5.22-1.fc33.x86_64 As of 5.22, Lotus Approach now crashes on start up. Word Pro is okay. I have attached the trace. -T -- 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 33

[Bug 58558] New: In the Neverwinter Nights 1.69 toolset, the 3D areas have stopped working.
by WineHQ Bugzilla 15 Sep '25

15 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58558 Bug ID: 58558 Summary: In the Neverwinter Nights 1.69 toolset, the 3D areas have stopped working. Product: Wine-staging Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vivienne.lumina(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- The Neverwinter Nights 1.69 Toolset has been working well in wine for more than 15 years. Now for the first time using wine-staging 10.11 and newer, the 3d area window fails to show. -- 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 58701] New: World of Warcraft: When launching a classic version of wow the windows is not fullscreen
by WineHQ Bugzilla 14 Sep '25

14 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58701 Bug ID: 58701 Summary: World of Warcraft: When launching a classic version of wow the windows is not fullscreen Product: Wine-staging Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pally.squatter102(a)passfwd.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 79303 --> http://bugs.winehq.org/attachment.cgi?id=79303 How the game launches together with the taskbar When I open up world of warcraft classic the game screen is not in fullscreen mode, it sets the game resolution to a custom to make space for taskbar. If you rightclick on wow task in the taskbar and tick the fullscreen checkbox it works fine, but if you close down the game and open up wow classic again it's back ot the custom game resolution to fit the taskbar into the screen. I have tried several versions of Wine, but since it happens with wine-staging I have a feeling it's somehwere there. Sadly I can't test older version of wine anymore since an update with the Blizzard Update Agent not waking up, which was solved in 10.1. I have seen people report this problem for the retail version of wow as well but works for me there so I can't really report it. There is a lutris thread asking about this issue as well. https://forums.lutris.net/t/world-of-warcraft-doesnt-go-fullscreen-anymore/… -- 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

← Newer
1
...
21
22
23
24
25
26
27
...
34
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 September 2025