November 2025 - Wine-Bugs - list.winehq.org

[Bug 50133] New: Command line: Issues in some generic commands
by WineHQ Bugzilla Aug. 10, 2026

Aug. 10, 2026

https://bugs.winehq.org/show_bug.cgi?id=50133 Bug ID: 50133 Summary: Command line: Issues in some generic commands Product: Wine Version: 5.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: Psycho-A(a)yandex.ru Distribution: --- Continuing exploring native CMD.exe issues... 1) TYPE command can't read from UTF-8 and UTF-16 files. Windows can do it since Win2000. 2) MOVE command doesn't support /Y key for overwriting target files. Also, the command still can't move between disk partitions, and haven't produce any output on moving files operation. 3) PAUSE command's output text have no line-breaking, so any further text will be merged with same line. 4) TASKLIST command does nothing. 5) TASKKILL command have no /T key for killing processes tree. -- 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 55653] New: Logitech Extreme 3d Joystick has axes mapped incorrectly
by WineHQ Bugzilla Aug. 10, 2026

Aug. 10, 2026

https://bugs.winehq.org/show_bug.cgi?id=55653 Bug ID: 55653 Summary: Logitech Extreme 3d Joystick has axes mapped incorrectly Product: Wine Version: 8.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: jonathan(a)jdcox.net Distribution: --- Using the jstest utility the joystick reports this: Joystick (Logitech Logitech Extreme 3D) has 6 axes (X, Y, Rz, Throttle, Hat0X, Hat0Y) wine control shows that Rz is mapped to the Z axis and the throttle is mapped to the Rz axis in wine. These two should be flipped. I have tested with SDL disabled and enabled and I get the same behavior. This occurs in current wine and in current proton releases. The problem does not occur in Proton 6 series, but does with 7 and later. I am aware this bug tracker is for wine, but using Proton was the best way to test an older, albeit heavily patched, version of wine that I am currently aware of. This issue is a problem because games in the X-Wing and Tie Fighter series of games treat the rudder (or accidental joystick rotation on this cheap joystick) as throttle movements and constantly adjust throttle during gameplay. -- 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 27

[Bug 58683] New: "Frame" sample from Win32++ does not show the Menu
by WineHQ Bugzilla Aug. 9, 2026

Aug. 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=58683 Bug ID: 58683 Summary: "Frame" sample from Win32++ does not show the Menu Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- Created attachment 79277 --> http://bugs.winehq.org/attachment.cgi?id=79277 Screenshot in Wine 10.14 (KO) The Win32++ framework website: http://win32-framework.sourceforge.net/ The attached .exe is not showing the "File Edit View" Menu in Wine as it does in Windows. Sample application from https://jira.reactos.org/secure/attachment/61319/Frame.zip Seen in https://jira.reactos.org/browse/CORE-17940 and Wine is also affected -- 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 3

[Bug 51722] New: WinSpyEx doesn't show tab control properly, issues with overlapping controls
by WineHQ Bugzilla Aug. 9, 2026

Aug. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=51722 Bug ID: 51722 Summary: WinSpyEx doesn't show tab control properly, issues with overlapping controls Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 70603 --> https://bugs.winehq.org/attachment.cgi?id=70603 How it looks like on Win7 This is a purely cosmetic issue, it still works like you'd expect. -- 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 5

[Bug 58325] New: wined3d swapchain use-after-free
by WineHQ Bugzilla Aug. 9, 2026

Aug. 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=58325 Bug ID: 58325 Summary: wined3d swapchain use-after-free Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: yshuiv7(a)gmail.com Distribution: --- Releasing the swapchain brings us to wined3d_swapchain_cleanup, which destroys the front/back buffer textures. Texture destruction is async, happening on the device's command stream. This means these textures can be destroyed way after the swapchain itself. But we did set `texture->swapchain` to `NULL` before queuing their destruction, so that bit is fine. The problem is in texture_resource_unload. Here we try to acquire the context, which goes adapter_gl_acquire_context -> wined3d_context_gl_acquire -> wined3d_context_gl_activate -> wined3d_context_gl_update_window. And here we try to access `context_gl->c.swapchain->win_handle`, which unfortunately points to the swapchain that was just freed. I am unsure what's the fix for this. Do we hold a refcount of the swapchain in the context? Do we clear `context->swapchain` when a swapchain is being freed? Should we release the front/back buffer synchronously? Or something else? -- 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 57828] New: Approach Smart Icons do not show
by WineHQ Bugzilla Aug. 8, 2026

Aug. 8, 2026

https://bugs.winehq.org/show_bug.cgi?id=57828 Bug ID: 57828 Summary: Approach Smart Icons do not show Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com Distribution: --- Created attachment 78036 --> https://bugs.winehq.org/attachment.cgi?id=78036 Smart Icon in Windows 10 and Wine SmartSuite-N99.8.0208.0800 Fedora 41 wine-devel-10.1-1.1.x86_64 and wine-stable-10.0.0-1.1.x86_64 winehq-stable-10.0.0-1.1.x86_64 In Approach, the View pull down, Smart Icon setting does not active. This makes Approach very difficult to use. -- 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 33

[Bug 57633] New: Lotus Approach and Word Pro have graphic issues with high resolution monitors
by WineHQ Bugzilla Aug. 8, 2026

