wine-bugs

wine-bugs@winehq.org

1 participants
159103 discussions

[Bug 58709] New: upgrade to 10.15 results in garbled fullscreen in Limelight Lemonade Jam
by WineHQ Bugzilla 17 Sep '25

17 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58709 Bug ID: 58709 Summary: upgrade to 10.15 results in garbled fullscreen in Limelight Lemonade Jam Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pernegger(a)gmail.com Distribution: --- Created attachment 79308 --> http://bugs.winehq.org/attachment.cgi?id=79308 terminal output for 10.12–10.15 [Ubuntu 22.04, WINE packages from winehq.org repo] I've been playing the trial version of Limelight Lemonade Jam, which is available for free from https://sample9.dmm.co.jp/digital/pcgame/yuzu_0012/yuzu_0012t.zip, using WINE 10.12. No issues. Warning! The full game is NSFW, it's possible the trial has NSFW content as well; but if so, it doesn't come up for quite a while. WINE got upgraded to 10.15 just now, and the game doesn't launch correctly any more, the display is messed up, see screenshot. So I tested 10.12–10.15, each run with a fresh prefix, and it's reproducible: - 10.12: OK - 10.13: OK - 10.14: OK - 10.15: BROKEN Full disclosure, I've set the game to fullscreen and enabled the suspend/resume function, i.e. it'll bypass the main menu on launch and resume the game directly. Judging by the sound, the game loads fine even on 10.15, AFAICT it still reacts to keyboard input correctly, it's just the display that's messed up. It's likely that this affects other games using the KiriKiri engine as well. -- 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 58704] New: io_uring support for Wine
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58704 Bug ID: 58704 Summary: io_uring support for Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: k.kahurani(a)gmail.com Distribution: --- This issue mostly relates to the server(for filesystem operations), it seems like the networking implementation could be done outside the server. Just throwing this out there, it's highly unlikely I will work on it for various reasons. Wine still doesn't have io_uring support though, quite a few projects have already implemented io_uring support. Wine would also do with any performance benefits. io_uring is at least promoted as performance oriented, this makes it very interesting. io_uring offers performance benefits in multiple fronts. -> The first and probably the simplest is where operations on file might not have to make calls to 'fget'; typically when an operation is executed on files in Linux, it will involve some call to 'fget' one way or the other. With io_uring, it's possible to register files so that this 'fget' call is avoided. I am not sure how much performance benefit that could achieve. But, still an optimization nonetheless. Similarly, you could register buffers for opcodes(which translate to syscalls) so they're validated, mapped and so on so forth beforehand. When the actual operations/syscall are being executed, this boilerplate is not called. That is also an optimization. -> io_uring allows submitting a batch of syscalls(opcode operations) via one single syscall. This is an optimization, because, of course, without io_uring, you'd have to make multiple syscalls to achieve the same. However, it only seems like this optimization would only be applicable when making very many syscalls and making them very fast otherwise when making singular syscalls, they have to wait until the batch is full and hence would introduce some latency in low throughput situations. -> There might be other optimizations that I have not considered. What interests me most, though, is the syscall/request polling feature which allows applications to submit syscalls(opcode) via zero syscalls. io_uring sets up a kernel thread which polls the io ring and hence when submissions are made, the thread will discover them without any syscalls been made. This is very interesting and would be a straightforward mega-optimization were it not for that fact that the created kernel thread does pin a CPU. Would this work well with other work that's competing for CPU? It's consequently not very clear whether this would be an improvement to Wine, which makes syscalls alongside and in the midst of doing other heavy work. Any thoughts? -- 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 58706] New: Blood Fresh Supply / Doom 64 (KEX engine games) fail to start when OpenGl API is selected (EGL backend)
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58706 Bug ID: 58706 Summary: Blood Fresh Supply / Doom 64 (KEX engine games) fail to start when OpenGl API is selected (EGL backend) Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Distribution: --- Those games using the Kex Engine that support the Opengl renderer API fail to start when the new experimental EGL opengl backend is used. Such games are: Blood - Fresh Supply Doom 64 System Shock: Enhanced Edition The error message that is shown on start: kexPlatformApp::InitVideo: Failed to create window (No matching GL pixel format available). Other available renderers in those games (Vulkan and D3d11) work properly with the new EGL backend. wine-10.15-28-g7d26649f637 NVIDIA 580.82.09 X.Org X Server 1.21.1.18 -- 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 0

