wine-bugs September 2023

wine-bugs@winehq.org

1 participants
2292 discussions

[Bug 49195] New: Multiple 4k demoscene OpenGL demos crash on startup (failure to lookup atom 0xC019 'static' from global atom tables)
by WineHQ Bugzilla 12 Dec '23

12 Dec '23

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 7

[Bug 55548] New: kernel32:power - test_GetSystemPowerStatus() fails on macOS
by WineHQ Bugzilla 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55548 Bug ID: 55548 Summary: kernel32:power - test_GetSystemPowerStatus() fails on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:power - test_GetSystemPowerStatus() fails on macOS: power.c:34: Test failed: expected TRUE See https://test.winehq.org/data/patterns.html#kernel32:power The failure is systematic and only happens macOS (see Remi's rbernon-macos-* cloud test machines). It looks like the macOS implementation of fill_battery_state() fails, presumably because of permission issues. -- 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 47028] New: WinSCP hosts list missing indentation
by wine-bugs＠winehq.org 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=47028 Bug ID: 47028 Summary: WinSCP hosts list missing indentation Product: Wine Version: 4.6 Hardware: x86-64 URL: http://winscp.net/download/winscp577.zip OS: Mac OS X Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com CC: jr98(a)gmx.net Created attachment 64194 --> https://bugs.winehq.org/attachment.cgi?id=64194 terminal output, +message log, screenshots On windows there is space between the edge of the box and the icons. To reproduce, run WinSCP.exe and you can see the hosts list on the left. Attached is a zip containing terminal output, a +message log and screenshots for comparison. -- 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 6

[Bug 54397] New: Wine does not populate prefixes with 32-bit dlls
by WineHQ Bugzilla 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=54397 Bug ID: 54397 Summary: Wine does not populate prefixes with 32-bit dlls Product: Wine Version: 7.22 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: eralegrid(a)hotmail.com Starting from Wine 7.22, Wine doesn't copy any 32-bit files into new prefixes. For a 32-bit prefix, only system.reg/user.reg/user.reg and a bunch of empty directories are created. For a 64-bit prefix, things appear to be normal aside from $WINEPREFIX/drive_c/windows/syswow64 being empty. It seems this situation started with commit d45de318748639cfd1e80a976b39f5e19213990f. -- 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 13778] New: Date and Time display
by wine-bugs＠winehq.org 11 Dec '23

11 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=13778 Summary: Date and Time display Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: rx9tx(a)qrz.ru Created an attachment (id=13813) --> (http://bugs.winehq.org/attachment.cgi?id=13813) wine window The problem is that in a Windows application running in Wine the date and time displayed as digit like 39591.6425810185 instead of May-23-2008, 15:25, see pictures http://rx9tx.qrz.ru/wine.jpg and http://rx9tx.qrz.ru/windows.jpg . Same about the frequency value 0000000000028.012100 in mHz (28.0121 mhz) is shown like 298112000.0. I dont know what kind of database is used, but it has the .isd extension, also .isf, .ism, .isl files are present. Here's the excerption from the database with the data shown on the pics: http://rx9tx.qrz.ru/log.txt -- 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 25

[Bug 50338] New: Open/save dialog don't show current folder path.
by WineHQ Bugzilla 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=50338 Bug ID: 50338 Summary: Open/save dialog don't show current folder path. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: ltgustavsen(a)gmail.com Distribution: --- Created attachment 68924 --> https://bugs.winehq.org/attachment.cgi?id=68924 Screenshot from linux. Missing folder path. Hello The opening/save dialog in Picture Window 8 from dl-c.com doesn't work as expected. There is no way to see which folder I’m in. The green back arrows on the top don’t work when I open the default catalog. I have to start each time in the left sidebar and browse to the correct directory. If I do so, the arrows work. I have attached some screenshots. And a debug file. I have tested with wine-5.0.3 and wine-6.0-rc2 I have installed Picture Window this way winetricks vcrun2019 wine msiexec /i Picture\ Window\ Pro.msi -- 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 44016] New: Improve path handling in Open and Save dialogs
by wine-bugs＠winehq.org 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=44016 Bug ID: 44016 Summary: Improve path handling in Open and Save dialogs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- Current open and save dialogs have large usability issues. 1 When I paste a path of a folder into it to make it open that folder in itself it doesn't work and writes an error. 2 I also expect this dialog to accept the absolute path in linux rootfs. 3 I also expect it to show a drop-down menu as in Windows. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 11