Aug. 8, 2026

https://bugs.winehq.org/show_bug.cgi?id=57633 Bug ID: 57633 Summary: Lotus Approach and Word Pro have graphic issues with high resolution monitors Product: Wine-staging Version: 10.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal 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: --- Lotus Approach N99.8.0208.0800 (Smart Suite) Fedora 41 Xfce 4.18 screen resolution: 4096x2160 (4k) Reproduced under: WineHQ Staging: wine-staging-10.0.rc3-1.1.x86_64 winehq-staging-10.0.rc3-1.1.x86_64 Wine Staging Fedora repo: wine-9.15-1.fc41.x86_64 wine-9.15-1.fc41.i686 When Lotus Approach are started from the command line $ wine approach $ wine wordpro Approach menu bars will not paint, but they are there if you remember where to click. Spreadsheet with flicker/flash when you click on their tabs. Wordpro will have artifacts of different parts of WorPro's screen. Typing will sometimes not appear unless you move the window to another part of the screen, then the typing, which really is there, will appear. But if you move the windows back where it came from, the typing will disappear again. But when both are started as a "virtual Desktop", it does not. $ cd .wine/drive_c/lotus/approach/ $ wine explorer /desktop approach From Xfce Launcher: bash -c "cd $HOME/.wine/drive_c/lotus/approach; wine explorer /desktop=`date +%%H:%%M:%%S`_wine_virtual_desktop_1680x1050,1680x1050 approach.exe" If would be great to break Approach and Wordpro free of the virtual desktop as it would allow my accounting spreadsheets to be seen fully without having to scroll back and forth. This would be wonderful. Many thanks, -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.

2 5

[Bug 58330] New: Ami Pro 3.1 crashes
by WineHQ Bugzilla Aug. 8, 2026

Aug. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=58330 Bug ID: 58330 Summary: Ami Pro 3.1 crashes Product: Wine Version: 10.9 Hardware: x86-64 URL: https://archive.org/download/lotussmartsuiterelease3.1 forwindows/Lotus%20SmartSuite%20Release%203.1%20for%20 Windows.zip OS: Linux Status: NEW Keywords: download, win16 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Blocks: 19660, 46232 Distribution: Ubuntu Created attachment 78701 --> http://bugs.winehq.org/attachment.cgi?id=78701 Wine 10.9 backtrace Lotus Ami Pro 3.1 crashes after a few seconds of loading. There are similar bugs, but the backtraces are different: Bug 46232, Bug 19660 =>0 0x0f4f:0x0476 (0x09ef:0x5e34) 1 0x011f:0x044a in krnl386.exe16 (+0xa248) (0x09ef:0x5e72) 2 0x7e731115 K32WOWCallback16Ex+0x5b8(vpfn16=<couldn't compute location>, dwFlags=<couldn't compute location>, cbArgs=<couldn't compute location>, pArgs=<couldn't compute location>, pdwRetCode=<couldn't compute location>) [/home/test/wine-git/dlls/krnl386.exe16/wowthunk.c:504] in krnl386.exe16 (0x01088168) 3 0x00004f03 (0x00005e72) I tried bisecting but I was hit by a host of different bugs and incomplete backtraces so I had to give up. To work around Bug 58329 I installed with 60709d197926e78ec2d1e3d6d53620c801766ca5. -- 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 19661] New: Lotus Approach 3.1 causes a page fault on load
by wine-bugs＠winehq.org Aug. 8, 2026

Aug. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=19661 Summary: Lotus Approach 3.1 causes a page fault on load Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: NEW Keywords: win16 Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Created an attachment (id=22944) --> (http://bugs.winehq.org/attachment.cgi?id=22944) Wine 1.1.27 console output Lotus Approach 3.1 causes a page fault on loading and has to be killed. -- 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 27

[Bug 39439] New: calling CreateProcess from windows code on a program binary mounted with noexec crashes wine
by wine-bugs＠winehq.org Aug. 8, 2026

Aug. 8, 2026

https://bugs.winehq.org/show_bug.cgi?id=39439 Bug ID: 39439 Summary: calling CreateProcess from windows code on a program binary mounted with noexec crashes wine Product: Wine Version: 1.7.51 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: hramrach(a)gmail.com Distribution: --- I moved a windows application from a failed disk partition to a flash drive. I mounted the flash drive using pmount which adds the noexec flag. Executing the application as in wine ./Client.exe works. However, the application also spawns Client.bin (presumably using CreateProcess) and that binary crashes on start when spawned from noexec filesystem. It raises an exception very early in Wine code so I guess the application is in no position to catch it. And it raises it in the spawned application, not the spawning application. The Client.bin itself is not executable (as in +x mode). I can add traces if needed but this should be easy to reproduce. I see multiple related problems here 1) wine does not check the noexec flag when loading a binary initially from the commandline but does check it (or uses a library function that does) when a windows application calls spawn or clone or whatever - inconsistency 2) wine checks the noexec in the wrong place - it should check before performing CreateProcess and report error in the calling application but it fails executing the created process and crashes 3) when wine fails executing an application due to the noexec flag it should produce an intelligible error message rather than crash -- 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 6