[Bug 58534] New: Grand Theft Auto: Vice City intros play with a black screen
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58534 Bug ID: 58534 Summary: Grand Theft Auto: Vice City intros play with a black screen Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: e5e2fd0a5209b0d07233d294e0ace5f1e41dfed5 Distribution: --- State of df00a5c097cd9cb292952f5307ee96d96fbc58b4 works good. -- 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 49195] New: Multiple 4k demoscene OpenGL demos crash on startup (failure to lookup atom 0xC019 'static' from global atom tables)
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=49195 Bug ID: 49195 Summary: Multiple 4k demoscene OpenGL demos crash on startup (failure to lookup atom 0xC019 'static' from global atom tables) Product: Wine Version: 5.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, extracted from bug 48898 My comment: https://bugs.winehq.org/show_bug.cgi?id=48898#c12 --- quote --- To me it looks like bug 18490 ("Multiple games fail to set pixel format on D3D device context created on desktop window (Empire: Total War, Napoleon: Total War, Utopia City)") but for GL device context on the desktop window. According to online information it's not allowed to do any rendering using this context but enough to call functions like glGetString() etc. Maybe some of the Wine graphics folks could weigh in with an opinion if this limitation is already known / tracked in a bug? --- quote --- Henri's answer: https://bugs.winehq.org/show_bug.cgi?id=48898#c13 --- quote --- I'm not aware of an existing bug report for this issue, no. It does strike me as similar to bug 36506 though, and it would not particularly surprise me if wglGetProcAddress() is supposed to return results consistent with GL_EXTENSIONS/GL_VERSION here, even without a current GL context. I seem to recall having established in the context of bug 18490 that creating a GL context (or more specifically, setting a pixel format) on the desktop window is indeed supposed to fail. In any case, this seems like of of those bugs that would benefit from tests to establish what's supposed to happen. --- quote --- Turns out this was a side-effect of an earlier problem. It was not supposed to be GetDC(NULL) (Desktop window). --- snip --- $ WINEDEBUG=+seh,+relay,+server,+class,+win,+msg wine ./End\ of\ time\ 720p.exe >>log.txt 2>&1 ... 0024:Call user32.ChangeDisplaySettingsA(00421288,00000004) ret=004200da ... 0024: get_desktop_window( force=0 ) 0024: get_desktop_window() = 0 { top_window=00010020, msg_window=00010026 } ... 0024:Ret user32.ChangeDisplaySettingsA() retval=00000000 ret=004200da 0024:Call KERNEL32.CreateThread(00000000,00000000,004201ca,004304e8,00000000,00000000) ret=004200ee ... 0024:Ret KERNEL32.CreateThread() retval=00000080 ret=004200ee 00bc: *fd* 17 <- 38 00bc: init_thread( unix_pid=3683, unix_tid=3729, debug_level=1, teb=7ffd4000, entry=004201ca, reply_fd=15, wait_fd=17, cpu=x86 ) 0024:Call user32.CreateWindowExA(00000000,0000c019,00000000,91000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000) ret=004200f4 0024:trace:win:WIN_CreateWindowEx (null) #c019 ex=00000000 style=91000000 0,0 0x0 parent=(nil) menu=(nil) inst=(nil) params=(nil) 00bc: init_thread() = 0 { pid=0020, tid=00bc, server_start=1d62d3b280579be (-2.9701360), info_size=0, version=603, all_cpus=00000003, suspend=0 } 0024:trace:win:dump_window_styles style: WS_POPUP WS_VISIBLE WS_MAXIMIZE 0024:trace:win:dump_window_styles exstyle: ... 00bc:Starting thread proc 0x4201ca (arg=0x4304e8) ... 0024: create_window( parent=00010020, owner=00000000, atom=c019, instance=00000000, dpi=96, awareness=2, class=L"" ) 0024: create_window() = INVALID_HANDLE { handle=00000000, parent=00000000, owner=00000000, extra=0, class_ptr=00000000, dpi=0, awareness=0 } 0024:warn:win:create_window_handle error 6 creating window 0024:trace:class:GetClassInfoExW (nil) #c019 0x1518f9e0 0024:trace:class:CLASS_FindClass #c019 0x7e910000 -> not found 0024:Ret user32.CreateWindowExA() retval=00000000 ret=004200f4 --- snip --- The failing window creation resulted in NULL handle which got passed to user32.GetDC(): --- snip --- 0024:Call user32.GetDC(00000000) ret=004200fb 0024:trace:win:GetDCEx hwnd 0x10020, hrgnClip (nil), flags 00000003 ... 0024: get_visible_region( window=00010020, flags=00000013 ) 0024: get_visible_region() = 0 { top_win=00010020, top_rect={-1920,0;-1919,1}, win_rect={0,0;3200,1080}, paint_flags=00000001, total_size=16, region={{-1920,0;1280,1080}} } 0024:Call winex11.drv.GetDC(00030039,00010020,00010020,1518fde0,1518fdf0,00000013) ret=7e97bd3e 0024:Ret winex11.drv.GetDC() retval=00000001 ret=7e97bd3e 0024:trace:win:GetDCEx (0x10020,(nil),0x13): returning 0x30039 (updated) 0024:Ret user32.GetDC() retval=00030039 ret=004200fb --- snip --- Well, the rest of the OpenGL story is known and the current behaviour makes sense. Back to the actual problem... The creation of the window which ought the be used for OpenGL context/rendering fails because atom 0xc019 can't be found/resolved. I should have looked more carefully at the trace log and the demo disassembly. --- snip --- ... 004200B6 | xor esi,esi | 004200B8 | push esi | 004200B9 | push esi | 004200BA | push esi | 004200BB | push esi | 004200BC | push esi | 004200BD | push esi | 004200BE | push esi | 004200BF | push esi | 004200C0 | push esi | 004200C1 | push 91000000 | 004200C6 | push esi | 004200C7 | push C019 | global atom! 004200CC | push esi | 004200CD | push 4 | 004200CF | push end of time 720p.421288 | 004200D4 | call dword ptr ds:[<&user32.ChangeDisplaySettingsA>] | 004200DA | push esi | 004200DB | push esi | 004200DC | push end of time 720p.4304E8 | 004200E1 | push end of time 720p.4201CA | 004200E6 | push esi | 004200E7 | push esi | 004200E8 | call dword ptr ds:[<&KERNEL32.CreateThread>] | 004200EE | call dword ptr ds:[<&user32.CreateWindowExA>] | fails 004200F4 | push eax | 004200F5 | call dword ptr ds:[<&user32.GetDC>] | 004200FB | mov edi,eax | 004200FD | mov dword ptr ds:[3AB08EC],eax | 00420102 | push esi | 00420103 | push edi | 00420104 | push esi | 00420105 | push end of time 720p.42125C | 0042010A | push edi | 0042010B | call dword ptr ds:[<&gdi32.ChoosePixelFormat>] | 00420111 | push eax | 00420112 | push edi | 00420113 | call dword ptr ds:[<&gdi32.SetPixelFormat>] | 00420119 | call dword ptr ds:[<&opengl32.wglCreateContext>] | 0042011F | push eax | 00420120 | push edi | 00420121 | call dword ptr ds:[<&opengl32.wglMakeCurrent>] | 00420127 | call dword ptr ds:[<&user32.ShowCursor>] | 0042012D | call end of time 720p.4202CC | --- snip --- The demoscene guys are crazy and fight for each saved byte ;-) Courtesy of: http://www.pouet.net/topic.php?which=9894 --- quote --- I was able to get 4 bytes off of a test 1k intro (Peach GLSL Shader of Japan) by replacing the "edit" string with 0xC018, making it 1006 bytes instead of 1010. Nice. ...and then I got it down to 1004 bytes, because now "test eax, eax" compressed better than "test ax, ax", which used to compress better sometime before this newest change. ;) This 1k intro business is crazy, you'd really need some kind of brute-force code masher that tries all possible combinations of code that perform the same thing. --- quote --- --- quote --- That´s mine since 2009 using DirectX9...someone told me using "static" instead of "edit" would be better back then in some other thread...was iq if i remember correctly. The ATOM for "static" is 0xC019 btw, but be warned: it added 7 bytes here in my first test, opposed to chopping off 4 bytes in case of "edit". --- quote --- --- quote --- Oh, shit...i did the test the wrong way around...meaning the ATOM actually chopped off 7 bytes in case of "static" vs. "0xC019" :/ :D Yay, thanks for the nice trick, man! :) --- quote --- Also relevant, shows dump of global and typical local atom tables: https://github.com/lungetech/ICAS/blob/master/logs/volatility/win32/output/… Wine source: https://source.winehq.org/git/wine.git/blob/9e26bc811656ad8eb901bffa5528b9c… --- snip --- 407 /*********************************************************************** 408 * CLASS_FindClass 409 * 410 * Return a pointer to the class. 411 */ 412 static CLASS *CLASS_FindClass( LPCWSTR name, HINSTANCE hinstance ) 413 { 414 static const WCHAR comctl32W[] = {'c','o','m','c','t','l','3','2','.','d','l','l',0}; 415 struct list *ptr; 416 ATOM atom = get_int_atom_value( name ); 417 418 GetDesktopWindow(); /* create the desktop window to trigger builtin class registration */ 419 420 if (!name) return NULL; 421 422 name = CLASS_GetVersionedName( name, NULL, NULL, TRUE ); 423 424 for (;;) 425 { 426 USER_Lock(); 427 428 LIST_FOR_EACH( ptr, &class_list ) 429 { 430 CLASS *class = LIST_ENTRY( ptr, CLASS, entry ); 431 if (atom) 432 { 433 if (class->atomName != atom) continue; 434 } 435 else 436 { 437 if (strcmpiW( class->name, name )) continue; 438 } 439 if (!class->local || class->hInstance == hinstance) 440 { 441 TRACE("%s %p -> %p\n", debugstr_w(name), hinstance, class); 442 return class; 443 } 444 } 445 USER_Unlock(); 446 447 if (atom) break; 448 if (!is_comctl32_class( name )) break; 449 if (GetModuleHandleW( comctl32W )) break; 450 if (!LoadLibraryW( comctl32W )) break; 451 TRACE( "%s retrying after loading comctl32\n", debugstr_w(name) ); 452 } 453 454 TRACE("%s %p -> not found\n", debugstr_w(name), hinstance); 455 return NULL; 456 } --- snip --- https://source.winehq.org/git/wine.git/blob/9e26bc811656ad8eb901bffa5528b9c… $ sha1sum atz-end_of_time.zip 3a4ce3fd92e2fdd1a4533ee67d4809d3f2184f6b atz-end_of_time.zip $ du -sh atz-end_of_time.zip 3.3M atz-end_of_time.zip $ wine --version wine-5.8-173-g9e26bc8116 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.

