March 2025 - Wine-bugs - list.winehq.org

[Bug 55325] New: msiexec.exe office 2016 on manjaro
by WineHQ Bugzilla 01 Jun '25

01 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=55325 Bug ID: 55325 Summary: msiexec.exe office 2016 on manjaro Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juanpablocacioli(a)gmail.com Distribution: --- Created attachment 74922 --> https://bugs.winehq.org/attachment.cgi?id=74922 This is the report of the errror Try installing office 2016 and 2010 on manjaro linux gnome. During the installation process this error appears, I send an attached file with the 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.

1 3

[Bug 40436] New: huge sound latency delay in some games
by wine-bugs＠winehq.org 01 Jun '25

01 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=40436 Bug ID: 40436 Summary: huge sound latency delay in some games Product: Wine Version: 1.9.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: validemail(a)mailinator.com Distribution: --- Games such as Spooky's House of Jump Scares and Barkley, Shut Up and Jam: Gaiden have a huge sound delay of nearly a second when using either the alsa driver or the pulseaudio driver. dsound and directmusic are installed as components in order to ensure that every single sound from the game actually plays. The bug does not appear to affect an rpgmaker game called Space Funeral, however the above titles have it very noticeably. -- 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 49515] New: Star Wars: The Old Republic unable to patch on Debian but works on Mint
by WineHQ Bugzilla 31 May '25

31 May '25

https://bugs.winehq.org/show_bug.cgi?id=49515 Bug ID: 49515 Summary: Star Wars: The Old Republic unable to patch on Debian but works on Mint Product: Wine Version: 5.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: toad(a)amphibian.dyndns.org Distribution: --- Created attachment 67644 --> https://bugs.winehq.org/attachment.cgi?id=67644 Wine log of running the launcher The SWTOR launcher is unable to patch itself, or to patch the game, and hence refuses to start the game even if it is actually up to date. However, it works on Linux Mint 19.3 (with the Xenial packages; the recommended bionic packages do not install). Debug output from Wine is not obviously helpful. Logs from SWTOR show an UnzipFailed error which is suspicious. Wine logs show nothing obviously helpful. I am using all the usual precautions for SWTOR: - Run the original installer in wine-devel. The installer does not work with staging. However, the patcher has the same issues on both. - On an affected system, the launcher hangs trying to patch itself, with errors in the SWTOR log. This can be fixed using the launcher repair utility. On Mint, it shows a bunch of assertion error dialogs, and works. - Login and accept the EULA, at this point it will complain about BitRaider. Exit and modify launcher.settings as usual to turn off BitRaider. - At this point, on Mint, Wine 5.11 is downloading the game successfully. On any version of Debian, it shows the error "Unable to retrieve patch data. Please check network connection. (206)". The TOR log shows the unzip error. I think the unzip error and the problems with the patcher patching itself are probably the same bug. This stopped working around the time of Wine 5.10, I think because of an update to the launcher. It does not work on Debian 9, 10 or 11 on staging 5.11. On Debian 11, it does not work on staging 5.11 or devel 5.12. -- 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 54

[Bug 57412] New: Steam launcher is black
by WineHQ Bugzilla 31 May '25

31 May '25

https://bugs.winehq.org/show_bug.cgi?id=57412 Bug ID: 57412 Summary: Steam launcher is black Product: Wine Version: 9.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: timon2201(a)gmail.com Distribution: --- Created attachment 77398 --> https://bugs.winehq.org/attachment.cgi?id=77398 steam launcher black, wayland log When starting the steam windows version with wine 9.21, with the waylanddriver, the launcher or better said steam is black and takes up the whole screen. I cant change the size of the window. Its always fullscreen and just black. When i launch it with x11 then steam look normal except that the store page is black. It gets visible for a fraction of a second whenever i move over a hyperlink or button and so on. here is the log of the x11 test: https://file.io/WoQksUpWYv7e -- 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 50375] New: Celemony Melodyne 3 demo: application starts, but suddenly stops responding to user actions, without any errors
by WineHQ Bugzilla 31 May '25

31 May '25

https://bugs.winehq.org/show_bug.cgi?id=50375 Bug ID: 50375 Summary: Celemony Melodyne 3 demo: application starts, but suddenly stops responding to user actions, without any errors Product: Wine Version: 6.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: suenish.salkimbaev(a)gmail.com Distribution: --- The application starts at the beginning without any errors, but does not respond to any user actions. -- 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 11

[Bug 41112] New: Wine does not open .log files automatically
by wine-bugs＠winehq.org 31 May '25

31 May '25

https://bugs.winehq.org/show_bug.cgi?id=41112 Bug ID: 41112 Summary: Wine does not open .log files automatically Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 00cpxxx(a)gmail.com Distribution: Debian When running CPU-Z sometimes it will fail to load its driver and then will ask if you want to see the log file. This will always fail with a second message box saying the file was not found. By running +process we can see this: trace:process:create_process_impl app (null) cmdline L"\"C:\\users\\wine\\Temp\\\\cpuz_driver_8.log\"" Then I opened the .exe and changed .log for .txt and voilà, the file was opened in notepad. trace:process:create_process_impl app (null) cmdline L"\"C:\\users\\wine\\Temp\\\\cpuz_driver_8.txt\"" ... trace:process:create_process_impl starting L"C:\\windows\\system32\\notepad.exe" as Win32 binary (0x10000000-0x1002f000, arch 014c, fakedll) Is it possible to make .log files also open in notepad? -- 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

