wine-bugs

wine-bugs@winehq.org

1 participants
159456 discussions

[Bug 41024] New: Failure to install
by wine-bugs＠winehq.org 30 Sep '25

30 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=41024 Bug ID: 41024 Summary: Failure to install Product: Wine Version: 1.8.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: leo_one(a)telus.net Distribution: --- Created attachment 55190 --> https://bugs.winehq.org/attachment.cgi?id=55190 config.log shows compilation failure Attempts to install wine-1.8.3 fail to compile. config.log attached. -- 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 58142] New: Teraterm 5.4.0 / Serial communication not functional
by WineHQ Bugzilla 30 Sep '25

30 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58142 Bug ID: 58142 Summary: Teraterm 5.4.0 / Serial communication not functional Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janne.kekkonen(a)gmail.com Distribution: --- tested with wine 10.5-staging When data is sent to serial port that is opened with TeraTerm, GUI becomes very sluggish and data received is not shown on the terminal. When data sending is stopped. Received data is shown and GUI responsivenes becomes normal. This behavior seems very similar that is described in bug(s): 57246 and 50591. Download link: https://github.com/TeraTermProject/teraterm/releases Side note: Wine registry do not have serial port friendly name information. Teraterm needs to be started with command line parameter which defines port: wine ttermpro.exe /C=2 -- 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 7

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

30 Sep '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 3

[Bug 58735] New: Wine 10.15 crash (c0000005) on Arch Linux with nvidia drivers
by WineHQ Bugzilla 29 Sep '25

29 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58735 Bug ID: 58735 Summary: Wine 10.15 crash (c0000005) on Arch Linux with nvidia drivers 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: ilya.laguxa(a)gmail.com Distribution: --- Created attachment 79357 --> http://bugs.winehq.org/attachment.cgi?id=79357 Debug log output of wineboot -u System Information: - Arch Linux x86_64 - Kernel: Linux 6.16.8-arch3-1 - Window Manager: Openbox 3.6.1 (X11) - Laptop: HP Omen 15, Ryzen 7 4800H, NVIDIA RTX 2060M - Bumblebee for hybrid graphics Launching wineboot -u (or any other wine command) on a fresh prefix (~/.wine) hangs indefinitely. Ctrl+C does not interrupt. Removing NVIDIA drivers and using amdgpu allows Wine to run correctly. With NVIDIA drivers installed, Wine immediately crashes with access violation (c0000005). I can only terminate wineboot by running: wineserver -k Steps Taken: Verified 32-bit libraries installed (lib32-nvidia-utils, Vulkan working) LANG=C, clean user, WINEARCH=win64 Tested on fresh prefix Tested on an old kernel, same result glxinfo shows NVIDIA RTX 2060 nvidia-smi works correctly nvidia and amdgpu modules are loaded I have no custom xorg.conf Other Wine builds such as staging or AUR and proton don't work with same behavior -- 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 58741] New: Maintainer requests should only be submittable once
by WineHQ Bugzilla 28 Sep '25

28 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58741 Bug ID: 58741 Summary: Maintainer requests should only be submittable once Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 URL: https://appdb.winehq.org/objectManager.php?sClass=main tainer&sState=queued&sTitle=Maintainer%20Queue OS: Linux Status: NEW Keywords: download, source Severity: minor Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: --- Created attachment 79371 --> http://bugs.winehq.org/attachment.cgi?id=79371 Screenshot A user can currently submit as many requests to maintain an application as they want, effectively spamming the queue. There's no reason for there to ever be more than one request per user per application (or version). -- 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 6254] riched32: Various Programms need EM_FORMATRANGE (Installer infinite loop from richtext error / wordpad: Printed Page is only white / Also affected: Half-Life, Endnote X5 Demo, ZMud, MukClient )
by WineHQ Bugzilla 28 Sep '25

