June 2022 - Wine-bugs - list.winehq.org

[Bug 35331] New: Ellipse drawing problem using GM_ADVANCED graphics mode
by wine-bugs＠winehq.org 25 Feb '26

25 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=35331 Bug ID: 35331 Summary: Ellipse drawing problem using GM_ADVANCED graphics mode Product: Wine Version: 1.7.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: ralf.habacker(a)freenet.de Classification: Unclassified Painting Ellipses in GM_ADVANCED graphicsmode and using dc rotation set with SetWorldTranform fails. Instead of painting a rotated ellipse a still unrotated ellipse is drawn. The dc rotation only effects the height of the ellipse. -- 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.

3 23

[Bug 24851] New: Explorer++ treeview shows plus signs even when a folder contains no subfolders
by wine-bugs＠winehq.org 25 Feb '26

25 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=24851 Summary: Explorer++ treeview shows plus signs even when a folder contains no subfolders Product: Wine Version: 1.3.5 Platform: x86-64 URL: http://www.explorerplusplus.com/download OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Created an attachment (id=31446) --> (http://bugs.winehq.org/attachment.cgi?id=31446) terminal output On Windows, the little plus signs for expanding folders in the treeview don't appear next to folders that contain no subfolders (and thus, nothing to expand). In Wine, such folders still have the plus sign even though it doesn't do anything. Native comctl32 didn't help. -- 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 13

[Bug 42027] New: Xilinx Vivado 2014.4 installer fails: systeminfo is a stub
by wine-bugs＠winehq.org 25 Feb '26

25 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=42027 Bug ID: 42027 Summary: Xilinx Vivado 2014.4 installer fails: systeminfo is a stub Product: Wine Version: 2.0-rc1 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: jack.lovell(a)ukaea.uk Created attachment 56490 --> https://bugs.winehq.org/attachment.cgi?id=56490 Log output until the installer crashes. When trying to run the Xilinx Vivado 2014.4 web installer, the program crashes shortly after startup. A look at the log output suggests the installer is calling systeminfo and piping the output to findstr to get the OS version. However, systeminfo is a stub, and so outputs nothing to stdout. I plan to file the findstr stub as a separate bug report. -- 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.

3 10

[Bug 44820] New: Processes might terminate with incorrect exit code due to race-condition when threads are killed during shutdown
by wine-bugs＠winehq.org 25 Feb '26

25 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=44820 Bug ID: 44820 Summary: Processes might terminate with incorrect exit code due to race-condition when threads are killed during shutdown Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, to track https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-Thre… Unfortunately there is no further information/details, I just found this: https://wine-staging.com/news/2015-03-07-release-1.7.38.html -> https://github.com/wine-staging/wine-staging/blob/v1.7.38/debian/changelog --- quote --- * Added patch to fix race-condition when threads are killed during shutdown. --- quote --- https://github.com/wine-staging/wine-staging/blob/master/patches/ntdll-Thre… --- quote --- When exit_thread is executed, nb_threads is decremented before the thread is fully shutdown. When another thread runs ExitProcess() this will cause a SIGQUIT signal to all threads, effectively decrementing nb_threads twice. The process will terminate with a wrong exitcode then because the refcount reaches zero too early. Currently Wine has no locking protection of LdrShutdownProcess(), so it can only be executed safely when all other threads have terminated before. Most likely there are more Wine bugs in this area, but the attached patch should fix the most critical one (messed up refcounting of threads) for now. --- quote --- Sadly no applications are mentioned that could be used to validate the problem. $ wine --version wine-3.4 Regards -- 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 7

[Bug 37664] New: CUDA encoder does not work on MediaCoder x64 0.8.33 build 5680
by wine-bugs＠winehq.org 25 Feb '26

25 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=37664 Bug ID: 37664 Summary: CUDA encoder does not work on MediaCoder x64 0.8.33 build 5680 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rickardj42(a)gmail.com Distribution: --- Created attachment 50128 --> https://bugs.winehq.org/attachment.cgi?id=50128 Screenshot of the error message In MediaCoder x64 0.8.33 build 5680 attempting to select GPU encoder causes error "No supported acceleration hardware detected", dispite the presence of an NVidia GeForce 750ti in my system. Attempting to force GPU encoding using CUDA encoder results in Error (14) on all items(general encoder error). -- 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.

