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

[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 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 50643] New: IK Product Manager: Unable to download plugins
by WineHQ Bugzilla Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=50643 Bug ID: 50643 Summary: IK Product Manager: Unable to download plugins Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: gearoidburke(a)outlook.com Distribution: --- Created attachment 69355 --> https://bugs.winehq.org/attachment.cgi?id=69355 Wine log file. IK Product Manger (https://www.ikmultimedia.com/products/productmanager/) should be able to download and install VST plugins from IK Multimedia, however upon clicking the install button for any plugin, the application will become unresponsive for a minute or so before resuming as if nothing had happened. The error in wine seems to be with wmic, with a wmic logicaldisk command failing. The download location, by default ~/Documents/IK Multimedia/IK Product Manager, is empty. Upon clicking the install button on a plugin again, nothing happens. IK Product Manager installs and works as expected up until this point, provided you have a dx11 compatibility layer like dxvk installed, though sometimes I need to use wine-staging to get it to run properly. I would have liked to have tested this in a 32 bit prefix so I could install wmi, but the application is 64 bit only. Wine version is 6.1-1, 64 bit architecture. Tested on both wine and wine-staging. OS is Arch Linux, 64 bit, kernel 5.10. Hardware: Thinkpad X13 Yoga, Intel Core i5-10310U with Intel integrated graphics. -- 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 46839] New: Happy Foto Designer Font not found "Fehler (Code 1) [ Font is not supported: Roboto]"
by wine-bugs＠winehq.org Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=46839 Bug ID: 46839 Summary: Happy Foto Designer Font not found "Fehler (Code 1) [Font is not supported: Roboto]" Product: Wine Version: 4.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: martin.marmsoler(a)gmail.com Distribution: --- Hello, while creating a new Photo book in Happy Foto Designer(https://www.happyfoto.at/) I get the following error: "Fehler (Code 1) [Font is not supported: Roboto]" The error can be solved by installing gdiplus, but the fonts are not drawn properly and only the first character is shown. -- 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 11

[Bug 52064] New: Solidworks 2008 crashes on startup - Regression since Wine 5.21
by WineHQ Bugzilla Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=52064 Bug ID: 52064 Summary: Solidworks 2008 crashes on startup - Regression since Wine 5.21 Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jpleonard12(a)gmail.com Distribution: --- Created attachment 71076 --> https://bugs.winehq.org/attachment.cgi?id=71076 Debug log file SolidWorks 2008 worked well on Wine (32bit) up through Wine 5.21. After this, it crashes on startup, once the full screen workspace is displayed. Sometimes it allows the user to browse for a file, but will always crash before the graphics are displayed. Laptop on which SolidWorks 2008 is still working almost flawlessly: --------------------------------------- Wine 5.21 (32bit/WinXP) Linux Mint 18.3, kernel 4.4.0.159-generic winetricks msxml6 vcrun2005 dotnet20 Mesa DRI Intel(R) Ivybridge Mobile 4.2 (Core Profile) Mesa 18.0.5 3.0 Mesa 18.0.5 Desktop on which SolidWorks crashes on startup ---------------------------------------------- Wine 6.21 (32bit/WinXP) Linux Mint 20.1 kernel 5.11.0.40-generic winetricks msxml6 vcrun2005 dotnet20 Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1) 4.2 (Core Profile) Mesa 21.0.3 3.0 Mesa 21.0.3 Have also attempted to run in plain 64 bit wine instance, as well as many combinations of msxml6, dotnet20, dotnet30, vcrun2005, gdiplus_winxp, as well as most versions of Wine 5.22 thru 6.21. But the crash always occurs in the same spot. -- 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 51458] New: Western Digital SSD Dashboard displays black screen
by WineHQ Bugzilla Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=51458 Bug ID: 51458 Summary: Western Digital SSD Dashboard displays black screen Product: Wine Version: 6.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 70302 --> https://bugs.winehq.org/attachment.cgi?id=70302 Console output The program installs, but when you try to run it, it just displays a black screen. Console output is attached. I'm guessing this is the problem: 0130:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. Dashboard version: 3.2.2.9 Installer version: 4.0.2.3 $ sha256sum DashboardSetup.exe 9670e6bd54e1e0729262f13ded12de56d0a02a0e29ba0c9e6e6cb3663de4c781 -- 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 8

[Bug 45901] New: Avoid GPU synchronization due to GPU-CPU transfer ( Overwatch)
by wine-bugs＠winehq.org Feb. 23, 2024

Feb. 23, 2024

https://bugs.winehq.org/show_bug.cgi?id=45901 Bug ID: 45901 Summary: Avoid GPU synchronization due to GPU-CPU transfer (Overwatch) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: awesie(a)gmail.com Distribution: --- Created attachment 62422 --> https://bugs.winehq.org/attachment.cgi?id=62422 Patch to avoid GPU synchronization One performance gap with Overwatch on Wine + AMD + Mesa is GPU synchronization due to transfers from GPU texture to CPU texture. By using PBOs and glReadPixels with GL_PIXEL_PACK_BUFFER, we can avoid this synchronization leading to improved performance. The attached patch is one approach to resolve the performance issue, but I am not sure that it is the best way. Feedback is appreciated. Also attached is before and after screenshots with Mesa's HUD. You can observe that the buffer wait time decreases with the patched version. Both the before and after screenshots are on wine-staging master plus my patch for 45723. -- 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