1 8

[Bug 58582] New: Rainmeter 4.5.23: crashes on X11 after refreshing default skin Clock.ini
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58582 Bug ID: 58582 Summary: Rainmeter 4.5.23: crashes on X11 after refreshing default skin Clock.ini Product: Wine Version: unspecified Hardware: x86-64 URL: https://github.com/rainmeter/rainmeter/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: castelei(a)yahoo.com Regression SHA1: 980a2e3c65bee1422adbe06fead768669835e3e1 Distribution: --- Created attachment 79106 --> http://bugs.winehq.org/attachment.cgi?id=79106 WINEDEBUG=+synchronous,+seh Rainmeter 4.5.23 Reproduction: 1) Click on the Rainmeter icon on the system tray to open the 'Manage Rainmeter' window. 2) Click on the 'Active skins' drop-down list and select illustro\Clock\Clock.ini 3) Click the 'Refresh' button to the right. This X11 error prints as the application crashes if run without +synchronous: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 139 (RENDER) Minor opcode of failed request: 4 (RenderCreatePicture) Serial number of failed request: 15285 Current serial number in output stream: 15292 Found this regression on a merged patch newer than 10.12 (the newest development release at this time) while working on an unrelated bug. -- 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

[Bug 58698] New: Application goes into an infinite loop under new wow64 but works okay under old wow64
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58698 Bug ID: 58698 Summary: Application goes into an infinite loop under new wow64 but works okay under old wow64 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: dkk089(a)gmail.com Distribution: --- Created attachment 79297 --> http://bugs.winehq.org/attachment.cgi?id=79297 WINEDEBUG=+virtual under "new wow64" Application goes into an infinite loop under new wow64 but works okay under old wow64 I have an application that enters an infinite loop under "new wow64" but works okay with "old wow64". Running under actual 64-bit Windows is okay too. The problem seems to be caused by application logic which calls VirtualAlloc() repeatedly in order to (presumably) find out the maximum available amount of memory that the application is able to allocate. The first hint that this might be somehow related to memory were the error messages reported when running under "old wow64" : 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x74010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 74000000 Running the application with WINEDEBUG=+virtual showed the NtAllocateVirtualMemory calls that are made by the application, starting with a size of 0x7fffffff, exploring a number of different sizes, and then eventually settling on 0x701f0000 : 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 7fffffff 2000 00000004 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 3fffffff 2000 00000004 01a0:trace:virtual:map_view got mem in reserved area 0x11050000-0x51050000 01a0:trace:virtual:dump_view View: 0x11050000 - 0x5104ffff (valloc) 01a0:trace:virtual:dump_view 0x11050000 - 0x5104ffff --rw- 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff 0x11050000 00000000 8000 -- snip : successful calls after that with sizes 0x5fffffff , 0x6fffffff -- 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 77ffffff 2000 00000004 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 -- snip : goes on to try sizes starting with 0x70 ... -- 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 701f0001 2000 00000004 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x70201000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 701f1000 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 701f0000 2000 00000004 01a0:trace:virtual:map_view got mem with anon mmap 0x80000000-0xf01f0000 01a0:trace:virtual:dump_view View: 0x80000000 - 0xf01effff (valloc) 01a0:trace:virtual:dump_view 0x80000000 - 0xf01effff --rw- 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 The application makes the same calls under "new wow64", but since none of those calls ever fail, it seems to get confused, reaches size=0, and then gets stuck on that size : 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 7fffffff 2000 00000004 016c:trace:virtual:map_view got mem with map_free_area 0x7fff0000-0xffff0000 016c:trace:virtual:dump_view View: 0x7fff0000 - 0xfffeffff (valloc) 016c:trace:virtual:dump_view 0x7fff0000 - 0xfffeffff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x7fff0000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 3fffffff 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x11050000-0x51050000 016c:trace:virtual:dump_view View: 0x11050000 - 0x5104ffff (valloc) 016c:trace:virtual:dump_view 0x11050000 - 0x5104ffff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x11050000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 1fffffff 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x11050000-0x31050000 016c:trace:virtual:dump_view View: 0x11050000 - 0x3104ffff (valloc) 016c:trace:virtual:dump_view 0x11050000 - 0x3104ffff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x11050000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 0fffffff 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x11050000-0x21050000 016c:trace:virtual:dump_view View: 0x11050000 - 0x2104ffff (valloc) 016c:trace:virtual:dump_view 0x11050000 - 0x2104ffff --rw- -- snip : repeated calls with size right-shifted by 1 -- 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 0000000f 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000007 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000003 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000001 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 It then loops on the call with size=0 indefinitely and keeps running until I kill the wineserver. Unfortunately, this is a proprietary legacy application so I can't share it, however I'll be more than glad to accept pointers on which debug channels to activate, any other further debugging steps, or changes to the code that might fix this. Thanks in advance. -- 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 57806] New: visual and response lags in Guitar Pro v8.1.3 (build 121)
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57806 Bug ID: 57806 Summary: visual and response lags in Guitar Pro v8.1.3 (build 121) Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: acidbong(a)tilde.club Distribution: --- Created attachment 78013 --> https://bugs.winehq.org/attachment.cgi?id=78013 Guitar Pro in Wine-9.20 I've been using Wine-staging for running Guitar Pro on Linux (Gentoo, then NixOS), and it's been smooth until 9.20 -> 9.22 update (https://github.com/NixOS/nixpkgs/pull/359908, nixpkgs maintainers skipped v9.21). Then visual lags (constant, as if the program runs at 5 FPS) started to happen. Welp, they aren't solely visual, responsiveness also suffers. Audio, however, doesn't lag and is still smooth. The lag is also present on Wine10. Regression also confirmed on Wine-development v9.22 and with a demo version of the program and on different PCs (first on an Intel-based laptop (Core i3-7100), then on an AMD-based one (AMD Ryzen 5 5500U)), both with integrated GPUs. Camera recording (not screen capture, because `simplescreenrecorder` (haven't tried other tools) for some reason reduced these lags): https://0x0.st/8KNw.mp4 Logs are attached below. -- 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 58700] New: Regression: Direct3D applications show a blank screen under wined3d in 10.15
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58700 Bug ID: 58700 Summary: Regression: Direct3D applications show a blank screen under wined3d in 10.15 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: im.tech.tac+wine(a)gmail.com Distribution: --- As of Wine-staging 10.15, all Direct3D applications only render a blank (often black) screen while still producing sound and reacting to inputs. This issue was not present in 10.14, downgrading to it fixes the problem. Multiple Unity games seem to have consistently produced this issue. Arch Linux, latest packages up to 2025/09/14. KDE Plasma 6 Wayland session. Both X11 and Wayland Wine backends seem affected. AMD A8-5500B with Radeon HD 7560D. No Vulkan support whatsoever. -- 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 9

