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

[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

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

Feb. 23, 2024

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(a)16 () from /home/benutzer/.local/share/rr/wine-1/mmap_pack_343_ntdll.dll #9 0x7b0561af in RegOpenKeyExW(a)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 Feb. 23, 2024

Feb. 23, 2024

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 50098] New: FFXIV_Textools crashes on start
by WineHQ Bugzilla Feb. 18, 2024

Feb. 18, 2024

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 54093] New: Tomb Raider Level Editor - Custom Level "Biohazard" has problems loading Save-File
by WineHQ Bugzilla Feb. 15, 2024

Feb. 15, 2024

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 55205] New: Fixed scancodes patchset partially breaks keyboard input in NFS Underground
by WineHQ Bugzilla Feb. 14, 2024

Feb. 14, 2024

https://bugs.winehq.org/show_bug.cgi?id=55205 Bug ID: 55205 Summary: Fixed scancodes patchset partially breaks keyboard input in NFS Underground Product: Wine-staging Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aidas957(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: ArchLinux Created attachment 74801 --> https://bugs.winehq.org/attachment.cgi?id=74801 x11drv,+dinput,+keyboard,+key log with autodetection disabled Hello, So NFS Underground (and likely Underground 2 considering it also uses ActionMap stuff) has partially broken keyboard input with wine-staging if the fixed scancodes patchset is enabled The first thing you notice in the main menu is that the arrow keys don't work at all Also the mappings you set in vanilla Wine/wine-staging without the patchset have slightly changed if you can actually get into the mapping menu (this is with a standard US QWERTY layout by the way) What's interesting is if you enable scancode autodetection in winecfg things go back to normal I have attached a +x11drv,+dinput,+keyboard,+key log with scancode autodetection disabled (I'll send another log with that option enabled after submitting this bug because of Bugzilla limitations) -- 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 47116] New: Indiana Jones and the Emperor's Tomb: white line
by wine-bugs＠winehq.org Feb. 11, 2024

Feb. 11, 2024

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