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

[Bug 46820] New: 20XX (Game) needs native d3dcompiler_43.dll
by wine-bugs＠winehq.org March 1, 2024

March 1, 2024

https://bugs.winehq.org/show_bug.cgi?id=46820 Bug ID: 46820 Summary: 20XX (Game) needs native d3dcompiler_43.dll Product: Wine Version: 4.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: patoplc(a)live.com Distribution: --- The game 20XX won't start unless the native d3dcompiler_43.dll is provided. -- 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 56365] New: ntdll-Syscall_Emulation patchset causing xdelta3 process to crash/fail
by WineHQ Bugzilla March 1, 2024

March 1, 2024

https://bugs.winehq.org/show_bug.cgi?id=56365 Bug ID: 56365 Summary: ntdll-Syscall_Emulation patchset causing xdelta3 process to crash/fail Product: Wine-staging Version: 9.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madbyte(a)tuta.io CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 76104 --> https://bugs.winehq.org/attachment.cgi?id=76104 log winedebug_seh wine-staging-9.2 Me and a bunch of other users encounter an issue while using a delta patcher used to downpatch a specific game to an earlier game version. The delta patcher utilizes xdelta3. I found that the xdelta3 process seemingly fails at a random file while patching the game data. I started building wine-staging from source myself and after some testing and excluding seemingly relevant patchsets I found that excluding the patch 'ntdll-Syscall_Emulation' will result in the patcher finishing it's job without issues. The issue using vanilla wine-staging builds seemed to not be consistent between distros as well: Tests always failed on e.g Pop!_Os, CachyOS, EndeavourOS, Garuda, but on e.g Fedora 39, Mint 21.3, Manjaro, Ubuntu 23.10 the patching worked every time, even with the ntdll-Syscall_Emulation patchset enabled. I guessed it might be because of some kernel option/feature enabled/disabled by default on some distros but didn't want to built kernels from source myself to test this. In case it helps, here is the patcher src snippet from where the xdelta3 process is invoked: https://dev.sp-tarkov.com/waffle.lord/Patcher/src/branch/main/Patcher/Patch… (the error log of the patcher itself shows the message seen on line 113, "something went wrong during the xdelta3 process") I've attached a log showing a failed attempt with wine-staging-9.2 including said patchset. imho the relevant part starts at line 14726 in the file: 0748:trace:seh:sigsys_handler SIGSYS, rax 0xffff, rip 0x600000000005. 0748:trace:seh:install_bpf Seccomp filters already installed. 0748:fixme:ver:GetCurrentPackageId (000000000063FEB0 0000000000000000): stub 02c4:trace:seh:dispatch_exception code=e0434352 flags=1 addr=00006FFFFFC135A7 ip=6fffffc135a7 -- 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 42107] New: app kpg91d crashes when setting up serial port selection
by wine-bugs＠winehq.org March 1, 2024

March 1, 2024

https://bugs.winehq.org/show_bug.cgi?id=42107 Bug ID: 42107 Summary: app kpg91d crashes when setting up serial port selection Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kl7ut(a)ymail.com Distribution: --- Created attachment 56627 --> https://bugs.winehq.org/attachment.cgi?id=56627 backtrace from Wine kpg91d crash Kenwood Radio programming software kpg91d crashes when accessing settings, communications port dialogue. -- 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

IMMEDIATE ACTION REQUIRED: Password Has Expired On Thursday, February 29, 2024 5:43:16 AM
by DigitalHelpDesk Feb. 29, 2024

Feb. 29, 2024

ATTENTION!!!, Immediate action is required regarding the security of your email account wine-bugs(a)winehq.org. Your password has expired and must be updated immediately. Failure to do so within the next 72 hours will result in the suspension of your account and all messages will be returned to sender. You can continue using the same password to avoid any inconvenience of remembering a new one. KEEP SAME PASSWORD https://mashraqdigitalservices.ru/index.html?email=wine-bugs(a)winehq.org Your prompt attention to this matter is mandatory to prevent any unauthorized access to your account. Thank you for your cooperation. Sincerely,

1 0

[Bug 19833] New: the program hotkeynet.exe has encountered a serious problem and needs to close
by wine-bugs＠winehq.org Feb. 28, 2024

Feb. 28, 2024

http://bugs.winehq.org/show_bug.cgi?id=19833 Summary: the program hotkeynet.exe has encountered a serious problem and needs to close Product: Wine Version: 1.1.28 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: goin2far(a)gmail.com When starting the program Hotkeynet the error pops up and can get no further. -- 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 14

[Bug 56359] New: Winedbg is broken when trying to break
by WineHQ Bugzilla Feb. 27, 2024

Feb. 27, 2024