3 12

[Bug 23775] New: Text box is too small in 16-bit program. Only one line high, should be two.
by wine-bugs＠winehq.org 24 Feb '26

24 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=23775 Summary: Text box is too small in 16-bit program. Only one line high, should be two. Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Created an attachment (id=29800) --> (http://bugs.winehq.org/attachment.cgi?id=29800) Stellar Explorer 2.0b demo The 16-bit game Stellar Explorer 2.0b (attached) shows a problem with the size of a text box. The text box at the upper left of the window should show two lines of text. Running under Wine, it's only one line high and the scroll buttons at the right side consequently appear squashed. Run stellar2.exe. Click through the initial dialog boxes then select File->New from the menu and click OK. -- 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 14

[Bug 15346] New: Winamp disappears when you move it's location
by wine-bugs＠winehq.org 24 Feb '26

24 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=15346 Summary: Winamp disappears when you move it's location Product: Wine Version: 1.1.5 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: homerhomer(a)gmail.com Created an attachment (id=16178) --> (http://bugs.winehq.org/attachment.cgi?id=16178) DwmSetWindowAttribute error Sort of a silly bug, basically once winamp is up and running, if you click on the title bar and move it around winamp disappears. To make sure that the bug happens make sure to swirl it around a couple of times. ( A Swirly if you will ) Attached I also noticed this when running winamp manually at startup. This may be related. but then I move winamp and it disappears I don't get any more error messages. So I'm not sure. I appreciate the good work Thank you I'm running Ubuntu 8.04, Wine 1.1.5, AMD64 -- 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.

3 48

[Bug 49583] New: Assassin's Creed Odyssey displays black bars on top and bottom.
by WineHQ Bugzilla 24 Feb '26

24 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=49583 Bug ID: 49583 Summary: Assassin's Creed Odyssey displays black bars on top and bottom. Product: Wine Version: 5.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: GloriousEggroll(a)gmail.com Distribution: --- Created attachment 67739 --> https://bugs.winehq.org/attachment.cgi?id=67739 AC Odyssey black bar fix It's been a long known issue that AC: Odyssey renders with black bars on the top and bottom of the screen (see screenshot 1). Derek Lesho came up with a stub patch that both fixed this -and- allowed STEEP to run (it would not display previously). That patch can be found here: https://github.com/GloriousEggroll/proton-ge-custom/blob/5.12-GE-1/patches/… Recently, the relevant function QueryDisplayConfig was implemented, however it did not contain some of the changes Derek's patch adds. This allowed steep to work, however AC: Odyssey still retained the black bar issue. I modified Derek's patch by adding the relevant parts to QueryDisplayConfig, and removing the relevant flag checks (Derek's patch did this previously), and this allowed AC: Odyssey to render properly without the black bars. (see screenshot 2). The patch is hacky but may provide more information towards fixing this properly. -- 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 49393] New: Gag game crash
by WineHQ Bugzilla 24 Feb '26

24 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=49393 Bug ID: 49393 Summary: Gag game crash Product: Wine Version: 5.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: axet(a)me.com Distribution: --- Hello! I'm trying to run 'Gag' game. And it's crashing winmm reading at zero memory address. I've tested few wine versions 5.0.0 .. 5.10 and all have same issue. https://en.wikipedia.org/wiki/GAG_The_Impotent_Mystery If you want trying to run the game, you gonna need start X server with 16-bit display like this: Xephyr :1 -ac -screen 800x600x16 & Crash output: 5.10 Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x639d7db6). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:639d7db6 ESP:016cf7c0 EBP:00000001 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:00ca3e08 ECX:016cf760 EDX:000001d0 ESI:00000000 EDI:014afb1c Stack dump: 0x016cf7c0: 009b38b8 639ec090 00000001 00000000 0x016cf7d0: 00ca3e24 00000000 00000000 639d85b5 0x016cf7e0: 00ca3ed4 00000008 000000e8 7ea09ea0 0x016cf7f0: 00000001 016cf810 016cf8cc 016cf820 0x016cf800: 0000001c 7ffc4000 0000003f 00ca0cf0 0x016cf810: 00ca0cf0 016cf830 639efe20 00ca3e08 Backtrace: =>0 0x639d7db6 EntryPoint+0xffffffff() in winmm (0x00000001) 1 0x639d8688 EntryPoint+0xffffffff() in winmm (0x00ca3ed4) 2 0x639da5b9 EntryPoint+0xffffffff() in winmm (0x016cf918) 3 0x7ea1bd0c in user32 (+0x9bd0b) (0x016cf918) 4 0x7ea1c35d in user32 (+0x9c35c) (0x016cf968) 5 0x7ea1e5a3 in user32 (+0x9e5a2) (0x016cf9b8) 6 0x7e9db0f2 in user32 (+0x5b0f1) (0x016cfa28) 7 0x7e9dd6c7 in user32 (+0x5d6c6) (0x016cfe48) 8 0x7e9e32df in user32 (+0x632de) (0x016cfea8) 9 0x639d9949 EntryPoint+0xffffffff() in winmm (0x016cff5c) 0x639d7db6 EntryPoint+0xffffffff in winmm: cmpw $1,0x0(%eax) 5.0.0 Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x639d7b36). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:639d7b36 ESP:0127f700 EBP:00000001 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:0089e300 ECX:0127f6a0 EDX:0089e678 ESI:00000000 EDI:0105fb0c Stack dump: 0x0127f700: 0089c3c8 639eb090 00000001 00000000 0x0127f710: 0089e31c 00000000 00000000 639d8335 0x0127f720: 0089e3cc 00000008 000000e8 0127f750 0x0127f730: 0000000c 00030038 0127f768 7e925c50 0x0127f740: 7ea78cc0 7ffc4000 0000003f 0089c9f0 0x0127f750: 0089c9f0 0127f770 639eee20 0089e300 Backtrace: =>0 0x639d7b36 EntryPoint+0xffffffff() in winmm (0x00000001) 1 0x639d8408 EntryPoint+0xffffffff() in winmm (0x0089e3cc) 2 0x639da339 EntryPoint+0xffffffff() in winmm (0x0127f858) 3 0x7e93863c in user32 (+0xa863b) (0x0127f858) 4 0x7e938cad in user32 (+0xa8cac) (0x0127f8a8) 5 0x7e93b113 in user32 (+0xab112) (0x0127f8f8) 6 0x7e8f635e in user32 (+0x6635d) (0x0127f968) 7 0x7e8f8a7f in user32 (+0x68a7e) (0x0127fe38) 8 0x7e8fedca in user32 (+0x6edc9) (0x0127fe98) 9 0x639d96c9 EntryPoint+0xffffffff() in winmm (0x0127ff4c) 0x639d7b36 EntryPoint+0xffffffff in winmm: cmpw $1,0x0(%eax) -- 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 4

[Bug 45882] New: (Overwatch, several source games) Raw Mouse input not working
by wine-bugs＠winehq.org 24 Feb '26

24 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=45882 Bug ID: 45882 Summary: (Overwatch, several source games) Raw Mouse input not working Product: Wine Version: 3.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: florian98.rg(a)gmail.com Distribution: --- Playing Overwatch I've noticed that the game still uses mouse pointer speed even though on Windows it uses Raw Mouse input exclusively. I've tried this on any branch of Wine (staging, esync, whatsoever) and the problem still persists. This also happens in Valve games where you can enable Raw Mouse Input, e.g. Team Fortress 2 etc. This does not happen with the native ports of said games that use SDL to get mouse input. I already disabled any mouse acceleration in GNOME whatsoever (using the "Flat" Profile), however the problem persists. Is it possible to rewrite Wine to get Mouse input via SDL2 instead? That would help pave way for Wayland etc. 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.

3 34