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

[Bug 57428] New: Can't launch apps
by WineHQ Bugzilla Nov. 22, 2024

Nov. 22, 2024

https://bugs.winehq.org/show_bug.cgi?id=57428 Bug ID: 57428 Summary: Can't launch apps Product: Wine Version: 9.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nathan.vidal2197(a)gmail.com Distribution: --- Created attachment 77423 --> https://bugs.winehq.org/attachment.cgi?id=77423 error message After updating my system (fedora 41 workstation) by running `sudo dnf update` I couldmn't run my exe files anymore. Before the update I could. It is not a problem with the file as I tried many different ones. Wine version: wine-9.15 (Staging) -- 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 57440] New: date format bug in wine env creation
by WineHQ Bugzilla Nov. 21, 2024

Nov. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=57440 Bug ID: 57440 Summary: date format bug in wine env creation Product: Wine Version: 9.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)evolution-hosting.eu Distribution: --- Name : wine-core Version : 9.15 Release : 1.fc40 Architecture: x86_64 Install Date: Do 14 Nov 2024 13:19:06 CET When a wine env is created, the REG value of: HKEY_CURRENT_USER -> Control Panel -> International -> sShortDate is set to "d.M.yyyy", which is wrong and confuses some apps. It needs to be "dd.MM.yyyy" for Germany ( CC=DE ). Please inform me, if this a true Wine issue, or if i.e. LUTRIS gives the wrong date format to the creationprocess. The ENV, with that issue, has been created by Lutris, which is way easier than doing it manually ;) -- 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 55859] New: LabView 2023.3.1 fails to install
by WineHQ Bugzilla Nov. 21, 2024

Nov. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=55859 Bug ID: 55859 Summary: LabView 2023.3.1 fails to install Product: Wine Version: 8.19 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75381 --> https://bugs.winehq.org/attachment.cgi?id=75381 Terminal output Steps to reproduce: 1. Extract ni-labview-2023-community-x86_23.3.1_offline.iso to a directory called ni-labview-2023-community-x86_23.3.1_offline 2. Run `chmod +r -R ni-labview-2023-community-x86_23.3.1_offline` 3. Run `winetricks dotnet48` 4. Run `winecfg` and change the Windows version back to 10 5. Run `winetricks d3dcompiler_47` 6. Run `wine Install.exe` $ sha256sum ni-labview-2023-community-x86_23.3.1_offline.iso 654dec2f01a3ae2e13ac69dd22bb717fac25e625da1099f974676ea79516e7c5 -- 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 37

[Bug 57426] New: Battlefield 2 won't launch.
by WineHQ Bugzilla Nov. 21, 2024

Nov. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=57426 Bug ID: 57426 Summary: Battlefield 2 won't launch. Product: Wine Version: 9.21 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: critical Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: tanvir.maht(a)outlook.com Created attachment 77419 --> https://bugs.winehq.org/attachment.cgi?id=77419 Terminal output Battlefield 2 opens to show a black screen and crashes later on. -- 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

[Bug 57432] New: dxdiag will return "Windows XP" unconditionally from systeminfo.szOSExLongEnglish
by WineHQ Bugzilla Nov. 21, 2024

Nov. 21, 2024

https://bugs.winehq.org/show_bug.cgi?id=57432 Bug ID: 57432 Summary: dxdiag will return "Windows XP" unconditionally from systeminfo.szOSExLongEnglish Product: Wine Version: 9.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: braiamp(a)gmail.com Distribution: --- Created attachment 77424 --> https://bugs.winehq.org/attachment.cgi?id=77424 dxdiag.log with windows xp set Running dxdiag /t dxdiag.log on a new prefix, will show that "Operating System: Windows XP Professional", despite the prefix being created by default with Windows 10 configuration on recent versions of wine. Whatever it is, is caused by dxdiag_info->system_info.szOSExLongEnglish being specified as Windows XP. I couldn't trace where it was set, after I reached https://gitlab.winehq.org/wine/wine/-/blob/master/programs/dxdiag/informati… and was lost in the source. Attached the "dxdiag /t dxdiag.log" resulting file. -- 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 57436] New: ntlm_auth was not found after Debian update?
by WineHQ Bugzilla Nov. 20, 2024

Nov. 20, 2024