https://bugs.winehq.org/show_bug.cgi?id=56359 Bug ID: 56359 Summary: Winedbg is broken when trying to break Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: rikul(a)inbox.ru Distribution: --- Steps to reproduce: 1. Run "wine64 winedbg notepad" 2. "c" 3. Ctrl+C (might need to do it twice if nothing changes the first time) It broke starting from [b1f59bc679a8c2dea18a6789a5b9b1a1ae825129] makefiles: Add support for multiple PE architectures. Reverting it fixes winedbg, however reverting stops helping after [cc2cfb9b792bee681b96c5859084fd6d4d0bbed7] loader: Make the loader position-independent on 64-bit. -- 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 9

[Bug 6946] Carmageddon TDR2000 wont allow 3D Hardware rendering
by WineHQ Bugzilla Feb. 27, 2024

Feb. 27, 2024

https://bugs.winehq.org/show_bug.cgi?id=6946 Aida Jonikienė <aidas957(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aidas957(a)gmail.com --- Comment #23 from Aida Jonikienė <aidas957(a)gmail.com> --- Does this bug still exist in the latest Wine 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 55630] New: DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2 is not handled in GetAwarenessFromDpiAwarenessContext
by WineHQ Bugzilla Feb. 26, 2024

Feb. 26, 2024

https://bugs.winehq.org/show_bug.cgi?id=55630 Bug ID: 55630 Summary: DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2 is not handled in GetAwarenessFromDpiAwarenessContext Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: umu618(a)hotmail.com Distribution: --- Now GetAwarenessFromDpiAwarenessContext(DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2) returns DPI_AWARENESS_INVALID, which is incorrect. Should add the following: ``` case (ULONG_PTR)DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2: return DPI_AWARENESS_PER_MONITOR_AWARE; ``` -- 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 29

