wine-bugs August 2023

wine-bugs@winehq.org

1 participants
3065 discussions

[Bug 28659] New: rpcrt4/server test crashes on 32-bit FreeBSD9
by wine-bugs＠winehq.org 16 Nov '23

16 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=28659 Bug #: 28659 Summary: rpcrt4/server test crashes on 32-bit FreeBSD9 Product: Wine Version: 1.3.30 Platform: x86 OS/Version: FreeBSD Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: rpc AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Created attachment 36831 --> http://bugs.winehq.org/attachment.cgi?id=36831 backtrace The rpcrt4/rpc test fails as well, but that may be related to missing ntlm_auth (which I haven't found how to satisfy on FreeBSD). The server test shows that same error, but also crashes, so something nastier is going on. Backtrace attached. -- 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 9

[Bug 53095] New: system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2
by WineHQ Bugzilla 15 Nov '23

15 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53095 Bug ID: 53095 Summary: system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2 Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zizka(a)seznam.cz Distribution: --- Created attachment 72524 --> https://bugs.winehq.org/attachment.cgi?id=72524 1) Wine 7.0 crash; 2) Attempts to run with the Wine bundled by the vendor (i-deal Games) App: "Jagged Alliance 2 - Wildfire" from Steam Wine 7.0 Ubuntu 2022.04 I am trying to make Jagged Alliance run. The Wine distributed with Jagged Alliance seems not to work, because it has 36 byte long libwine.so and Wine doesn't even start. See the "JA 2 dist Wine log" below. So I tried with Wine 7.0 (current stable), and it failed with: system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2 Along that, the system switched to fullscreen, with the whole screen black. On a second run, Wine crashed - see the 1st part of the attached text. I will try to contact the company and ask if they could figure out. But in the meantime, I think this is a valid bug on an old Win32 game which could be present on some others. Thanks to anyone who takes a look. -- 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 22904] New: Register URL protocol handlers under Linux
by wine-bugs＠winehq.org 15 Nov '23

15 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=22904 Summary: Register URL protocol handlers under Linux Product: Wine Version: unspecified Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: kempe.marcus(a)gmail.com winemenubuilder is able to automatically register file type associations and build menus under Linux, when triggered by an application under wine. It would be great if the same thing were true for protocol handlers, so that these would become registered in much the same way as when using gconftool in gnome: gconftool -s /desktop/gnome/url-handlers/spotify/command 'wine c:\\spotify\\spotify.exe %s' --type String gconftool-2 -s /desktop/gnome/url-handlers/spotify/enabled --type Boolean true Would this be possible, hard, or maybe not a good idea? -- 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 12

[Bug 20474] New: Wine can't be built with GCC in C99 mode
by wine-bugs＠winehq.org 14 Nov '23

14 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=20474 Summary: Wine can't be built with GCC in C99 mode Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env AssignedTo: wine-bugs(a)winehq.org ReportedBy: yann(a)droneaud.fr For multiple reason, wine can't be built by GCC in C99 mode ( --std=c99 ). In particular, wine rely on GCC behavor regarding to extern inline. It produces errors regarding asm construct conflicting with extern inline symbols. It produces errors with multiple defination of inline function in object files. According to this, it seems that wine is not compatible with C99, but rely a lot on GCC specific behavor. See also bug #20306 -- 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 26

[Bug 53216] New: d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs
by WineHQ Bugzilla 13 Nov '23