https://bugs.winehq.org/show_bug.cgi?id=57436 Bug ID: 57436 Summary: ntlm_auth was not found after Debian update? Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)infobahn.33m.co Distribution: --- So I am new to submitting bugs but will try to give relevant info. Wine --version = wine-8.0 (Debian 8.0~repack-4) I recently did a mundane: sudo apt-get update && sudo apt-get upgrade and later tried running a win program (foobar2000) and got: err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. So I checked the version: user(a)media:~/.wine/drive_c/Program Files$ ntlm_auth --version Version 4.17.12-Debian and the path: user(a)media:~/.wine/drive_c/Program Files$ echo $PATH /home/user/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games user(a)media:~/.wine/drive_c/Program Files/foobar2000$ which ntlm_auth /usr/bin/ntlm_auth Ultimately this results in foobar2k crashing, but seemingly only fb2k. I have tried running mp3tag, Awesome Duplicate Finder, notepad.exe, and iexplorer.exe and none of them crashed (IE would not load pages but I can't be sure that is a related issue). I will be happy to post more information, please let me know what is needed. -- 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 54482] New: RtlCaptureStackBackTrace cause segv
by WineHQ Bugzilla Nov. 20, 2024

Nov. 20, 2024

https://bugs.winehq.org/show_bug.cgi?id=54482 Bug ID: 54482 Summary: RtlCaptureStackBackTrace cause segv Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: ake.rehnman(a)gmail.com Distribution: --- Created attachment 74033 --> https://bugs.winehq.org/attachment.cgi?id=74033 patch attempt RtlCaptureStackBackTrace crash on segmentation fault because the unwinding keeps going beyond the stack end. It seems on x86-64 the stack actually starts at least 32 bytes below StackBase so the compariston with context.rsp to StackBase will never hit but we get a context.rpc value of 0 which obviously SEGV:s. I made a patch attempt and just check if rcp = 0 and end the unwinding. -- 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 42407] New: LdrUnloadDll may recursion unload same dll
by wine-bugs＠winehq.org Nov. 19, 2024

Nov. 19, 2024

https://bugs.winehq.org/show_bug.cgi?id=42407 Bug ID: 42407 Summary: LdrUnloadDll may recursion unload same dll Product: Wine Version: 1.9.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: xiewei(a)deepin.com Distribution: --- Created attachment 57219 --> https://bugs.winehq.org/attachment.cgi?id=57219 LdrUnloadDll log file It may cause QQ crash.LdrUnloadDll funcation recursion unload Flash.ocx,and dsound.dll ldr.LoadCount to 0,then dsound.dll be unload.But QQ process is still using dsound.dll. Type: EXCEPTION_ACCESS_VIOLATION Error: Read address 0x7985C309 Address: 7985C309 -- 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 8

[Bug 40972] New: RtlVerifyVersionInfo returns wrong results
by wine-bugs＠winehq.org Nov. 19, 2024

Nov. 19, 2024

https://bugs.winehq.org/show_bug.cgi?id=40972 Bug ID: 40972 Summary: RtlVerifyVersionInfo returns wrong results Product: Wine Version: 1.9.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: marcinwiaz(a)poczta.onet.pl Distribution: --- Created attachment 55126 --> https://bugs.winehq.org/attachment.cgi?id=55126 Tiny test program - EXE and source (Note: this a different problem than in Bug 36143) Steps to reproduce: 1) Download and unpack Reproduce.exe, which is attached to this bug report 2) Configure Wine to emulate Windows 2003 (which has version number 5.2) for Reproduce.exe 3) Launch Reproduce.exe - you will see in the console window: CurrentOS is: 5.2 RequestedOS is >= than: 5.19 CurrentOS is < than RequestedOS (which is WRONG!) 4) Run true Microsoft Windows 2003 Server 5) Launch Reproduce.exe - you will see in the console window: CurrentOS is: 5.2 RequestedOS is >= than: 5.19 CurrentOS is >= than RequestedOS Explanation: Minor version numbers should be treated similarly to digits after a decimal point - so when comparing software versions: version 5.1 is < than version 5.2 version 5.11 is < than version 5.2 (note that 11 is > than 2 !) version 5.19 is < than version 5.2 (note that 19 is > than 2 !) So when comparing for VER_MINORVERSION or VER_SERVICEPACKMINOR inside the "VerifyVersionInfo" API, Microsoft uses a lexical comparison - which works as: lstrcmp(tostring(dwMinorVersion1),tostring(dwMinorVersion2)) or lstrcmp(tostring(wServicePackMinor1),tostring(wServicePackMinor2)) Please note, that it's still different than comparing real numbers, because: 5.20 = 5.2 but lstrcmp("5.20","5.2") != 0 So lstrcmp-like function must be used for VER_MINORVERSION and VER_SERVICEPACKMINOR checking inside the "RtlVerifyVersionInfo" function (which is called by the "VerifyVersionInfo" API in Wine) to be compatible with Microsoft Windows. Possible fix: in "version.c" file, add a new "version_compare_values_lexical" function. It should be based on the original "version_compare_values" function, but should use "lstrcmp" calls instead of integer comparisons. This "version_compare_values_lexical" function should be called instead of "version_compare_values" when checking for VER_MINORVERSION and VER_SERVICEPACKMINOR inside the "RtlVerifyVersionInfo" function. -- 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 49828] New: MSVC 2019 executables with ASAN enabled fail to start
by WineHQ Bugzilla Nov. 19, 2024

