wine-bugs March 2023

wine-bugs@winehq.org

1 participants
3532 discussions

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

25 Feb '24

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 24 Feb '24

24 Feb '24

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 23 Feb '24

23 Feb '24

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 23 Feb '24

23 Feb '24

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 23 Feb '24

23 Feb '24

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 23 Feb '24

23 Feb '24

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 23 Feb '24

23 Feb '24

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 23 Feb '24

23 Feb '24

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

[Bug 50297] New: Blindwrite 7 crashes with a stack overflow (followup to #49092)
by WineHQ Bugzilla 23 Feb '24

23 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=50297 Bug ID: 50297 Summary: Blindwrite 7 crashes with a stack overflow (followup to #49092) Product: Wine Version: 5.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 68867 --> https://bugs.winehq.org/attachment.cgi?id=68867 Do wineserver calls on a different stack by using fibers. I still can reproduce this issue with wine-6.0-rc1. 00f0:err:virtual:virtual_setup_exception stack overflow 4548 bytes in thread 00f0 addr 0x40e68e stack 0x21fe3c (0x220000-0x221000-0x320000) (rr) bt 30 #0 0xb7db9b5e in __libc_disable_asynccancel (oldtype=0) at ../nptl/cancellation.c:72 #1 0xb7e35705 in __GI___writev (iovcnt=2, iov=0x222058, fd=3) at ../sysdeps/unix/sysv/linux/writev.c:26 #2 __GI___writev (fd=3, iov=0x222058, iovcnt=2) at ../sysdeps/unix/sysv/linux/writev.c:24 #3 0xb7bd68ae in send_request (req=0x2221ac) at .../wine-git/dlls/ntdll/unix/server.c:213 #4 0xb7bd69f0 in server_call_unlocked (req_ptr=0x2221ac) at .../wine-git/dlls/ntdll/unix/server.c:273 #5 0xb7bd6a4b in wine_server_call (req_ptr=0x2221ac) at .../wine-git/dlls/ntdll/unix/server.c:289 #6 0xb7bcf1cd in NtOpenKeyEx (key=0x222340, access=131097, attr=0x2222b8, options=0) at .../wine-git/dlls/ntdll/unix/registry.c:112 #7 0xb7bb11be in __wine_syscall_dispatcher () from /home/benutzer/.local/share/rr/wine-1/mmap_pack_2_ntdll.so #8 0x7bc0bdcc in NtOpenKeyEx@16 () from /home/benutzer/.local/share/rr/wine-1/mmap_pack_343_ntdll.dll #9 0x7b0561af in RegOpenKeyExW@20 (hkey=<optimized out>, name=0x46c06dc, options=0, access=131097, retkey=0x222340) at .../wine-git/dlls/kernelbase/registry.c:208 #10 0x006996a6 in ?? () #11 0x0069ab41 in ?? () #12 0x00699e14 in ?? () #13 0x0069a89b in ?? () #14 0x0069a84f in ?? () #15 0x0073bb4b in ?? () #16 0x007354d2 in ?? () #17 0x00736cc5 in ?? () #18 0x00736f53 in ?? () #19 0x00737f77 in ?? () #20 0x007384a9 in ?? () #21 0x00a9a1a7 in ?? () #22 0x00a99388 in ?? () #23 0x00a99394 in ?? () #24 0x00a99394 in ?? () #25 0x00a99394 in ?? () #26 0x00a99394 in ?? () #27 0x00a99394 in ?? () #28 0x00a99394 in ?? () ... I tried to have another look and got to the impression that blindwrite expects RegOpenKeyExW and RegSetValueExW too use less stack. I experimented a bit and one way to achive this was to do the work in these functions on a different stack. Attached proof of concept uses fibers for this. With this patch blindwrite can finish its stack exhaustion without visible error and shows the trial option dialog. After one successful start that patch is no longer necessarry. Another option to might be to use some more guard pages and switch them to regular pages when we are inside wine code? -- 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 10

[Bug 16911] New: WriteProcessMemory() not working for memory protected by X11DRV_DIB_DoProtectDIBSection()
by wine-bugs＠winehq.org 23 Feb '24

23 Feb '24

http://bugs.winehq.org/show_bug.cgi?id=16911 Summary: WriteProcessMemory() not working for memory protected by X11DRV_DIB_DoProtectDIBSection() Product: Wine Version: 1.1.12 Platform: PC OS/Version: Linux Status: UNCONFIRMED Keywords: patch, source Severity: minor Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: thestig(a)google.com Created an attachment (id=18660) --> (http://bugs.winehq.org/attachment.cgi?id=18660) test program Hi, I have a test case here that works on WinXP but not Wine. I deliberately wrote a standalone test case because I'm not sure which unit test to put it in. It's in fact based off of dlls/kernel32/tests/virtual.c where the other WriteProcessMemory() test is. In this test case, we call CreateDIBSection() which returns a HBITMAP (hbitmap) and some memory (mem). Next, we call SetDIBits() with hbitmap. We get into X11DRV_SetDIBits(), where it calls X11DRV_DIB_Lock( physBitmap, DIB_Status_GdiMod );. This marks the memory (mem) as PAGE_NOACCESS, and leaves it in that state as SetDIBts() returns. Normally if the process tries to access it, we get a page fault that's handled by X11DRV_DIB_FaultHandler(), and everything works. However, when the test code calls WriteProcessMemory(), we talk to wineserver in NtWriteVirtualMemory(). In wine_server_call(), we do send_request(), where writev() tries to read 'mem' and fails with EFAULT. This doesn't trigger X11DRV_DIB_FaultHandler(), and WriteProcessMemory() fails. -- 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 5

[Bug 12401] New: Support junction points, i.e. DeviceIoCtl( FSCTL_SET_REPARSE_POINT/FSCTL_GET_REPARSE_POINT)
by wine-bugs＠winehq.org 22 Feb '24

22 Feb '24

http://bugs.winehq.org/show_bug.cgi?id=12401 Summary: Support junction points, i.e. DeviceIoCtl(FSCTL_SET_REPARSE_POINT/FSCTL_GET_REPARSE_PO INT) Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Junction points are one of Microsoft's answers to symlinks. Unix symlinks could be mapped into junction points. This would allow applications (e.g. Picasa) avoid following symlinks if they wanted to. Also, the .net 2 installer would be happier in winxp mode if wine supported junction points (see bug 10601): "The .NET 2.0 Framework installer checks if the target volume is NTFS filesystem type and then uses the FSCTL_SET_REPARSE_POINT ioctl (used for mount points and junctions) to create junction points for each registered assembly in Windows SxS directory to GAC assembly directory (link target). Basically the junction point is used to redirect access from one directory to another." Tommy Kho posted a patch to add a conformance test for getting and setting junction points, http://www.winehq.org/pipermail/wine-patches/2006-March/024956.html but it was not accepted. -- 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 88

[Bug 50098] New: FFXIV_Textools crashes on start
by WineHQ Bugzilla 18 Feb '24

18 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=50098 Bug ID: 50098 Summary: FFXIV_Textools crashes on start Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nsextyfour(a)protonmail.com Distribution: --- Created attachment 68574 --> https://bugs.winehq.org/attachment.cgi?id=68574 I try to start FFXIV_TexTools, and then try to copy the text from the error dialog. FFXIV Textools, a modding tool for Final Fantasy XIV, will not launch in Wine. https://textools.dualwield.net/ It brings up an error window, and when I try to copy the text from it, the window disappears due to a crash. If I click 'yes', I get another error window. Clicking yes on this brings another, and then another. After the fourth, the program closes. -- 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 52250] New: windows.h WINE_NOWINSOCK check has been removed
by WineHQ Bugzilla 16 Feb '24

16 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=52250 Bug ID: 52250 Summary: windows.h WINE_NOWINSOCK check has been removed Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: sacrom(a)gmail.com Distribution: --- I'm using winelib to compile a Windows/Linux application, where we want to use the Linux code for threads, files system handling, network code, shared memory... and we want WINE just for the Win32 GUI code (as we did not implement a GUI in the Linux/Unix side just on Windows) Since WINE 6.8 (due this commit https://source.winehq.org/git/wine.git/commit/9603fba8943f9699e3af6fcfe4acb…) the WINE_NOWINSOCK check: #ifndef WINE_NOWINSOCK #include <winsock.h> #endif /* WINE_NOWINSOCK */ Has been removed, now my application does not compile as I'm mixing Linux socket definitions with the WINE/Windows "winsock.h" file. If I add this check to the file, the application does compile as with WINE 6.7 Is it possible to add the check back? or should this be done in another way now? -- 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 16

[Bug 54093] New: Tomb Raider Level Editor - Custom Level "Biohazard" has problems loading Save-File
by WineHQ Bugzilla 15 Feb '24

15 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=54093 Bug ID: 54093 Summary: Tomb Raider Level Editor - Custom Level "Biohazard" has problems loading Save-File Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Hello everyone, download link is at: https://www.trle.net/levels/levels/2021/0621/TombRaider95-TRBiohazard.zip with a sha256sum of: bash-5.1$ sha256sum TombRaider95-TRBiohazard.zip 58b35b648ecaaab691ce9904833730953ae155b4556d752f70d0f0a7442bcfa7 TombRaider95-TRBiohazard.zip Please note that it comes with its own Tomb4.exe and you don't need to have your own copy of any "Tomb Raider" episode. Unpacking the .zip file and running Tomb4.exe is fine. Still created its own prefix though. The problem I am facing is that (at least in the first level) you can save your game state (press Escape to get to menu and press the Arrow-Downkey) but then in turn this new game state isn't being loaded. The progress bar when loading the state goes to 100% but then nothing more happens and you can't get back into the game from where you left off. bash-5.1$ /sbin/lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] bash-5.1$ wine --version wine-7.22 Console output will follow in the next couple of minutes. -- 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 21

[Bug 50177] New: War Thunder Launcher doesn't render anything, just spams d2d_geometry_sink_AddArc stubs
by WineHQ Bugzilla 14 Feb '24

14 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=50177 Bug ID: 50177 Summary: War Thunder Launcher doesn't render anything, just spams d2d_geometry_sink_AddArc stubs Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: fzatlouk(a)redhat.com Distribution: --- Created attachment 68699 --> https://bugs.winehq.org/attachment.cgi?id=68699 stdout It appears WarThunder Launcher might need d2d_geometry_sink_AddArc . It keeps spaming "0108:fixme:d2d:d2d_geometry_sink_AddArc iface 0B274638, arc 0031DB90 stub!" with stuck window with background from underneath it. Tested Wine 5.19 - 5.22 in Windows XP and Windows 10 modes. -- 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 47116] New: Indiana Jones and the Emperor's Tomb: white line
by wine-bugs＠winehq.org 11 Feb '24

11 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=47116 Bug ID: 47116 Summary: Indiana Jones and the Emperor's Tomb: white line Product: Wine Version: 4.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)free.fr Distribution: --- Created attachment 64326 --> https://bugs.winehq.org/attachment.cgi?id=64326 screen captures with white lines Hello, to play Indiana Jones and the Emperor's Tomb with Wine, I know I have to: - override dll msvcrt bug 27594 - disable vertex shader 12400 But now I have a new graphic issue with Wine 4.7 (even with staging version): look at the screen captures I joined to this bug report, there are white lines. -- 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 12

[Bug 49199] New: Wine on macOS no longer loads dylibs from /lib(64)
by WineHQ Bugzilla 11 Feb '24

11 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=49199 Bug ID: 49199 Summary: Wine on macOS no longer loads dylibs from /lib(64) Product: Wine Version: 5.6 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gcenx83(a)gmail.com Starting from Wine-5.6 the libwine wrappers have been removed in favor of using dlopen() however this now causes component in question to no longer load embedded dylibs into /lib(64) Here’s an example; ```907aaf9e72714293909351648827e7c5aebc12a3 is the first bad commit commit 907aaf9e72714293909351648827e7c5aebc12a3 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Apr 6 11:46:10 2020 +0200 gdi32: Use standard dlopen() instead of the libwine wrappers. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/gdi32/dibdrv/opengl.c | 12 +++++------- dlls/gdi32/freetype.c | 20 ++++++++++---------- 2 files changed, 15 insertions(+), 17 deletions(-)``` Any commit doing “ Use standard dlopen() instead of the libwine wrappers.” will now experience this. Previous behavior was the ability to simply embed dylibs into /lib(64) and wine(64) would load them as needed, now rpath is required. Winehq packages will also experience this issue worse once the current embedded libraries swap to using dlopen() -- 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 20

[Bug 39859] New: WineHQ packages for wine-gecko and wine-mono
by wine-bugs＠winehq.org 11 Feb '24

11 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=39859 Bug ID: 39859 Summary: WineHQ packages for wine-gecko and wine-mono Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Most users of the distros we now package for are accustomed to installing wine-gecko and wine-mono from packages. We should provide them. -- 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 53656] New: cannot install an update because of Conflicting Values set for option
by WineHQ Bugzilla 11 Feb '24

11 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=53656 Bug ID: 53656 Summary: cannot install an update because of Conflicting Values set for option Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thereal7kqx(a)gmail.com Distribution: --- Created attachment 73058 --> https://bugs.winehq.org/attachment.cgi?id=73058 the error I am using LMDE 5, based on Debian, and this (bug?) is dragging me down ive tried everything i can to remove this stuff, but the delete button is just shaded black, or it spats out bullshit that it cant be removed. -- 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 54181] New: nothing provides wine-devel64 = 1:8.0.rc1-1.1 needed by winehq-devel-1:8.0.rc1-1.x86_64
by WineHQ Bugzilla 11 Feb '24

11 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=54181 Bug ID: 54181 Summary: nothing provides wine-devel64 = 1:8.0.rc1-1.1 needed by winehq-devel-1:8.0.rc1-1.x86_64 Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thegamemaster(a)hotmail.com Distribution: --- In Fedora 37 KDE Spin on Toshiba Satellite L655. Upon sudo dnf update -y error returned "Problem: cannot instal the best update candidate for package winehq-devel-1:7.22-1.1.x86_66 - nothing provides wine-devel64 = 1:8.0.rc1-1.1 needed by winehq-devel-1:8.0.rc1-1.1.x86_64 wine will not update. -- 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 47558] New: Ubuntu package for 4.12.1 cannot open project in Adobe Premiere Pro 2.0
by wine-bugs＠winehq.org 11 Feb '24

11 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=47558 Bug ID: 47558 Summary: Ubuntu package for 4.12.1 cannot open project in Adobe Premiere Pro 2.0 Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: julius.schwartzenberg(a)gmail.com CC: dimesio(a)earthlink.net, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 64946 --> https://bugs.winehq.org/attachment.cgi?id=64946 output of Wine When I run Adobe Premiere Pro 2.0 with Wine 4.12.1 in Ubuntu, I get the following dialog when trying to open a project: Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project. Rebuilding Wine myself from Git, currently the latest commit matches 4.12.1, does not show this problem. -- 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 50692] New: Office 2019 Professional Plus doesn't install
by WineHQ Bugzilla 11 Feb '24

11 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=50692 Bug ID: 50692 Summary: Office 2019 Professional Plus doesn't install Product: Wine Version: 6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: atillolann-1815(a)yopmail.com Distribution: --- Created attachment 69422 --> https://bugs.winehq.org/attachment.cgi?id=69422 Terminal Log Tried intalling Office 2019 ProPlus Retail, after the loading screen the installer crashes. Using Wine 6.2-developer Arch: x86_64 Distro: Linux Mint 19.0 Cinnamon 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 32

[Bug 14010] New: RivaTuner 2.09 not work ,no overclocking or sensor ability
by wine-bugs＠winehq.org 10 Feb '24

10 Feb '24

http://bugs.winehq.org/show_bug.cgi?id=14010 Summary: RivaTuner 2.09 not work ,no overclocking or sensor ability Product: Wine Version: 1.0.0 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dj--alex(a)ya.ru RivaTuner 2.09 not work ,no overclocking or sensor ability My videocard is very loud without this program!! I and not only i, want to overclocking without BIOS VRAM rewrite. Program can be downloaded free from http://www.radeon.ru/ (Main menu left - newest version) -- 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 4

[Bug 51360] New: vkGetDeviceProcAddr invalid behavior for functions from extensions unsupported by host Vulkan instance
by WineHQ Bugzilla 09 Feb '24

09 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=51360 Bug ID: 51360 Summary: vkGetDeviceProcAddr invalid behavior for functions from extensions unsupported by host Vulkan instance Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: loothelion(a)nvidia.com Distribution: --- I believe the below may also be true for vkGetInstanceProcAddr, but I haven't confirmed this locally. The Vulkan 1.2.182 specification states the following about the behavior of vkGetDeviceProcAddr: > The table below defines the various use cases for vkGetDeviceProcAddr and > expected return value for each case. > > The returned function pointer is of type PFN_vkVoidFunction, and must be cast to > the type of the command being queried before use. The function pointer must only > be called with a dispatchable object (the first parameter) that is device or a > child of device. > > Table 2. vkGetDeviceProcAddr behavior > > device | pName | return value > --------------------------------------------------------------------------------------- > NULL | *[1] | undefined > --------------------------------------------------------------------------------------- > invalid device | *[1] | undefined > --------------------------------------------------------------------------------------- > device | NULL | undefined > --------------------------------------------------------------------------------------- > device | core device-level Vulkan command [2] | fp[3] > --------------------------------------------------------------------------------------- > device | enabled extension device-level commands [2] | fp[3] > --------------------------------------------------------------------------------------- > any other case, not covered above | NULL > > [1] - "*" means any representable value for the parameter (including valid > values, invalid values, and NULL). > > [2] - In this function, device-level excludes all physical-device-level > commands. > > [3] - The returned function pointer must only be called with a dispatchable > object (the first parameter) that is device or a child of device e.g. > VkDevice, VkQueue, or VkCommandBuffer. Winevulkan's behavior differs from this slightly. Note the fifth row of the table uses the language "enabled extension device-level commands", this means that if a command is queried via vkGetDeviceProcAddr and isn't part of core, the extension which introduces it must be enabled for the given VkDevice object in order for vkGetDeviceProcAddr to return a valid function pointer, and otherwise it should return NULL. In order to properly conform to the Vulkan specification Winevulkan should only expose device-level commands whose extensions have been enabled. Note that applications should not be querying for Vulkan commands via vkGetDeviceProcAddr if they know the extension is not supported by the underlying implementation. However in the case of an application which does rely on this bad behavior, Winevulkan will return a function pointer to one of its thunks and then proceed to deference a null function pointer when it tries to call into the underlying host Vulkan implementation. -- 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 47521] New: digikam 6.10 crashes on start
by wine-bugs＠winehq.org 09 Feb '24

09 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=47521 Bug ID: 47521 Summary: digikam 6.10 crashes on start Product: Wine Version: 4.11 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo Created attachment 64913 --> https://bugs.winehq.org/attachment.cgi?id=64913 crash output Backtrace: =>0 0x66401f0a EntryPoint+0xb6a() in qt5widgets (0x006ff4f8) 1 0x1084cf64 WXMPUtils_DuplicateSubtree_1+0x44c5d3() in libdigikamcore (0x737adae8) 2 0x10388bb9 EntryPoint+0x387818() in libdigikamcore (0x006ff5f8) 3 0x104c0cba WXMPUtils_DuplicateSubtree_1+0xc0329() in libdigikamcore (0x006ff688) 4 0x2278b630 EntryPoint+0xba28f() in libdigikamgui (0x006ffab8) 5 0x2276e7b3 EntryPoint+0x9d412() in libdigikamgui (0x006ffb98) 6 0x00404be5 _ZN7Digikam6DColor11premultiplyEv+0x15e4() in digikam (0x006ffe88) 7 0x00401382 EntryPoint+0xffffffff() in digikam (0x006fff28) 8 0x7b47e022 call_process_entry+0x11() in kernel32 (0x006fff48) 9 0x7b480acc start_process+0xeb(entry=<couldn't compute location>, peb=<couldn't compute location>) [Z:\home\austin\wine-git\dlls\kernel32\process.c:1297] in kernel32 (0x006fffd8) 10 0x7b47e02e start_process_wrapper+0x9() in kernel32 (0x006fffec) 0x66401f0a EntryPoint+0xb6a in qt5widgets: movl 0x4(%eax),%ecx austin@laptop:~/Downloads$ du -sh digiKam-6.1.0-Win32.exe 321M digiKam-6.1.0-Win32.exe austin@laptop:~/Downloads$ sha256sum digiKam-6.1.0-Win32.exe fb870263a8bb2bd178590dfacfe68110b68d8c5b0ca53606084162a1a5e42b44 digiKam-6.1.0-Win32.exe -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs March 2023