wine-bugs May 2022

wine-bugs@winehq.org

1 participants
3908 discussions

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

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 May 2022