October 2024 - Wine-bugs - list.winehq.org

[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 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 25872] New: dxdiag doesn't support /t option, needed by Guild Wars 'test system' button
by wine-bugs＠winehq.org 31 May '25

31 May '25

http://bugs.winehq.org/show_bug.cgi?id=25872 Summary: dxdiag doesn't support /t option, needed by Guild Wars 'test system' button Product: Wine Version: 1.3.12 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com This is the next problem after bug 25871. Guild wars installs nicely, but if you press 'test system', you see ... fixme:dxdiag:ProcessCommandLine /t unimplemented -- 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 16

[Bug 48264] New: WineHQ Debian repos are missing Wine 4.21
by WineHQ Bugzilla 30 May '25

30 May '25

https://bugs.winehq.org/show_bug.cgi?id=48264 Bug ID: 48264 Summary: WineHQ Debian repos are missing Wine 4.21 Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com CC: dimesio(a)earthlink.net, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- WineHQ Debian repo (testing for example) is still at 4.20, even though 4.21 came out at the end of last month already: https://dl.winehq.org/wine-builds/debian/dists/testing/main/binary-amd64/ -- 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 52

[Bug 54648] New: Call of Juarez needs "isnan" handling
by WineHQ Bugzilla 30 May '25

30 May '25

https://bugs.winehq.org/show_bug.cgi?id=54648 Bug ID: 54648 Summary: Call of Juarez needs "isnan" handling Product: vkd3d Version: 1.6 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 0718:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0718:err:d3dcompiler:D3DCompile2 Shader log: 0718:err:d3dcompiler:D3DCompile2 <anonymous>:18:6: E5005: Function "isnan" is not defined. 1.6-195-g2880be64 -- 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 5

[Bug 54660] New: Call of Juarez shows 'Assertion failed: deref->offset_regset == HLSL_REGSET_NUMERIC'
by WineHQ Bugzilla 30 May '25

30 May '25

https://bugs.winehq.org/show_bug.cgi?id=54660 Bug ID: 54660 Summary: Call of Juarez shows 'Assertion failed: deref->offset_regset == HLSL_REGSET_NUMERIC' Product: vkd3d Version: 1.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Assertion failed: deref->offset_regset == HLSL_REGSET_NUMERIC, file ../vkd3d/libs/vkd3d-shader/hlsl_codegen.c, line 3143 1.6-199-gda243570 -- 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