[Bug 42645] New: File dialog usability
by wine-bugs＠winehq.org 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=42645 Bug ID: 42645 Summary: File dialog usability Product: Wine Version: 1.9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: freddi34(a)yahoo.de Distribution: --- When working with project files across different programs (e.g. Linux/OS X program and Windows program through Wine), users usually have to access the same locations and files. Quick file access and navigation is essential for productivity. If Wine's goal is not to be a bottom-of-the-drawer academic project, but actually useful, it must sufficiently integrate with the non-Windows desktop that its users are using. Example workflow: A 1. Native file manager (e.g. Nautilus) is opened at /home/username/folder1 2. User wants to open file1.ext from this folder in a Wine program through the file open dialog. B 1. User creates a file2.ext in a Wine program, opens the file save dialog and wants to save it in the same location (folder1). 2. File save dialog is opened at a path deep in the virtual C: drive (C:/Programs/Manufacturer/ProgramName/client/assets/.../...). The file save dialog's location may be controlled by the Windows application or where it was opened the last time. Wine's file open/save dialog has significantly worse usability than any GTK/KDE/OS X file dialog or even Windows' own. - It is more likely not opened where the user needs it (since working cross-system) - Navigation is only possible by one step up (green up arrow button) or by going multiple steps up towards the file system root (scrollable dropdown) and then navigating step by step down in the native system's file tree. - Double-click is cumbersome and leads repeatedly to accidental renamings or wrong selections. Wine's open/save dialogs should allow faster changing between commonly used locations. This should be supported through: - editable address (would allow to paste a complete path and press enter) - droppable for native paths (drag&drop a folder from a native file manager, this is commonly supported in e.g. GTK) - persistent list of recently openend locations in this WINEPREFIX While these are platform-agnostic, more comfort can be achieved by further integrating with the desktop (Gnome/KDE/OS X): - integrate with the desktop's bookmarks through Free Desktop Standard - integrate with the desktop's recent locations - (native file dialogs) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 4

[Bug 35062] New: FarCry3 : graphical glitches
by wine-bugs＠winehq.org 11 Dec '23

11 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=35062 Bug #: 35062 Summary: FarCry3 : graphical glitches Product: Wine Version: 1.7.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: berillions(a)gmail.com Classification: Unclassified Created attachment 46762 --> http://bugs.winehq.org/attachment.cgi?id=46762 Graphical glitches on see Hi, There is a graphical bug when i play at FarCry3. this bug appears only when you look the sea. As you can see in the screenshot, it seems that the map is drawn in the sea. I think it's not a problem about the sun/moon light reflections on the sea, they're correctly drawn (not viewable in the screenshot) Thanks, Max -- 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 22

[Bug 45166] New: Mafia III has messed and very dark graphics
by wine-bugs＠winehq.org 10 Dec '23

10 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=45166 Bug ID: 45166 Summary: Mafia III has messed and very dark graphics Product: Wine Version: 3.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: mo78(a)abv.bg Distribution: --- Created attachment 61366 --> https://bugs.winehq.org/attachment.cgi?id=61366 Wine log Mafia III has messed and very dark graphics and it cannot be played. I can't get apitrace for the game doesn't start with it. I try it on Nvidia GTX 1080 Ti and I tried a a couple of versions past 11-12 months, all with the same effect. -- 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 25

Jump to page:

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