September 2023 - Wine-Bugs - list.winehq.org

[Bug 45461] New: OnScreenKeyboard Portable: App displays splash screen but does not start
by wine-bugs＠winehq.org March 2, 2024

March 2, 2024

https://bugs.winehq.org/show_bug.cgi?id=45461 Bug ID: 45461 Summary: OnScreenKeyboard Portable: App displays splash screen but does not start Product: Wine Version: 3.12 Hardware: x86-64 URL: https://portableapps.com/apps/accessibility/on-screen_ keyboard_portable OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tobbi.bugs(a)googlemail.com Created attachment 61801 --> https://bugs.winehq.org/attachment.cgi?id=61801 log After installing (extracting) OnScreenKeyboard Portable and tryin to run it, it does show the splash screen but does not start the actual program. $ openssl sha256 On-ScreenKeyboardPortable_2.0.paf.exe SHA256(On-ScreenKeyboardPortable_2.0.paf.exe)= 12c4943e1d7a65a12f7c58ac5aac3430b98c5158f18a94c51c26036770af19df -- 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 55149] New: Nancy Drew: Danger by Design exits on game start
by WineHQ Bugzilla March 2, 2024

March 2, 2024

https://bugs.winehq.org/show_bug.cgi?id=55149 Bug ID: 55149 Summary: Nancy Drew: Danger by Design exits on game start Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tiger12506(a)gmail.com Distribution: --- Created attachment 74715 --> https://bugs.winehq.org/attachment.cgi?id=74715 warn+all,+seh,+ddraw Nancy Drew: Danger By Design is 2 disc cd game. I have ISOs created from original discs that I am installing from. Setup.exe works fine -- I choose to change the install location to C:\ND\DangerbyDesign\ because previous attempts to run game from the default location result in it looking for a CIFTree file in the C:\ND\DangerbyDesign directory. That's not the issue. When installed correctly, the game appears to start, the screen goes black, resolution changes to the game's chosen 640x480, and then the game quits (leaving my linux desktop resolution in 640x480 mode). This is the issue. I assume this is a crash, but I either haven't found, or don't understand the outputs of the WINEDEBUG logs well enough to diagnose the issue. Any way that I can help you help me would be appreciated. -- 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 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 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

[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 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 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

[Bug 54346] New: (Multithreaded) Applications sometimes get heap corruption on exit due to ignoring critical sections in Wine
by WineHQ Bugzilla Feb. 24, 2024

Feb. 24, 2024

https://bugs.winehq.org/show_bug.cgi?id=54346 Bug ID: 54346 Summary: (Multithreaded) Applications sometimes get heap corruption on exit due to ignoring critical sections in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dmusic Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- (Multithreaded) Applications sometimes get heap corruption on exit due to ignoring critical sections in Wine. For instance dmloader:loader: 0118:warn:sync:RtlpWaitForCriticalSection process L"Z:\\home\\fgouget\\wine\\wine-gitlab\\dlls\\dmloader\\tests\\i386-windows\\dmloader_test.exe" is shutting down, returning STATUS_SUCCESS ... 0118:warn:sync:RtlpWaitForCriticalSection process L"Z:\\home\\fgouget\\wine\\wine-gitlab\\dlls\\dmloader\\tests\\i386-windows\\dmloader_test.exe" is shutting down, returning STATUS_SUCCESS 0118:err:sync:RtlLeaveCriticalSection section 00140074 "dlls/ntdll/heap.c: main process heap section" is not acquired Normally this does not cause the test to fail. But when running with WINEDEBUG=heap this frequently leads to heap corruption because: * Each call to the heap API triggers a heap validation. * Each heap_validate() call is requires taking the main process heap lock. * More contention makes the "not acquired" events more likely. * Leading to multiple threads manipulating the heap at the same time, thus causing corruption. Also, be aware that when heap corruption is detected due to WINEDEBUG=heap, Wine raises an exception which kills the process. Also note that although dmloader:loader looks like it is not multithreaded (no CreateThread() call), it loads dlls that create their own thread: * winealsa.drv/midi.c -> notify_thread * winealsa.drv/mmdevdrv.c -> alsa_timer_thread * winepulse.drv/mmdevdrv.c -> pulse_mainloop_thread, pulse_timer_cb ...etc. So this issue probably impacts most audio / multimedia applications and Wine tests. The "main process heap section is not acquired" errors most often look like they are caused by the following functions which are all called on DLL_PROCESS_DETACH: * msacm32.MSACM_WriteCache() calling RegSetValueExA() * ucrtbase.msvcrt_free_io() calling DeleteCriticalSection() when WINEDEBUG=heap Ignoring the critical sections during shutdown is intentional and was introduced by the 7def0f200f11 commit to fix bug 42470. See RtlpWaitForCriticalSection(): /* Don't allow blocking on a critical section during process termination */ if (RtlDllShutdownInProgress()) { WARN( "process %s is shutting down, returning STATUS_SUCCESS\n", debugstr_w(NtCurrentTeb()->Peb->ProcessParameters->ImagePathName.Buffer) ); return STATUS_SUCCESS; } However that commit also had to add todo_wine statements to kernel32:loader so it's not clear that is is correct. -- 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 46263] New: Final Fantasy XI crashes after accepting EULA when using Ashita
by wine-bugs＠winehq.org Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=46263 Bug ID: 46263 Summary: Final Fantasy XI crashes after accepting EULA when using Ashita Product: Wine-staging Version: 3.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)foreversmall.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62965 --> https://bugs.winehq.org/attachment.cgi?id=62965 Terminal Output with backtrace of crash. When using Ashita with FFXI the game crashes shortly after accepting the EULA. I've confirmed this with all the versions of wine starting from version 3.0 stable, all the way up to 3.21 staging. The only way I've been able to get the game to launch is to compile wine myself with the following patch: https://gitlab.com/farmboy0/wine/commit/54aea128e91a6b03bff05e79d9a09bea572… Its very easy to recreate, use all the standard AppDB info to get FFXI setup. Download ashita from the website: https://git.ashitaxi.com/Ashita/Ashitav3-Launcher/raw/master/Ashita.exe >From here you need all the ashita pre-reqs: http://docs.ashitaxi.com/requirements/ Setup a config file with the settings ../Ashita/Config/Boot/ You can launch the game via this command: wine %path_to_Ashita%/injector.exe "%CONFIGFILE%.xml" If it properly loads then once you accept the EULA it will crash. -- 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 17

[Bug 55584] New: Possibly incorrect handling of end_c in ARM64 process_unwind_codes
by WineHQ Bugzilla Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=55584 Bug ID: 55584 Summary: Possibly incorrect handling of end_c in ARM64 process_unwind_codes Product: Wine Version: unspecified Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: wine(a)corsix.org Distribution: --- In signal_arm64.c, unwind code 0xe5 (end_c) is considered in three places: 1. get_sequence_len 2. The while loop at the start of process_unwind_codes which skips codes 3. The main while loop in process_unwind_codes which performs codes Place 1 looks correct. Place 2 also looks fine, though I hope we'd never see end_c there (because we should only skip an amount identified by get_sequence_len). I am less certain about place 3 though; it currently treats end_c like end, whereas I think it should treat end_c like nop. The documentation at https://learn.microsoft.com/en-us/cpp/build/arm64-exception-handling?view=m… isn't great in describing end_c, though the example at "Unwind code for region 2" is a fairly clear example of end_c behaving like a nop for place 3. -- 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