[Bug 49704] New: Voicemod: setup closes after stating that an uninstaller is already running even though it's not
by WineHQ Bugzilla 31 May '25

31 May '25

https://bugs.winehq.org/show_bug.cgi?id=49704 Bug ID: 49704 Summary: Voicemod: setup closes after stating that an uninstaller is already running even though it's not Product: Wine Version: 5.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sssandum(a)gmail.com Distribution: --- Created attachment 67950 --> https://bugs.winehq.org/attachment.cgi?id=67950 Log from launching Voicemod setup Doesn't crash, setup closes after saying "An uninstaller is running. Setup will now close" even though Voicemod has never been installed on my computer. -- 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 39871] New: Evernote: Fatal error dialog is unable to open the log file
by wine-bugs＠winehq.org 31 May '25

31 May '25

https://bugs.winehq.org/show_bug.cgi?id=39871 Bug ID: 39871 Summary: Evernote: Fatal error dialog is unable to open the log file Product: Wine Version: 1.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: robert.munteanu(a)gmail.com Distribution: --- Created attachment 53235 --> https://bugs.winehq.org/attachment.cgi?id=53235 Fatal error dialog with the 'Open Log' button After a crash Evernote presents a dialog which can be used to send feedback to the dev team and also open the error log. When trying to open the error log I get a dialog which says that There is no Windows program configured to open this type of file The terminal output after pressing the button is only fixme:exec:SHELL_execute flags ignored: 0x00004100 -- 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 55639] New: OSS driver sends output to wrong device
by WineHQ Bugzilla 31 May '25

31 May '25

https://bugs.winehq.org/show_bug.cgi?id=55639 Bug ID: 55639 Summary: OSS driver sends output to wrong device Product: Wine Version: 8.16 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineoss.drv Assignee: wine-bugs(a)winehq.org Reporter: sean-freebsd(a)farley.org Created attachment 75175 --> https://bugs.winehq.org/attachment.cgi?id=75175 trace:oss of test sound using default device in winecfg Sometime after Wine 8.11, the OSS driver sends to the device node one higher than selected. Whether the "System Default" or the specific node device is picked in winecfg, the "Test Sound" goes to one higher than chosen. In my case, the speakers are on /dev/dsp4. In the log, that device is considered the default devnode. However, the devnode chosen for output is /dev/dsp5. If I chose /dev/dsp3 specifically, then the audio will be output via the speakers. It definitely looks like an off-by-one bug. Workaround: select lower device by number -- 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 57942] New: WINE Staging 10.2 Ubuntu Noble not start
by WineHQ Bugzilla 31 May '25

31 May '25

https://bugs.winehq.org/show_bug.cgi?id=57942 Bug ID: 57942 Summary: WINE Staging 10.2 Ubuntu Noble not start Product: Wine-staging Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: augusto7744(a)aol.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hello. Thanks for reading that topic. OS Lubuntu ( Ubuntu using LXQT ) Noble 24.04. All WINE dependencies correctly installed. Run WINE 10.0-RC5 correctly. Is possible install WINE-Staging 10.2 , but not start the process creation of WINE files in path /home/username/.wine When installing show the messages below Preparing to unpack winehq-staging_10.2~noble-1_amd64.deb ... Unpacking winehq-staging (10.2~noble-1) over (10.2~noble-1) ... Preparing to unpack wine-staging_10.2~noble-1_amd64.deb ... Unpacking wine-staging (10.2~noble-1) over (10.2~noble-1) ... Preparing to unpack wine-staging-amd64_10.2~noble-1_amd64.deb ... Unpacking wine-staging-amd64 (10.2~noble-1) over (10.2~noble-1) ... Preparing to unpack wine-staging-i386_10.2~noble-1_i386.deb ... Unpacking wine-staging-i386:i386 (10.2~noble-1) over (10.2~noble-1) ... Setting up wine-staging-amd64 (10.2~noble-1) ... /opt/wine-staging/bin/wine64-preloader (No such file or directory) Setting up wine-staging-i386:i386 (10.2~noble-1) ... /opt/wine-staging/bin/wine-preloader (No such file or directory) Setting up wine-staging (10.2~noble-1) ... Setting up winehq-staging (10.2~noble-1) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ... Processing triggers for desktop-file-utils (0.27-2build1) ... Processing triggers for man-db (2.12.0-4build2) ... When trying create the wine environment in /home/username/.wine show the messages below wine: failed to load /opt/wine-staging/lib/wine/i386-windows/ntdll.dll error 4000000e 0024:err:environ:run_wineboot failed to start wineboot 1 0024:fixme:winediag:loader_init wine-staging 10.2 is a testing version containing experimental patches. 0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. wine: failed to load /opt/wine-staging/lib/wine/i386-windows/ntdll.dll error 4000000e wine: failed to load /opt/wine-staging/lib/wine/i386-windows/ntdll.dll error 4000000e 0024:err:win:get_desktop_window failed to start explorer 1 wine: failed to load /opt/wine-staging/lib/wine/i386-windows/ntdll.dll error 4000000e 0024:err:start:fatal_error FormatMessage failed and other message too wine: failed to open L"C:\\windows\\system32\\wineboot.exe": c0000135 0024:err:environ:run_wineboot failed to start wineboot c0000135 wine: could not load kernel32.dll, status c0000135 I not see details about fixes about that bug in WINE 10.3 changelog. Only reporting that bug. Have an nice day. -- 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