13 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53216 Bug ID: 53216 Summary: d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs: d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected 4.99999994e-003. d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected 4.99999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected 7.49999994e-003. d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected 7.49999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected 1.24999999e-002. d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected 1.24999999e-002. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected 6.42500000e-001. d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected 6.42500000e-001. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:27965: Test marked todo: Got 0xffffff00, expected 0x00ffffff at (0, 0, 0), sub-resource 0. d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected 0x147ae (4.99999553e-003). d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected 0x147ae (4.99999553e-003). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected 0x1eb85 (7.49999329e-003). d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected 0x1eb85 (7.49999329e-003). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected 0x33333 (1.24999888e-002). d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected 0x33333 (1.24999888e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected 0xa47ae1 (6.42500022e-001). d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected 0xa47ae1 (6.42500022e-001). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290 (1.00099184e-002). d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290 (1.00099184e-002). d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334 (1.25123980e-002). d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334 (1.25123980e-002). d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b (1.75020981e-002). d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b (1.75020981e-002). d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a (6.42496376e-001). d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a (6.42496376e-001). https://test.winehq.org/data/patterns.html#d3d11:d3d11 These failures: * Don't happen on Debian 11 + Intel / KDE * Happen on Debian 11 + QXL + single-monitor * Happen on Debian 11 + QXL + multi-monitor * Don't happen on Debian Testing + QXL + multi-monitor So they are probably caused by some bug in the Debian 11 QXL support. Note that despite being systematic these failures could cause false positives due to the test multi-threading (see bug 53212). -- 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 55214] New: Overwatch 2 crashes on launch on macOS
by WineHQ Bugzilla 12 Nov '23

12 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55214 Bug ID: 55214 Summary: Overwatch 2 crashes on launch on macOS Product: Wine-staging Version: 8.12 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yehia.wael(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Created attachment 74824 --> https://bugs.winehq.org/attachment.cgi?id=74824 Crash backtrace Overwatch 2 fails to launch on macOS, both when compiled with --enable-archs=i386,x86_64 and without. The game is launched directly from _retail_/Overwatch.exe and works as expected on Linux (tested on Ubuntu 22.04 and Archlinux, with both packaged and self-compiled wine versions), but does not launch on macOS. -- 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 54642] New: Page fault on read access to 0x0000
by WineHQ Bugzilla 12 Nov '23

12 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54642 Bug ID: 54642 Summary: Page fault on read access to 0x0000 Product: Wine-staging Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: santafejayyt(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 74172 --> https://bugs.winehq.org/attachment.cgi?id=74172 Wine debugger backtrace on game start I'm attempting to run Konami's E-Amusement Cloud Sound Voltex Exceed Gear game, and the launcher and its components work fine, however when attempting to launch the game, the window opens, but the game does not start, and stays on a black screen. I have installed the required dependencies for the game via winetricks (DXVK / D3DX9, FAudio, & XACT). -- 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 24

[Bug 55086] New: Dotnet 7: System.Net.WebSockets.WebSocketException (0x80004005) - SSL cannot be established
by WineHQ Bugzilla 12 Nov '23

12 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55086 Bug ID: 55086 Summary: Dotnet 7: System.Net.WebSockets.WebSocketException (0x80004005) - SSL cannot be established Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: reiichi001(a)gmail.com Distribution: --- Created attachment 74637 --> https://bugs.winehq.org/attachment.cgi?id=74637 Error message from POC, which matches error from game modding project As part of a game modding project, I maintain a plugin that makes use of Discord.Net to relay game messages to Discord. In recent versions of Wine with .Net 7 for Windows installed (as required by the modding project, as it uses Windows .Net 7), Discord.Net will fail to connect. Previously, this was due to WebSocket mishandling, which looks to have been fixed in Wine 7.18. When trying to connect to Discord's gateway in Wine 8.10 (current staging), an SSL exception occurs and the connection fails. Please see attached logs. I've made a quick POC with minimal functionality that can be used for testing/code review. It will run fine on Windows and on native .Net 7 installations, but not in Wine. On discord, the bot will accept a single text command, xl!ping and will respond with "pong" in an embed if working. In Wine, it never connects as noted above. https://github.com/reiichi001/DiscordNetWinePOC -- 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 55070] New: winemenubuilder adds incorrect prefix on 32bit only Wine
by WineHQ Bugzilla 11 Nov '23

11 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55070 Bug ID: 55070 Summary: winemenubuilder adds incorrect prefix on 32bit only Wine Product: Wine Version: 8.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dofficialgman(a)gmail.com Distribution: --- On 32bit (x86 only) wine, the Exec= line automatically created in an application's .desktop file is incorrect and can not be launched. eg: /home/gman/.local/share/applications/wine/Programs/7-Zip/7-Zip\ File\ Manager.desktop ``` [Desktop Entry] Name=7-Zip File Manager Exec=env WINEPREFIX="/home/gman/.wine/dosdevices/f:/home/gman/.wine" wine C:\\\\users\\\\gman\\\\AppData\\\\Roaming\\\\Microsoft\\\\Windows\\\\Start\\ Menu\\\\Programs\\\\7-Zip\\\\7-Zip\\ File\\ Manager.lnk Type=Application StartupNotify=true Icon=EA23_7zFM.0 StartupWMClass=7zfm.exe ``` 64bit (x64 with WOW64) wine does not have this issue and the generated .desktop file will be correct. eg: /home/gman/.local/share/applications/wine/Programs/7-Zip/7-Zip\ File\ Manager.desktop ``` [Desktop Entry] Name=7-Zip File Manager Exec=env WINEPREFIX="/home/gman/.wine" wine C:\\\\users\\\\gman\\\\AppData\\\\Roaming\\\\Microsoft\\\\Windows\\\\Start\\ Menu\\\\Programs\\\\7-Zip\\\\7-Zip\\ File\\ Manager.lnk Type=Application StartupNotify=true Icon=EA23_7zFM.0 StartupWMClass=7zfm.exe ``` Both are with fresh wine installs with fresh/clean prefixes. Confirmed on multiple devices. -- 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 14

[Bug 54183] New: wineserver crash when running d3d9:visual
by WineHQ Bugzilla 11 Nov '23

11 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54183 Bug ID: 54183 Summary: wineserver crash when running d3d9:visual Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: NEW Keywords: testcase Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: rbernon(a)codeweavers.com Distribution: --- d3d9:visual on this machine breaks somewhere in the middle, apparently while trying to do mode switches, and leaves the display switched off. Not sure what triggers it exactly; I've certainly had working runs on other machines. What's important is that then when d3d9_test.exe exits, it triggers a wined3d crash. Simple tl;dr version is that set_cursor_pos gets triggered not from a client request, and tries to access current->process, which crashes. The backtrace is: Core was generated by `/home/elizabeth/git/wine64/loader/../server/wineserver -d'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop@entry=0x5598ea1ce5d0, x=32767, y=32767) at ../wine/server/queue.c:427 427 if ((device = current->process->rawinput_mouse) && (device->flags & RIDEV_NOLEGACY)) (gdb) bt #0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop@entry=0x5598ea1ce5d0, x=32767, y=32767) at ../wine/server/queue.c:427 #1 0x00005598e8b43c7b in set_clip_rectangle (desktop=desktop@entry=0x5598ea1ce5d0, rect=rect@entry=0x0, send_clip_msg=send_clip_msg@entry=1) at ../wine/server/queue.c:476 #2 0x00005598e8b43da1 in set_foreground_input (input=0x0, desktop=0x5598ea1ce5d0) at ../wine/server/queue.c:483 #3 set_foreground_input (input=0x0, desktop=0x5598ea1ce5d0) at ../wine/server/queue.c:480 #4 thread_input_destroy (obj=0x5598ea1ba430) at ../wine/server/queue.c:1106 #5 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ba430) at ../wine/server/object.c:451 #6 release_object (ptr=0x5598ea1ba430) at ../wine/server/object.c:440 #7 0x00005598e8b43800 in msg_queue_destroy (obj=0x5598ea1ae4d0) at ../wine/server/queue.c:1077 #8 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ae4d0) at ../wine/server/object.c:451 #9 release_object (ptr=ptr@entry=0x5598ea1ae4d0) at ../wine/server/object.c:440 #10 0x00005598e8b3224e in release_object_from_handle (obj=0x5598ea1ae4d0) at ../wine/server/handle.c:115 #11 handle_table_destroy (obj=0x5598ea1d3810) at ../wine/server/handle.c:185 #12 0x00005598e8b3b144 in release_object (ptr=0x5598ea1d3810) at ../wine/server/object.c:451 #13 release_object (ptr=0x5598ea1d3810) at ../wine/server/object.c:440 #14 0x00005598e8b3260f in close_process_handles (process=process@entry=0x5598ea1ce7a0) at ../wine/server/handle.c:197 #15 0x00005598e8b3d990 in process_killed (process=0x5598ea1ce7a0) at ../wine/server/process.c:970 #16 remove_process_thread (process=0x5598ea1ce7a0, thread=thread@entry=0x5598ea1d4020) at ../wine/server/process.c:1020 #17 0x00005598e8b5b37f in kill_thread (thread=0x5598ea1d4020, violent_death=<optimized out>, violent_death@entry=0) at ../wine/server/thread.c:1294 #18 0x00005598e8b3dcb0 in kill_process (violent_death=0, process=0x5598ea1ce7a0) at ../wine/server/process.c:1077 #19 kill_process (process=0x5598ea1ce7a0, violent_death=<optimized out>) at ../wine/server/process.c:1058 #20 0x00005598e8b2d587 in fd_poll_event (event=<optimized out>, fd=<optimized out>) at ../wine/server/fd.c:542 #21 main_loop_epoll () at ../wine/server/fd.c:636 #22 0x00005598e8b2d7ee in main_loop () at ../wine/server/fd.c:992 #23 0x00005598e8b1ea7d in main (argc=2, argv=0x7ffd26625e48) at ../wine/server/main.c:237 Rémi, do you have any immediate insight on what we should be doing here? -- 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 16552] New: CreateIoCompletionPort fails in Chromium unit tests
by wine-bugs＠winehq.org 11 Nov '23

11 Nov '23

http://bugs.winehq.org/show_bug.cgi?id=16552 Summary: CreateIoCompletionPort fails in Chromium unit tests Product: Wine Version: 1.1.10 Platform: Other URL: http://chromium.org OS/Version: other Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_win.cc contains the code port_.Set(CreateIoCompletionPort(INVALID_HANDLE_VALUE, NULL, NULL, 1)); DCHECK(port_.IsValid()); ... HANDLE port = CreateIoCompletionPort(file_handle, port_, key, 1); DCHECK(port == port_.Get()); The DCHECK fires when running one of the Chromium unit tests: wine Debug/ui_tests.exe ... 001b:Call KERNEL32.CreateFileW(00ed7208 L"\\\\.\\pipe\\chrome.ChromeTestingInterface:8.1",c0000000,00000000,00000000,00000003,40110000,00000000) ret=010e0220 001b:Ret KERNEL32.CreateFileW() retval=000000c0 ret=010e0220 ... 0021:Call KERNEL32.CreateIoCompletionPort(ffffffff,00000000,00000000,00000001) ret=01a304b3 0021:Ret KERNEL32.CreateIoCompletionPort() retval=000000c8 ret=01a304b3 0021:Call KERNEL32.CreateIoCompletionPort(000000c0,000000c8,00ed5aa0,00000001) ret=01a30760 trace:ntdll:NtSetInformationFile (0xc0,0x7cdee318,0x7cdee320,0x00000008,0x0000001e) 0021:Ret KERNEL32.CreateIoCompletionPort() retval=00000000 ret=01a30760 0021:Call KERNEL32.OutputDebugStringA(00ed95a8 "[26:33:1249:FATAL:message_pump_win.cc(428)] Check failed: port == port_.Get(). \r\n") ret=019a7af3 I think it's failing in wineserver for some reason during NtSetInformationFile in set_completion_info. -- 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 52792] New: Error messages for invalid .exe files could be improved
by WineHQ Bugzilla 11 Nov '23

11 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=52792 Bug ID: 52792 Summary: Error messages for invalid .exe files could be improved Product: Wine Version: 7.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Trying to run a 0 byte .exe file under Wine will get you this: Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found. This doesn't look 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 2

[Bug 48004] New: winserver memory overflow
by WineHQ Bugzilla 11 Nov '23

11 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=48004 Bug ID: 48004 Summary: winserver memory overflow Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: heiko(a)stark-jena.de Distribution: --- with default and 'wineserver -d2 -f -p10' settings I run simulations with the software Opensim (https://opensim.stanford.edu/) and restart the Opensim one after the other with a script. This seems to cause a memory overflow (> 64 GB). Kill wineserver helps to fix the memory overflow. Is there a way to debug this? Best regards, Heiko -- 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 3

[Bug 52716] New: Sending key stroke (using [System.Windows.Forms.SendKeys]::SendWait) fails (seems to go into a loop?)
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=52716 Bug ID: 52716 Summary: Sending key stroke (using [System.Windows.Forms.SendKeys]::SendWait) fails (seems to go into a loop?) Product: Wine Version: 7.4 Hardware: x86-64 URL: https://github.com/PowerShell/PowerShell/releases/down load/v7.0.3/PowerShell-7.0.3-win-x64.msi OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Created attachment 72077 --> https://bugs.winehq.org/attachment.cgi?id=72077 ps script Hi, I have a powershell script where I need to send a keystroke to a program. I found code snippet on the internet and made little script that I tested in windows (using powershell core) and it works. It sends ctrp^p to notepad, and that opens the printer-dialog correctly on windows. On wine however it doesn`t work, cpu-usage goes up so it seems to get into loop(???) Script (also see attachment): ################################################################### Start-Process "notepad.exe" Sleep 3 $WindowHandle = Get-Process | Where-Object { $_.MainWindowTitle -Match "Notepad" } | Select-Object -ExpandProperty MainWindowHandle [void][System.Reflection.Assembly]::LoadWithPartialName('System.Windows.Forms') [System.Windows.Forms.SendKeys]::SendWait("^{p}") ##################################################################### Steps to reproduce: 1. winetricks -q dotnet48 2. wget https://github.com/PowerShell/PowerShell/releases/download/v7.0.3/PowerShel… 3. wine PowerShell-7.0.3-win-x64.msi 4. Save the script from attachment as a.ps1 in current folder 5. wine pwsh -file ./a.ps1 Notepad opens but nothing really happens and cpu-usage goes up -- 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 53213] New: d3d11:d3d11 - test_texture() fails in the TestBot VMs
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53213 Bug ID: 53213 Summary: d3d11:d3d11 - test_texture() fails in the TestBot VMs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 - test_texture() fails in the TestBot VMs: d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff0000ff at (0, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ffff at (1, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ff00 at (2, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffff00 at (3, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff0000 at (0, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff00ff at (1, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff7f7f7f at (3, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (1, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (2, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 3). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 3). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 3). https://test.winehq.org/data/patterns.html#d3d11:d3d11 These failures don't happen on my box which has an Intel graphics card instead of QEmu's QXL graphics card. Note also that these failures still happen on my debian11 VM which has a single monitor instead of the TestBot VMs' multi-monitor setup. So this seems to be related to the VMs QXL GPU. Note that despite being systematic these failures could cause false positives (see bug 53212). -- 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 54780] New: UndertaleModTool display regression since wine-staging 8.4
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54780 Bug ID: 54780 Summary: UndertaleModTool display regression since wine-staging 8.4 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janbidler00(a)protonmail.com Distribution: --- Created attachment 74277 --> https://bugs.winehq.org/attachment.cgi?id=74277 Display bug Starting from wine-staging 5.4 UndertaleModTool has corrupted display at boot. This did not happen on wine-staging 5.3 and earlier. The corrupted display can be fixed temporarily by clicking on any item in the Menubar (i.e. "File"). Happens both on a clean prefix and when upgrading. Issue is specific to wine-staging; wine-development has crashes going back all the way to wine-7.0 if not earlier and I didn't test it with wine-stable. Attached is an image of the display bug. The UndertaleModTool version can be found here (I used the asset "UndertaleModTool_v0.5.0.0.zip"): https://github.com/krzys-h/UndertaleModTool/releases/tag/0.5.0.0 Using Arch Linux. The wine-staging were gotten from here: https://archive.archlinux.org/packages/w/wine-staging/ -- 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 54519] New: d3d9:visual - test_mipmap_upload() fails on AMD and Nvidia GPUs
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54519 Bug ID: 54519 Summary: d3d9:visual - test_mipmap_upload() fails on AMD and Nvidia GPUs Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_mipmap_upload() fails on AMD and Nvidia GPUs. This impacts three VMs: fgtb-w10pro64_rx550 (AMD RX550): visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color 0x00000000. visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color 0x00000000. w11pro64_amd (AMD RX660): visual.c:404: Test failed: pool 0x2: level 0: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 1: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 2: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 3: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 4: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color 0x00ff0000. visual.c:404: Test failed: pool 0x2: level 5: Got hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color 0x00ff0000. w11pro64_nv (NVIDIA RTX3050): visual.c:195: pool 0x2: level 0: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color 0x00adbeef. visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color 0x00000000. visual.c:195: pool 0x2: level 2: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color 0x00adbeef. visual.c:195: pool 0x2: level 3: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color 0x00adbeef. visual.c:195: pool 0x2: level 4: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color 0x00adbeef. visual.c:195: pool 0x2: level 5: Can't create an offscreen plain surface to read the render target data, hr 0x80004005. visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color 0x00adbeef. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures all started on 2023-01-06 and a bisect shows that, on all three machines, they started with the commit below: commit 2954d3e4a23025657740fb178ddbe110890c0cc8 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Tue Dec 20 17:43:39 2022 -0600 d3d9/tests: Test uploading the whole mipmap chain in one map. Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> -- 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 3

[Bug 54399] New: d3d11:d3d11 - test_vertex_formats() fails on Windows 11 + AMD
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=54399 Bug ID: 54399 Summary: d3d11:d3d11 - test_vertex_formats() fails on Windows 11 + AMD Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d11:d3d11 - test_vertex_formats() fails on Windows 11 + AMD: d3d11.c:34906: Test failed: Format 0x58: Got {3.96078438e-001, 2.62745112e-001, 1.29411772e-001, 1.42236653e-019}, expected {3.96078438e-001, 2.62745112e-001, 1.29411772e-001, 1.00000000e+000} at (0, 0), sub-resource 0. See w11pro64-amd in https://test.winehq.org/data/patterns.html#d3d11:d3d11 The failures started on 2023-01-24, that is on the date the test was added by this commit: commit dc19f5c517af5d04bebb4f26bd79220b02f1ba64 Author: Zebediah Figura <zfigura(a)codeweavers.com> AuthorDate: Wed Jan 11 19:25:11 2023 -0600 d3d11/tests: Add a basic test for vertex formats. -- 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 3

[Bug 55316] New: d3d10core:d3d10core fails systematically on w11pro64-amd
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=55316 Bug ID: 55316 Summary: d3d10core:d3d10core fails systematically on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d10core:d3d10core fails systematically on w11pro64-amd: test_pipeline_statistics_query(): d3d10core.c:4922: Test failed: Got unexpected GSInvocations count: 2. d3d10core.c:4941: Test failed: Got unexpected GSInvocations count: 2. test_sample_c_lz(): d3d10core.c:8553: Test failed: Got 1.00000000e+000, expected 0.00000000e+000 at (100, 100), sub-resource 0. d3d10core.c:8553: Test failed: Got 1.00000000e+000, expected 0.00000000e+000 at (100, 100), sub-resource 0. See https://test.winehq.org/data/patterns.html#d3d10core:d3d10core These failures have been happening forever and are specific to the Windows 11 + AMD RX6600 configuration. In particular they never happened on fgtbw10pro64_rx550 (Windows 10 + AMD RX550). Also, except for 2023-05-10 to 2023-05-12 (3 days) they are present in all nightlies. -- 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 3

[Bug 53218] New: d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53218 Bug ID: 53218 Summary: d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs: d3d10core.c:13215: Test failed: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d10core.c:13215: Test failed: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d10core.c:13215: Test failed: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d10core.c:13215: Test failed: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. https://test.winehq.org/data/patterns.html#d3d10core:d3d10core These failures: * Don't happen on Debian 11 + Intel / KDE * Happen on Debian 11 + QXL + single-monitor * Happen on Debian 11 + QXL + multi-monitor * Happen on Debian Testing + QXL + multi-monitor (it actually has a couple extra) So they are probably related to QXL. Note that despite being systematic these failures could cause false positives due to the test multi-threading (see bug 53212). -- 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 53217] New: d3d11:d3d11 - test_cube_maps() crashes in Wine
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53217 Bug ID: 53217 Summary: d3d11:d3d11 - test_cube_maps() crashes in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 - test_cube_maps() crashes in Wine: $ WINETEST_REPORT_SUCCESS=1 WINETEST_NO_MT_D3D=1 ./wine dlls/d3d11/tests/d3d11_test.exe d3d11 Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x70baff74). [...] 0614:err:d3d:wined3d_debug_callback 00165DA0: "GL_OUT_OF_MEMORY in glMapBufferRange(map failed)". 0614:err:d3d:wined3d_allocator_chunk_gl_map Failed to map chunk memory. 0614:err:d3d:wined3d_bo_gl_map Failed to map chunk. 0614:err:d3d:wined3d_context_gl_map_bo_address Failed to map bo. Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x70baff74). [...] Backtrace: =>0 0x70baff74 memset+0x24(dst=0x000000000, c=0, n=0x4b0000) [Z:\home\winetest\tools\testbot\var\wine\dlls\msvcrt\string.c:3150] in ucrtbase (0x020ef908) 1 0x715283e3 wined3d_texture_load_location+0x423(texture=0016C8C0, sub_resource_idx=0, context=0016D920, location=0x8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:853] in wined3d (0x020ef9a8) 2 0x715173ae surface_cpu_blt+0x9ee(dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_box=020EFB38, src_texture=00171550, src_sub_resource_idx=0, src_box=020EFB50, flags=0x20000000, fx=020EFB68, filter=WINED3D_TEXF_POINT) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:752] in wined3d (0x020efaf8) 3 0x71518ea2 cpu_blitter_blit+0xc2(blitter=0016E408, op=WINED3D_BLIT_OP_RAW_BLIT, context=0016D920, src_texture=00171550, src_sub_resource_idx=0, src_location=0x10, src_rect=020EFE10, dst_texture=0016C8C0, dst_sub_resource_idx=<is not available>, dst_location=0x8, dst_rect=020EFE20, color_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1328] in wined3d (0x020efb98) 4 0x715368a2 ffp_blitter_blit+0xa2(blitter=0016E420, op=WINED3D_BLIT_OP_RAW_BLIT, context=0016D920, src_texture=00171550, src_sub_resource_idx=0, src_location=0x10, src_rect=020EFE10, dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_location=0x8, dst_rect=020EFE20, colour_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:6213] in wined3d (0x020efc58) 5 0x714dc91d glsl_blitter_blit+0x1ad(blitter=0016E438, op=WINED3D_BLIT_OP_RAW_BLIT, context=0016D920, src_texture=00171550, src_sub_resource_idx=0, src_location=0x10, src_rect=020EFE10, dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_location=0x8, dst_rect=020EFE20, colour_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\glsl_shader.c:13270] in wined3d (0x020efd78) 6 0x7151a181 texture2d_blt+0x3c1(dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_box=013EFAC4, src_texture=00171550, src_sub_resource_idx=0, src_box=013EFAE4, flags=0x20000000, fx=013EFB00, filter=WINED3D_TEXF_POINT) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1639] in wined3d (0x020efe48) 7 0x7149b07d wined3d_cs_exec_blt_sub_resource+0xcd(cs=013E0020, data=013EFAB8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:2579] in wined3d (0x020efec8) 8 0x7149cb2b wined3d_cs_command_unlock(queue=<internal error>, cs=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3310] in wined3d (0x020eff28) 9 0x7149cb2b wined3d_cs_execute_next+0x53(queue=<internal error>, cs=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3309] in wined3d (0x020eff28) 10 0x7149cb2b wined3d_cs_run+0x11b(ctx=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3375] in wined3d (0x020eff28) 11 0x7b62a170 in kernel32 (+0x2a170) (0x020eff48) 12 0x7bc5a937 in ntdll (+0x5a937) (0x020eff5c) 13 0x7bc5aff0 RtlCreateUserThread(entry=7149CA10, arg=013E0020) [Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:261] in ntdll (0x020effec) 0x70baff74 memset+0x24 [Z:\home\winetest\tools\testbot\var\wine\dlls\msvcrt\string.c:3150] in ucrtbase: movl %eax,0x0(%ebx) 3150 *(unaligned_ui64 *)(d + 0) = v; https://test.winehq.org/data/patterns.html#d3d11:d3d11 The crash happens with sub_resource_idx = 30. This impacts Debian 11 + QXL (the TestBot VMs), Intel (fg-deb64) and AMD RX460 (cw-rx460)... but only for 32-bit builds. -- 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 53522] New: Need for Speed III: joystick doesn't work after evdev removal
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=53522 Bug ID: 53522 Summary: Need for Speed III: joystick doesn't work after evdev removal Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: DirtY.iCE.hu(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: adfee25b45af8160848f94fdb24279d63d5f91f4 Distribution: Gentoo Created attachment 72888 --> https://bugs.winehq.org/attachment.cgi?id=72888 WINEDEBUG=+dinput, ds4 usb, overriden, nfs3 demo with git master wine I decided to try NFS3 after some time and realized that joystick no longer works with newer releases. Git bisect lead me to commit adfee25b45af8160848f94fdb24279d63d5f91f4, where the evdev and js backends were removed. With the new backend, in NFS3 deadzone calibration screen, all axes are at constant 0, and it doesn't respond to any keypress either. I've tried it with DualShock 4 (both usb and bt), DS3 (only usb), and some noname cheap controller, the same results. Interestingly, in joy.cpl the joysticks do work, I've tried to click on override to move the controller from the xinput to the non-xinput list, but no change. I also have no force-feedback support with the new backend. Tested it with the retail version of nfs3 and also with this patch, the results are the same: https://veg.by/en/projects/nfs3/ Also tested it with the demo version and the latest git (bfc73b0b80a1da2b137b5da4a2fcf530ee3a9d7d), same results. 1. Download demo from here: https://archive.org/details/nfs3_demo 2. Create a new 32-bit wine prefix (I've only compiled a 32-bit wine) 3. In winecfg, set windows compatibility to 98 (otherwise the install refuses to start), go to drives and add a (fake) cdrom device (otherwise setup refuses to start), and probably you should set a virtual desktop (the game likes to mess with your resolution) 4. Run setup.exe (it will throw a registry error but still installs the game) 5. Start the game with taskset: `taskset -c 0 path/to/wine nfs3demo -d3d0` (the game crashes/freezes if run on multicore cpu) 6. After the race countdown, press esc, controls, and try to bind some keys or click on dead zone to see axes values. I'm attaching a log with WINEDEBUG=+dinput and overridden joystick on joy.cpl. -- 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 49988] New: NosTale (and probably some other games) doesn't handle mouse clicks correctly
by WineHQ Bugzilla 10 Nov '23

10 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=49988 Bug ID: 49988 Summary: NosTale (and probably some other games) doesn't handle mouse clicks correctly Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: theszczepancio(a)gmail.com Distribution: --- Created attachment 68390 --> https://bugs.winehq.org/attachment.cgi?id=68390 Wine-staging 5.19 log Releated issues: https://bugs.winehq.org/show_bug.cgi?id=42999 https://bugs.winehq.org/show_bug.cgi?id=21739 Some info: Tested the issue with wine and wine-staging. Bug persists in 5.17, 5.18, 5.19 versions of wine. I have installed Arch Linux on r5 3600/rx5700 XT. I use D9VK (newest) for improvements of performance. Installing dinput8 is not fixing anything. I use Sway/wlroots on wayland, also I own newest kernel. Game works as should on steam proton with same version of D9VK. OpenGL backend works fine. Wine log in attachement. -- 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 14

[Bug 52444] New: Regression prevent eclipse from hitting breakpoints
by WineHQ Bugzilla 09 Nov '23

09 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=52444 Bug ID: 52444 Summary: Regression prevent eclipse from hitting breakpoints Product: Wine Version: 7.0-rc6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- I usually use eclipse with normal gdb for debugging. For that I compile without mingw, since it doesn't find the symbols when using real dlls. Since a while this is broken, and eclipse doesn't hit any breakpoints anymore. Bisected to commit 28fe84da45bea7de56539b50eac8ebcec54342de Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Mar 24 10:53:53 2021 +0100 ntdll: Load the main image from the Unix side. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 47848] New: Graphical glitches in "The suffering" game
by WineHQ Bugzilla 07 Nov '23

07 Nov '23

https://bugs.winehq.org/show_bug.cgi?id=47848 Bug ID: 47848 Summary: Graphical glitches in "The suffering" game Product: Wine Version: 4.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: inferrna(a)gmail.com Distribution: --- Created attachment 65353 --> https://bugs.winehq.org/attachment.cgi?id=65353 wine 1.5.17, good My system is Ubuntu 18.04.2 RX560 on Mesa 19.08 Last good wine version for this game is 1.5.17. Starting from 1.5.18 3D not shown, just HUD over black screen. But in some of later versions (somewhere between 1.7 and 2.0) bug was kind of half-fixed, at least starting from 2.0 3D is not all black, bus only some planes - floor, for example. Unfortunately I can't test versions between 1.7 and 2.0 because it this versions game just not fails to start with "X Error of failed request: BadWindow (invalid Window parameter)". -- 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 6

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 August 2023