Nov. 19, 2024

https://bugs.winehq.org/show_bug.cgi?id=49828 Bug ID: 49828 Summary: MSVC 2019 executables with ASAN enabled fail to start Product: Wine Version: 5.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nyanpasu64(a)tuta.io Distribution: --- Recent versions of MSVC allow building Windows .exes with ASAN (it may have already been possible using Clang.): https://devblogs.microsoft.com/cppblog/addresssanitizer-asan-for-windows-wi… I took an old Win32/MFC application and built it using MSVC ASAN on Windows 10, to try to discover memory bugs on Windows and Wine. - Program download at https://cdn.discordapp.com/attachments/653168829891084298/75454092297227479… . - Source at https://github.com/nyanpasu64/Dn-FamiTracker/tree/b3ba802f (permalink at https://cdn.discordapp.com/attachments/653168829891084298/75454082852061186… ). - To build, copy cmake_user_begin.cmake.example to cmake_user_begin.cmake, then run CMake in MSVC 32-bit Release mode. It may be possible using Visual Studio's .json file or msbuild, but I haven't tried yet. On Windows, the program starts without problems. On wine-5.17, when I try to run this program, it crashes during the loading process. nyanpasu64(a)dell-arch ~/apps> wine Dn_FamiTracker_ASAN.exe 0024:fixme:ntdll:EtwEventRegister ({6c6c766d-3846-4e6a-a4fb-5b530bd0f3fa}, 00401030, 00884590, 008845A8) stub. 0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0084A41C, 34) stub ==32==AddressSanitizer CHECK failed: D:\agent\_work\3\s\src\vctools\crt\asan\llvm\compiler-rt\lib\asan\asan_rtl.cc:401 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) <empty stack> `winedbg Dn_FamiTracker_ASAN.exe` doesn't work, it gets stuck on `0x00000000005c9701 EntryPoint+0xffffffffffffffff in dn_famitracker_asan: ret`. If I instead `winedbg --gdb Dn_FamiTracker_ASAN.exe`, I get a pile of identical SIGTRAP with different backtraces. These are non-fatal and can be continued. I think these correspond to asan errors that would normally terminate the program, but unfortunately it doesn't print log messages when running in winedbg. I don't know how to fix that. 0x005c9701 in _sanitizer_print_stack_trace () from /home/nyanpasu64/.wine/dosdevices/z:/home/nyanpasu64/apps/Dn_FamiTracker_ASAN.exe The last SIGTRAP is different: 0x7bc52379 in DbgBreakPoint(a)0 () from /home/nyanpasu64/.wine/dosdevices/c:/windows/syswow64/ntdll.dll Afterwards the program starts. (It used to crash, but works with lib32-libpulse and lib32-mpg123 installed, unsure if that's why.) -- 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 15

[Bug 43262] New: Drag&Drop not working between wine explorer and other applications
by wine-bugs＠winehq.org Nov. 19, 2024

Nov. 19, 2024

https://bugs.winehq.org/show_bug.cgi?id=43262 Bug ID: 43262 Summary: Drag&Drop not working between wine explorer and other applications Product: Wine Version: 2.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mintos(a)discard.email Distribution: --- https://pastebin.com/39uSnrR7 console output -- 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 52215] New: MSTSC (Remote Desktop) 7.0 cannot find its MUI files when Windows version is set to 7
by WineHQ Bugzilla Nov. 18, 2024