28 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=6254 --- Comment #94 from Alban Browaeys <prahal(a)yahoo.com> --- (In reply to James McKenzie from comment #71) > This bug has not been forgotten, but AJ wanted this function implemented in > a different way that is correct. First EM_DISPLAYBAND must be implemented > and then EM_FORMATRANGE. This is being investigated. Hi James. Are there more details about what AJ envisioned that you could share so as not to get lost? Or is implementing EM_DISPLAYBAND first, then EM_FORMATRANGE, all there is to it? (In reply to James McKenzie from comment #67) > Also, I have been instructed by AJ to let this lie for a little while and come > back to it. The code is NOT correct to fix the problem. > Mr. Smith has a .plan to implement a lot of the functionality within Richedit. Do you know if these plans have been abandoned since? -- 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 58740] New: Alt keys not recognized on macOS
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58740 Bug ID: 58740 Summary: Alt keys not recognized on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com the Alt keys are not recognized on macOS. There is no input registered with either Alt key. The Mac Cmd (https://en.wikipedia.org/wiki/Command_key) keys instead register as Alt Using KeyboardStateView (Windows keyboard on-screen viewer utility): the left Cmd key registers as both: * Left MENU key (key code 164) * ALT key (key code 18) the right Cmd key registers as both: * Right MENU key (key code 165) * ALT key (key code 18) KeyboardStateView v1.00 homepage: https://www.nirsoft.net/utils/keyboard_state_view.html download: https://www.nirsoft.net/utils/keyboardstateview.zip sha256: b8ea99128e5ec854f3ce2596177687538f8d2b802943f35a223795d9452a0cd5 my system: macOS 11 tested with: Wine-stable 9.0, 10.0, Wine-devel 10.14 -- 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 58729] New: various bugs in Jedi Knight - Dark Forces II Demo (macOS)
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58729 Bug ID: 58729 Summary: various bugs in Jedi Knight - Dark Forces II Demo (macOS) Product: Wine Version: 10.14 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com This is a new bug report following my previous bug report (bug# 58156). In the previous bug report, the game Jedi Knight - Dark Forces II Demo could not launch at all on macOS, with the following error: > "err:module:loader_init "smackw32.DLL" failed to initialize, aborting" As of Wine-devel 10.14, this game is now playabale again but only with workaround and caveats. (comments cross-posted as well in bug# 58156) my system: macOS 11 game demo download page (choose Download this File > Agree > Jedi Knight Demo.zip): https://community.pcgamingwiki.com/files/file/1308-jedi-knight-dark-forces-… sha256: 7bc013918cf79879a086a10c27306f2f3511852726f4b4a9fec09668ed221d18 ---- To play the game, you have to launch the JEDI.EXE launcher app (not the JKDEMO.EXE game app) and click "Play Jedi Knight Demo"... After clicking "Play Jedi Knight Demo": 1. the game app will be launched to an all-black fullscreen and tries to change the screen resolution 2. the game app will minimize itself to the macOS Dock after 1 to 3 seconds 3. the same error pop-up as in my first post will show up: > 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. Clicking the minimized game app from the macOS Dock (grayscale Jedi icon) will return the game app to fullscreen, with an all-black fullscreen and the intro video music playing in the background. Pressing Esc will skip the all-black intro video and correctly load the main menu and the game is playable! Press the equals key to increase the game viewport to fill the screen. ### NOTES: 1. if you choose "Cutscenes" from the main menu and press OK to play the Splash movie (intro movie), it will now play correctly 2. if you switch out of (Cmd-Tab) and return to the game from: * the all-black intro video (before pressing Esc to skip): the game correclty returns to the all-black intro video * the main menu: the main menu will now be all black, but the sounds still play when clicking your mouse and pressing Esc * the correctly-playing intro video from the Cutscenes menu: the game returns to an all-black intro video, but if you skip it (Esc), the main menu will display correctly * gameplay: the game viewport will be all the way off-screen to the top of the screen, meaning only the bottom 20% of the game can be seen (press the equals key to increase the in-game viewport). If you press Esc the pause menu still appears correctly * the pause menu, activated for the first time from gameplay: the game returns to an all-black pause menu, and pressing Esc returns the game viewport being off-screen to the top as before * the pause menu, activated for a second time from gameplay: the pause menu correctly reappears, but after returning to gameplay, the game viewport is still off to the top of the screen 3. if you close all macOS Terminal windows (which normally exits all wine processes), the game app will still be running, but the error pop-up will be killed. The game can be exited by force-quitting the wine processes in macOS Activity Monitor or Force Quit dialog I also bisected this with Wine-devel 10.12 and 10.13, and they both give the same error as in my first post: > "smackw32.DLL" failed to initialize, aborting so this was fixed in Wine-devel 10.14 I am using the official WineHQ/Gcenx binary from Homebrew/GitHub: https://formulae.brew.sh/cask/wine@devel https://github.com/Gcenx/macOS_Wine_builds/releases/download/10.14/wine-dev… -- 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 58592] New: Font substitution partially broken - regression
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58592 Bug ID: 58592 Summary: Font substitution partially broken - regression Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zdenek.koprivik(a)post.cz Distribution: --- While trying to replace "Tahoma" with "Noto Sans Regular" (the default Plasma desktop font), I've encountered an issue, where the font replacement does not work in some cases. Since I'm migrating from a very old system with Wine 1.6.2, I know that the font replacement used to work for the exact same binary and the same UI elements. I've set the following registry keys: [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Tahoma"="Noto Sans Regular" "Segoe UI"="Noto Sans Regular" "MS Shell Dlg"="Noto Sans Regular" "MS Shell Dlg 2"="Noto Sans Regular" The issue can be reproduced by opening the file dialog in the built-in registry editor. Running the built-in registry editor I've got the main font changed to "Noto Sans Regular" as expected, but in the file open dialog for import, there is still "Tahoma". When I'm browsing for directories, the font changes to "Noto Sans Regular", but when an item is selected, the font changes back to "Tahoma". Here is a short video showing the issue: https://imgur.com/a/l0BhsB8 This is only one example of the non-working substitution. The "Tahoma" is also rendered on the buttons and almost everywhere around in the dialog. I'm using the substitution mostly for MikroTik network equipment management apps (WinBox and The Dude) to improve the readability. It is working fine when running the exact same binaries on the old PC with Wine 1.6.2, but I can't get it to work with the newest Wine. The system is KDE neon User, Plasma 6.4.4, Wine 10.12 from the WineHQ PPA. -- 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 49780] New: wineconsole reports VT sequence support when it does not
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=49780 Bug ID: 49780 Summary: wineconsole reports VT sequence support when it does not Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: magiblot(a)hotmail.com Distribution: --- Created attachment 68092 --> https://bugs.winehq.org/attachment.cgi?id=68092 Demo application to reproduce the issue Wineconsole does not support applications writing Virtual Terminal sequences through the Console API. That's fine. However, when enabling the console ENABLE_VIRTUAL_TERMINAL_PROCESSING mode on stdout with SetConsoleMode, no error is returned, so the application has no way to detect whether VT sequences are supported or not. This is documented in https://docs.microsoft.com/en-us/windows/console/setconsolemode. The port of Turbo Vision at https://github.com/magiblot/tvision is affected by this. When using the Console API, Turbo Vision prefers VT sequences over SetConsoleCursorPosition/SetConsoleTextAttribute for code reusability and performance. Nevertheless, it can fall back to the latter method when SetConsoleMode fails to enable either ENABLE_VIRTUAL_TERMINAL_PROCESSING or DISABLE_NEWLINE_AUTO_RETURN. Since SetConsoleMode does not return error on wineconsole, garbage is shown instead of a colorful interface. STEPS TO REPRODUCE To reproduce the issue on Turbo Vision: (A) - Using the attached 'tvdemo.exe' 1. Run the application on wineconsole. You should see a black-and-white background and escape sequences drawn on the console. 2. Press Alt+F, then D. You should see the command prompt, and the message "VT enabled" at the top, which demonstrates the issue in SetConsoleMode. (B) - Compiling from source code (requires up-to-date CMake and MSVC). 1. Insert the following code after line 63 in source/linux/win32con.cpp (https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63…): ``` if (supportsVT) cerr << "VT enabled" << endl; else cerr << "VT not enabled: " << GetLastError() << endl; ``` 2. Follow the build instructions at https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63… 3. Follow the steps in (A). EXPECTED BEHAVIOUR On Windows, support for VT sequences can be disabled by turning on the "Legacy Console" mode. If tvdemo.exe is ran in these conditions, the interface is displayed properly. If entering the command prompt by pressing Alt+F, then D, the message "VT not enabled: 87" is displayed (error 87 stands for ERROR_INVALID_PARAMETER), which is what should be shown on wineconsole as well, since it clearly does not support VT sequences. Thank you! -- 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 13

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