[Bug 58703] New: Fedora 42: Suddenly getting checksum errors
by WineHQ Bugzilla 16 Sep '25

16 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58703 Bug ID: 58703 Summary: Fedora 42: Suddenly getting checksum errors Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: johnny.jy.ooi(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- Recently, while trying to do the standard "dnf upgrade", my system sees updates for wine-staging and winehq-staging, but upon triggering the upgrade, I get checksum errors Total size of inbound packages is 226 MiB. Need to download 226 MiB. After this operation, 6 MiB extra will be used (install 1 GiB, remove 1 GiB). [1/2] winehq-staging-1:10.15-1.1.x86_64 100% | 144.6 KiB/s | 75.0 KiB | 00m01s >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc [2/2] wine-staging-1:10.15-1.1.x86_64 0% | 3.3 MiB/s | 1.7 MiB | 00m01s >>> Not finished - interrupted by error: Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bd ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [2/2] Total 100% | 3.4 MiB/s | 1.8 MiB | 00m01s Failed to download packages Librepo error: Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfcbfea6(sha256) I've tried removing the winehq.repo, reimporting the repo key (https://dl.winehq.org/wine-builds/winehq.key), readding the repo according to the instructions, and doing "dnf clean" and it keep failing the checksum checks. I know there's been some issues with the repo in the past, do we have another similar issue? -- 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 0

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