wine-bugs April 2025

wine-bugs@winehq.org

1 participants
1033 discussions

[Bug 58101] New: Experimental wow64 mode issue Wine Arm64
by WineHQ Bugzilla 31 May '25

31 May '25

http://bugs.winehq.org/show_bug.cgi?id=58101 Bug ID: 58101 Summary: Experimental wow64 mode issue Wine Arm64 Product: Wine Version: 10.5 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cdfrosty(a)gmail.com Distribution: --- Created attachment 78360 --> http://bugs.winehq.org/attachment.cgi?id=78360 Experimental wow64 mode issue Wine Arm64 failing to load ntdll.dll Now thanks to the hard work done on this issue report: https://bugs.winehq.org/show_bug.cgi?id=52715 I can now compile for Arm64 I just want to report that binaries that use the experimental wow64 mode will fail and fail to load L"\\??\\C:\\windows\\syswow64\\ntdll.dll" -- 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 58170] New: apt archive broken
by WineHQ Bugzilla 31 May '25

31 May '25

http://bugs.winehq.org/show_bug.cgi?id=58170 Bug ID: 58170 Summary: apt archive broken Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: sebunger44(a)gmail.com Distribution: --- Hi, I am mirroring the WineHQ package archive for our CI system using reprepro. A few days (? not entirely sure when) ago, this process started failing with the following error message: aptmethod error receiving 'https://s3.amazonaws.comhttps//s3.amazonaws.comhttps://s3.amazonaws.comhttp…': 'Could not resolve 's3.amazonaws.comhttps' [IP: 151.101.166.217 80]' Nowhere in my setup of reprepro is s3.amazonaws.com mentioned and nothing in that setup has changed anyway since it last worked. So I suspect some form of redirect or something is broken. Rosanne DiMesio mentioned that the archive has recently moved to AWS, so I suspect that breakage is somewhere at your end. Cheers, Seb -- 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 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 58165] New: winedbg/cmd: Cannot enter BackSpace on jp106 keyboard
by WineHQ Bugzilla 31 May '25

31 May '25

http://bugs.winehq.org/show_bug.cgi?id=58165 Bug ID: 58165 Summary: winedbg/cmd: Cannot enter BackSpace on jp106 keyboard Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: axis6404(a)proton.me Distribution: --- Cannot enter BackSpace on jp106 keyboard. Entering BackSpace will enter ^H. -- 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 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 58160] New: Wine cannot download mono
by WineHQ Bugzilla 31 May '25

31 May '25

http://bugs.winehq.org/show_bug.cgi?id=58160 Bug ID: 58160 Summary: Wine cannot download mono 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: scallegari(a)arces.unibo.it Distribution: --- Recently, wine seems uncapable of downloading mono. The progress bar does not move from 0 an everything hangs. Might be an issue with wine itself or with the servers from which mono is meant to be developed. In either case, lack of a proper timeout and diagnostics in wine seems problematic. To repro: `wine 'C:\windows\system32\control.exe' appwiz.cpl install_mono` -- 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 14

[Bug 58178] New: err:ole:StdMarshalImpl_MarshalInterface
by WineHQ Bugzilla 31 May '25

31 May '25

http://bugs.winehq.org/show_bug.cgi?id=58178 Bug ID: 58178 Summary: err:ole:StdMarshalImpl_MarshalInterface Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: rkoptev70(a)gmail.com Distribution: --- Created attachment 78473 --> http://bugs.winehq.org/attachment.cgi?id=78473 winecfg Laptop: Lenovo G15 V4 IRU OS: Ubuntu 24.04 LTS and 22.04 LTS Wine versions tested: 9.0~repack-4build3, 10.0.0.0~noble-1, 10.6~noble-1 When running winecfg on a clean OS install - ole/rpcss errors occur in the terminal. These errors prevent wine-mono to be installed and it ultimately makes it not possible to run the windows app I want to run. I spent some long hours troubleshooting, trying to determine the root cause of the issue and resolve it(even wiped an entire OS to switch to the latest LTS). There are some posts on the forums with similar wine logs, however they were either ignored as non braking errors or solved in other or untold ways. What ultimately helped is to enable Secure Boot in BIOS settings (???). Now it works just fine. No idea why. Maybe my findings will provide you with a valuable troubleshooting info, or become one of the solutions for a problem which does not seem to have a common source or fix. -- 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

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 April 2025