Nov. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=52215 Bug ID: 52215 Summary: MSTSC (Remote Desktop) 7.0 cannot find its MUI files when Windows version is set to 7 Product: Wine Version: 7.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 71279 --> https://bugs.winehq.org/attachment.cgi?id=71279 Error. File not found. C:\windows\system32\<LANG_NAME>\mstsc.exe.MUI A workaround is to set the Windows version to XP but I don't like it because Wine as far as I know doesn't allow to set a per application Windows version and my default Windows version is set to 7. strace shows that Wine doesn't even attempt to find MUI files as if some resolution inside it breaks completely when Windows != XP. -- 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 57007] New: Sequence Editor from Legendary Explorer of ME3Tweaks Mod Manager triggers GDI assert
by WineHQ Bugzilla Nov. 18, 2024

Nov. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=57007 Bug ID: 57007 Summary: Sequence Editor from Legendary Explorer of ME3Tweaks Mod Manager triggers GDI assert Product: Wine Version: 9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: raulvior.bcn(a)gmail.com Distribution: --- Created attachment 76845 --> https://bugs.winehq.org/attachment.cgi?id=76845 Log generated with WINEDEBUG=warn Sequence Editor 6.4.18 from Legendary Explorer of ME3Tweaks Mod Manager 9.0 (Tools->Legendary Explorer) triggers assert from Wine code base "err:msvcrt:_wassert (L"graphics->hdc_refs == 0",L"dlls/gdiplus/graphics.c",2621)". Executing with WINEDEBUG=warn+heap shows the following warning "warn: Using GDI for swapchain presentation. This will impact performance." which belongs to https://github.com/doitsujin/dxvk/blob/master/src/d3d9/d3d9_swapchain.cpp#L… The assert is triggered when trying to add a BioSeqVar_StoryManagerX variable where X is one of {Bool,Float,Int,StateId}. I have not tried all other object types. But from the Variables tab it only crashes when double clicking in any of those four. The PCC file opened with the Sequence Editor can be downloaded here: https://drive.proton.me/urls/GSMNK9XPF8#MHMpgEs2uYHe You have to configure Wine to emulate a virtual desktop. Otherwise tooltips and menus appear as black rectangles. ### Software information Legendary Explorer 6.4.18 from ME3Tweaks Mod Manager 9.0. ### System information - GPU: AMD Radeon VII (RADV VEGA20) - Driver: radv 24.1.3 - Wine version: wine-9.13 ### Apitrace file(s) https://drive.proton.me/urls/DGQS3343J4#0BDgJCGU0pfz -- 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 6

[Bug 57420] New: Incorrect (broken) Japanese Font Substitution for Tahoma via FontLink
by WineHQ Bugzilla Nov. 18, 2024

Nov. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=57420 Bug ID: 57420 Summary: Incorrect (broken) Japanese Font Substitution for Tahoma via FontLink Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: rikul(a)inbox.ru Distribution: --- Created attachment 77410 --> https://bugs.winehq.org/attachment.cgi?id=77410 Left->FontLink,Right->FontSubstitutes When configuring the Tahoma font to use a Japanese fallback font via FontLink, issues arise with proper font substitution in Notepad++ and other applications. Here’s a summary of the issue: 1. A FontLink -> SystemLink registry key is added for Tahoma, which includes VL-Gothic-Regular.ttf,VL Gothic among other fonts. 2. The system locale is set to ja_JP.UTF-8. 3. Notepad++ (and other applications) is launched. Expected Behavior: The Japanese font should display correctly throughout the application interface. Actual Behavior: - In some parts in Notepad++ where using Tahoma font (e.g., menus), the Japanese font does not display correctly, though in other areas, like the settings window, it does. - We have verified this behavior in other applications, and the same issue is consistently observed. - Without linking to VL Gothic, the Japanese text in menus becomes completely unreadable. VL Gothic is used here as an example for a readable fallback font. Workaround: Adding a FontSubstitutes registry entry that maps Tahoma to VL Gothic Regular resolves the issue, and the correct font appears throughout the interface. Problem with the Workaround: This approach is not ideal because changing the system locale does not automatically update the FontSubstitutes entry. As a result, VL Gothic Regular remains set for Tahoma, which is undesirable in an English locale, for example. Additional Information: - Attached are screenshots showing correct and incorrect font rendering. - Tested on Wine 9.0 as well as the main branch, with consistent behavior in both versions. -- 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 57429] New: Wine fails to open a terminal window if a terminal application is invoked from the file manager
by WineHQ Bugzilla Nov. 18, 2024

Nov. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=57429 Bug ID: 57429 Summary: Wine fails to open a terminal window if a terminal application is invoked from the file manager Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tobi17spam(a)gmx.de Distribution: --- This is on Linux Mint. If Wine is invoked from the file manager (using an open action), on a windows terminal exe, it doesn't open a terminal on its own (like Windows would in such a situation). When run from an existing terminal, the executable is run as it should. -- 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 48641] New: skse64 is broken with the ntdll-ForceBottomUpAlloc patchset
by WineHQ Bugzilla Nov. 18, 2024