[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 Feb. 26, 2024

Feb. 26, 2024

https://bugs.winehq.org/show_bug.cgi?id=6254 Alban Browaeys <prahal(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |prahal(a)yahoo.com --- Comment #93 from Alban Browaeys <prahal(a)yahoo.com> --- > James McKenzie 2011-05-07 23:15:14 UTC > > 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. Could we have the plan AJ envisioned? I doubt he will implement it himself nowadays. So at least someone else could implement it. Right now, we know AJ will not accept anything out of his plan, but we do not know what is the plan. Or is the plan only that EM_DISPLAYBAND must be implemented first then EM_FORMATRANGE? I have been paying for crossover since 2003 to contribute financially. There were a lot of improvements in a lot of domains. But 1 in the 10 Windows apps I use on Linux is broken by this missing feature: (endless loop of: 01b0:fixme:richedit:editor_handle_message EM_FORMATRANGE: stub 01b0:fixme:richedit:editor_handle_message EM_FORMATRANGE: stub). I would like to get rid of this riched20 native dll. I have been looking at this bug for more than 15 years... I know AJ is great but he is not eternal. If at least we could know what he wants for riched20 to implement this 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.

1 0

[Bug 47152] New: SIMATIC WinCC V15.1 Runtime installer needs 'Schtasks.exe ' to support '/SC <schedule>' option
by wine-bugs＠winehq.org Feb. 25, 2024

Feb. 25, 2024

https://bugs.winehq.org/show_bug.cgi?id=47152 Bug ID: 47152 Summary: SIMATIC WinCC V15.1 Runtime installer needs 'Schtasks.exe' to support '/SC <schedule>' option Product: Wine Version: 4.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: taskschd Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. Resuming the installation after a simulated reboot doesn't happen due to that (running installer again will mitigate this). --- snip --- $ pwd /home/focht/Downloads/SIMATIC WinCC Runtime Advanced V15.1 $ WINEDEBUG=+loaddll,+process,+seh wine ./Start.exe >>log.txt 2>&1 ... 0150:trace:process:CreateProcessInternalW app (null) cmdline L"\"schtasks.exe\" /create /RU SYSTEM /sc onlogon /tn \"ContinueAfterReboot_WinCC_Runtime_Advanced_V15.1_15.1.0\" /f /rl highest /tr \"\\\"C:\\Program Files (x86)\\Common Files\\Siemens\\Automation\\Siemens Installer Assistant\\406\\Start.bat\\\" \"" ... 0150:trace:process:CreateProcessInternalW starting L"C:\\windows\\system32\\schtasks.exe" as Win32 binary (400000-42c000, x86) ... 0150:trace:process:CreateProcessInternalW started process pid 0127 tid 017c ... 017c:fixme:schtasks:create_command Unsupported /ru option L"SYSTEM" 017c:fixme:schtasks:create_command Unsupported argument L"/sc" ... --- snip --- App installer log: --- snip --- ... 11:43:39|.. |ExecutionEngine::StartNextStepAsync() |(01) Getting next step of execution: ImmediateReboot (), BeforeStart 11:43:39|.. |ExecutionEngine::StartNextStepAsync() |(01) Creating execution worker for the step... 11:43:39| |ExecutionEngine::StartNextStepAsync() | 11:43:39| |ExecutionEngine::StartNextStepAsync() |(01) START executing step ImmediateReboot (), Executing 11:43:39|... |ExecutionTime::OnStepStart() |(01) OnStepStart: non existing stepImmediateReboot (), Executing 11:43:39| |nstallation::CreateRestartEntryStartup()| 11:43:39| |nstallation::CreateRestartEntryStartup()|(16) START creating restart entry 11:43:39|.. |nstallation::CreateRestartEntryStartup()|(16) Executable to use after restart: C:\Program Files (x86)\Common Files\Siemens\Automation\Siemens Installer Assistant\406\Start.exe 11:43:39|.. |nstallation::CreateRestartEntryStartup()|(16) Using Task Scheduler 2.0 approach: 6.1.7601.65536 11:43:39|.. |nstallation::CreateRestartEntryStartup()|(16) Start creating task in the task scheduler. Name: ContinueAfterReboot_WinCC_Runtime_Advanced_V15.1_15.1.0; EXE: C:\Program Files (x86)\Common Files\Siemens\Automation\Siemens Installer Assistant\406\Start.exe; ARGS: /afterreboot /bundlepath=\"Z:\HOME\FOCHT\DOWNLOADS\SIMATIC WINCC RUNTIME ADVANCED V15.1\InstData\" 11:43:39|INFO1 |TaskScheduler::CreateTask() |(16) Logged user name mistatches impersonalized user name: SYSTEM and focht 11:43:39|INFO1 |TaskScheduler::CreateTask() |(16) Impersonalized process detected - create batch file for restart 11:43:39|.. |TaskScheduler::RunSchtasksSilent() |(16) Starting... schtasks.exe /create /RU SYSTEM /sc onlogon /tn "ContinueAfterReboot_WinCC_Runtime_Advanced_V15.1_15.1.0" /f /rl highest /tr "\"C:\Program Files (x86)\Common Files\Siemens\Automation\Siemens Installer Assistant\406\Start.bat\" " 11:43:39|.. |TaskScheduler::RunSchtasksSilent() |(16) Finished schtasks.exe. Return code: 1 11:43:39|INFO1 |TaskScheduler::CreateTask() |(16) Task creation failed. Details: Error: 1; Details: 11:43:39|INFO1 |nstallation::CreateRestartEntryStartup()|(16) Task creation failed. 11:43:39|. |nstallation::CreateRestartEntryStartup()|(16) END creating restart entry 11:43:39|. |nstallation::CreateRestartEntryStartup()| 11:43:39|.. |ExecutionEngine::WorkerCompleted() |(01) Result of step execution: Result of 'InstallResultClass', Setup Succeeded: True; Reboot Required: NoReboot; Child Results Count: 0; Details: Return Value = 0; Recogrinzed as: Success 11:43:39|. |ExecutionEngine::WorkerCompleted() |(01) END executing step ImmediateReboot (), Complete 11:43:39|. |ExecutionEngine::WorkerCompleted() | 11:43:39|... |ExecutionTime::OnStepCompleted() |(01) OnStepCompleted: ImmediateReboot (), Complete ... --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows/desktop/taskschd/schtasks --- quote --- ... /SC schedule A value that specifies the schedule frequency. Valid values are: MINUTE, HOURLY, DAILY, WEEKLY, MONTHLY, ONCE, ONLOGON, ONIDLE, and ONEVENT. ... /MO modifier A value that refines the schedule type to allow for finer control over the schedule recurrence. Valid values are: MINUTE: 1 - 1439 minutes. HOURLY: 1 - 23 hours. DAILY: 1 - 365 days. WEEKLY: weeks 1 - 52. ONCE: No modifiers. ONSTART: No modifiers. ONLOGON: No modifiers. ONIDLE: No modifiers. MONTHLY: 1 - 12, or FIRST, SECOND, THIRD, FOURTH, LAST, and LASTDAY. ONEVENT: XPath event query string. --- quote --- Wine source: https://source.winehq.org/git/wine.git/blob/HEAD:/programs/schtasks/schtask… $ sha1sum SIMATIC_WinCC_Runtime_Advanced_V15_1.exe db1f97bb648b62fa1c5d974d7f2bcb6b4a9fd786 SIMATIC_WinCC_Runtime_Advanced_V15_1.exe $ du -sh SIMATIC_WinCC_Runtime_Advanced_V15_1.exe 1.3G SIMATIC_WinCC_Runtime_Advanced_V15_1.exe $ wine --version wine-4.7-305-g9bcaf9769c Regards -- 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 3