Nov. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=48641 Bug ID: 48641 Summary: skse64 is broken with the ntdll-ForceBottomUpAlloc patchset Product: Wine-staging Version: 5.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)mail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- While SKSE64 now works properly under wine, it hangs (then fails to launch) when the ntdll-ForceBottomUpAlloc patchset is enabled. Building wine-staging without that specific patchset works fine. This is similar to how it was in earlier wine versions, before a better version of the F4SE patches (https://github.com/hdmap/wine-hackery/tree/master/f4se) were mainlined. -- 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 57099] New: Frosty Mod Manager opens up but apply nor launch the game.
by WineHQ Bugzilla Nov. 17, 2024

Nov. 17, 2024

https://bugs.winehq.org/show_bug.cgi?id=57099 Bug ID: 57099 Summary: Frosty Mod Manager opens up but apply nor launch the game. Product: Wine Version: 9.13 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tanvir.maht(a)outlook.com Frosty Mod Manager can be opened but you can’t apply mods and then launch the game. -- 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 54114] New: Cyberworld Browser: "Could not resolve 'intro_default.url'"
by WineHQ Bugzilla Nov. 17, 2024

Nov. 17, 2024

https://bugs.winehq.org/show_bug.cgi?id=54114 Bug ID: 54114 Summary: Cyberworld Browser: "Could not resolve 'intro_default.url'" Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: doomtay(a)gmail.com Distribution: --- Created attachment 73649 --> https://bugs.winehq.org/attachment.cgi?id=73649 Example files https://web.archive.org/web/20020808051830id_/http://www.cyberworldcorp.com… Cyberworld Browser Installer When opening up "intro.borg" in the sample zip, I expect both the large web panel and side panel to change. Instead, I get a black screen and the message "Could not resolve 'intro_default.url'" at the bottom -- 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

[Bug 30615] New: Audition CS6 (5.0) - strange UI graphics
by wine-bugs＠winehq.org Nov. 17, 2024

Nov. 17, 2024

http://bugs.winehq.org/show_bug.cgi?id=30615 Bug #: 30615 Summary: Audition CS6 (5.0) - strange UI graphics Product: Wine Version: 1.5.3 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jan(a)lugfl.de Classification: Unclassified Created attachment 40072 --> http://bugs.winehq.org/attachment.cgi?id=40072 Audition CS6 Mixer screenshot The UI looks very strange. Results with native and buildin gdiplus looks identical. see attached screenshot. A log of the console output is attached too. -- 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 26

[Bug 54511] New: Cygwin installer hangs during postprocessing step
by WineHQ Bugzilla Nov. 15, 2024

Nov. 15, 2024

https://bugs.winehq.org/show_bug.cgi?id=54511 Bug ID: 54511 Summary: Cygwin installer hangs during postprocessing step Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Install seems to go fine, but in the end it hangs when running C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_000_autorebase.dash" Both wineserver and dash.exe use about half a cpu core each, but nothing seems to happen. Comparing it to windows, that step should be fast. Cygwin used to install fine, but even when downgrading wine I can't seem to get it to work, it all shows the same issue. So it's probably not a Wine regression. -- 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

[Bug 52159] New: 64-bit cygwin gdb.exe and python3.8.exe fail to run
by WineHQ Bugzilla Nov. 15, 2024

Nov. 15, 2024

https://bugs.winehq.org/show_bug.cgi?id=52159 Bug ID: 52159 Summary: 64-bit cygwin gdb.exe and python3.8.exe fail to run Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 71205 --> https://bugs.winehq.org/attachment.cgi?id=71205 details.txt This issue can be seen if the workarounds for bug #47808 got applied first. Both gdb.exe and python3.8.exe fail in the python initialisation. As far as I see it python allocates 8 bytes for a sem_t structure. This uninitialized struct is given to sem_init which checks if this is a previously initialized semaphore by checking with verifyable_object_isvalid. This check happens inside a __try/__endtry [2] [3]. That way we end up in RtlUnwindEx, which inspects NtCurrentTeb()->Tib.ExceptionList. Unfortunately this list finally contains a pointer to the initial stack, which cygwin deallocated before [1]. See details.txt. -- 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

[Bug 57354] New: HeidiSQL 7.0 shows black window
by WineHQ Bugzilla Nov. 15, 2024

Nov. 15, 2024

https://bugs.winehq.org/show_bug.cgi?id=57354 Bug ID: 57354 Summary: HeidiSQL 7.0 shows black window Product: Wine Version: 9.20 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 77325 --> https://bugs.winehq.org/attachment.cgi?id=77325 Screenshot Bisected to commit ae3384fe2f9e1e5283fa2b8881251b4716c8487d Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Aug 5 13:05:46 2024 +0200 win32u: Always use the dummy surface if a surface isn't needed. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=57033 To reproduce: - Work around bug 57033 (revert 5924ab4c5155d97f4b23a33e97258c1ec382ea02) - Download https://web.archive.org/web/20130612145220/http://heidisql.googlecode.com/f… - Extract and run the exe - Click the new button - you now get a black window that updates when you hover/click elements -- 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 52642] New: game with avi video as opening will freeze when started
by WineHQ Bugzilla Nov. 14, 2024

Nov. 14, 2024

https://bugs.winehq.org/show_bug.cgi?id=52642 Bug ID: 52642 Summary: game with avi video as opening will freeze when started Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw Distribution: --- Created attachment 71963 --> https://bugs.winehq.org/attachment.cgi?id=71963 wine console log seems something error with avi codec Affect game: VirtualLife2 -- 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 15

[Bug 57416] New: xEdit Bethesda Modding Tool Crashes under Wine-9.21
by WineHQ Bugzilla Nov. 13, 2024

Nov. 13, 2024

https://bugs.winehq.org/show_bug.cgi?id=57416 Bug ID: 57416 Summary: xEdit Bethesda Modding Tool Crashes under Wine-9.21 Product: Wine Version: 9.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nekoNexus(a)protonmail.ch Distribution: --- Created attachment 77401 --> https://bugs.winehq.org/attachment.cgi?id=77401 Wine-9.21 Output Log Problem: xEdit crashes under Wine 9.21 and prevents basic usage of the app for use with Bethesda games. Download location: https://github.com/TES5Edit/TES5Edit/releases/tag/xedit-4.1.5f ----- Reproduction Steps: 1) Install a Bethesda game (in my case, I installed Oblivion from GOG using Heroic and with the system-installed Wine version) 2) cd to where xEdit is downloaded (download it, of course) 3) Depending on the game, change all references to "xEdit" to the specific game being used by renaming the executables (in this case, it would be "TES4Edit" instead) 4) Run: WINEPREFIX="/path/to/prefix" WINEARCH="win64" winecfg (then click okay / closer the window after adding a wincfg entry for xEdit to run in WinXP mode) 5) Run the game launcher once using that prefix, open the game, then close it (assuming the launcher doesn't have "Play" greyed out; it was for me, so I closed the launcher then launched the game directly) 6) Run: WINEPREFIX="/path/to/prefix" WINEARCH="win64" wine start ./TES4Edit64.exe -D "Z:\path\to\game\folder\Data" ("Data" is an actual folder named that) 7) xEdit Crashes with a runtime error Note: If you specifically run the 64-bit executable it'll give a message about considering using the 32-bit mode for speed, and interacting with that message box works, but it will proceed to crash afterwards. Running the program without any arguments instead throws an error about there being a missing registry entry for the game, but the program doesn't crash if doing this. Normally, this would be to detect the game location, but xEdit was made for the Steam version in mind in this regard, which is why this separate error is thrown. Performing a similar process using Mod Organizer in conjunction makes no difference as the results are the same. -- 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 57399] New: [wine-mono] ReadTimeout of SerialPort not working properly
by WineHQ Bugzilla Nov. 12, 2024

Nov. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=57399 Bug ID: 57399 Summary: [wine-mono] ReadTimeout of SerialPort not working properly Product: Wine Version: 9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: serial Assignee: wine-bugs(a)winehq.org Reporter: osu_Vanilla(a)126.com Distribution: --- The following code set ReadTimeout to 500ms, and call the function Read. When COM33 receives nothing, it should throw TimeoutException after timeout. But wine stuck on the Read operation, until it received 4096 (or more) bytes. ``` using System.IO.Ports; namespace ConsoleApplication1 { internal class Program { public static void Main(string[] args) { var serialPort = new SerialPort("COM33", 9600, Parity.None, 8, StopBits.One); serialPort.ReadTimeout = 500; serialPort.WriteTimeout = 500; serialPort.Open(); var buff = new byte[4096]; serialPort.Read(buff, 0, 4096); } } } ``` -- 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