February 2023 - Wine-bugs - list.winehq.org

[Bug 54453] New: Wow64 UI Drawing Black Screen When WNDCLASSEXW::hbrBackground set to NULL
by WineHQ Bugzilla 10 Feb '23

10 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54453 Bug ID: 54453 Summary: Wow64 UI Drawing Black Screen When WNDCLASSEXW::hbrBackground set to NULL Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: fanwj(a)mail.ustc.edu.cn Distribution: --- If set WNDCLASSEXW::hbrBackground to 0 (Default hbrBackground), Black Screen Occur For Example, The Simple Window: #include <Windows.h> #define MAX_LOADSTRING 100 // Global Variables: HINSTANCE hInst; // current instance WCHAR szTitle[MAX_LOADSTRING] = L"HELLO"; // The title bar text WCHAR szWindowClass[MAX_LOADSTRING] = L"HELLO"; // the main window class name // Forward declarations of functions included in this code module: ATOM MyRegisterClass(HINSTANCE hInstance); BOOL InitInstance(HINSTANCE, int); LRESULT CALLBACK WndProc(HWND, UINT, WPARAM, LPARAM); int main(void) { HINSTANCE hInstance = GetModuleHandle(NULL); int nCmdShow = SW_SHOW; // TODO: Place code here. // Initialize global strings MyRegisterClass(hInstance); // Perform application initialization: if (!InitInstance(hInstance, nCmdShow)) { return FALSE; } MSG msg; // Main message loop: while (GetMessage(&msg, nullptr, 0, 0)) { if (!TranslateAccelerator(msg.hwnd, NULL, &msg)) { TranslateMessage(&msg); DispatchMessage(&msg); } } return (int)msg.wParam; } // // FUNCTION: MyRegisterClass() // // PURPOSE: Registers the window class. // ATOM MyRegisterClass(HINSTANCE hInstance) { WNDCLASSEXW wcex; wcex.cbSize = sizeof(WNDCLASSEX); wcex.style = CS_HREDRAW | CS_VREDRAW; wcex.lpfnWndProc = WndProc; wcex.cbClsExtra = 0; wcex.cbWndExtra = 0; wcex.hInstance = hInstance; wcex.hIcon = NULL; wcex.hCursor = NULL; wcex.hbrBackground = (HBRUSH)NULL; // Black Screen Occur! wcex.lpszMenuName = NULL; wcex.lpszClassName = szWindowClass; wcex.hIconSm = NULL; return RegisterClassExW(&wcex); } // // FUNCTION: InitInstance(HINSTANCE, int) // // PURPOSE: Saves instance handle and creates main window // // COMMENTS: // // In this function, we save the instance handle in a global variable and // create and display the main program window. // BOOL InitInstance(HINSTANCE hInstance, int nCmdShow) { hInst = hInstance; // Store instance handle in our global variable HWND hWnd = CreateWindowW(szWindowClass, szTitle, WS_OVERLAPPEDWINDOW, CW_USEDEFAULT, 0, CW_USEDEFAULT, 0, nullptr, nullptr, hInstance, nullptr); if (!hWnd) { return FALSE; } ShowWindow(hWnd, nCmdShow); UpdateWindow(hWnd); return TRUE; } LRESULT CALLBACK WndProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam) { switch (message) { case WM_COMMAND: { int wmId = LOWORD(wParam); // Parse the menu selections: switch (wmId) { default: return DefWindowProc(hWnd, message, wParam, lParam); } } break; case WM_DESTROY: PostQuitMessage(0); break; default: return DefWindowProc(hWnd, message, wParam, lParam); } return 0; } -- 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 1

[Bug 54131] New: Installing kindle windows app gets 'Wine c++ error' and hitting cancel does NOT invoke debugger
by WineHQ Bugzilla 09 Feb '23

09 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54131 Bug ID: 54131 Summary: Installing kindle windows app gets 'Wine c++ error' and hitting cancel does NOT invoke debugger Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stevedonato(a)gmail.com Distribution: --- Created attachment 73661 --> https://bugs.winehq.org/attachment.cgi?id=73661 Screen print of wine error message about C++ error Tried to install Kindle windows app and recieved 'wine c++ error' it said hit cancel button to enter debugger. I hit cancel button and wine simply ended and did NOT enter the debuger? using latest wine for linux mint 20.2 repository lptop has i7 intel processor and 32gb ram -- 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 38905] New: In dlls/mshtml/tests, "make test" failed when some Chinese fonts are used
by wine-bugs＠winehq.org 08 Feb '23

08 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=38905 Bug ID: 38905 Summary: In dlls/mshtml/tests, "make test" failed when some Chinese fonts are used Product: Wine Version: 1.7.47 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: litimetal(a)gmail.com Distribution: --- Created attachment 51840 --> https://bugs.winehq.org/attachment.cgi?id=51840 backtrace.txt 0. Copy some Chinese fonts from C:\windows\fonts in Windows XP to ~/.fonts[1] 1. fc-cache -fv 2. run "make test" in dlls/mshtml/tests 3. crashed [1]: The fonts I copied to Linux: 文鼎CS长宋体繁.TTF 文鼎粗行楷简.TTF 文鼎粗圆简.TTF 文鼎琥珀繁.TTF 文鼎特粗宋简.TTF 文鼎小标宋简.TTF 文鼎报宋简.TTF 文鼎粗黑繁.TTF 文鼎大标宋简.TTF 文鼎书宋繁.TTF 文鼎习字体.TTF 文鼎新艺体简.TTF 文鼎齿轮体.TTF 文鼎粗魏碑简.TTF 文鼎古印体繁.TTF 文鼎特粗黑简.TTF 文鼎细仿宋繁.TTF I don't know how to determine which font caused this problem -- 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 3

[Bug 53225] New: gameux:gamestatistics has a rare pair of failures on Windows 8
by WineHQ Bugzilla 08 Feb '23

08 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=53225 Bug ID: 53225 Summary: gameux:gamestatistics has a rare pair of failures on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gameux Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gameux:gamestatistics has a rare pair of failures on Windows 8: gamestatistics.c:59: Test failed: got 0x80004005 gamestatistics.c:201: statistics file path: L"C:\\Users\\winetest\\AppData\\Local\\Microsoft\\Windows\\GameExplorer\\GameStatistics\\{17A6558E-60BE-4078-B66F-9C3ADA2A32E6}\\{17A6558E-60BE-4078-B66F-9C3ADA2A32E6}.gamestats" gamestatistics.c:75: Test failed: got 0x80070057 https://test.winehq.org/data/patterns.html#gameux:gamestatistics Only one known instance on 2022-06-20 on w8adm so far. -- 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 53239] New: dpnet:client - test_enum_hosts() and test_enum_hosts_peer() fail randomly on Windows
by WineHQ Bugzilla 08 Feb '23

08 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=53239 Bug ID: 53239 Summary: dpnet:client - test_enum_hosts() and test_enum_hosts_peer() fail randomly on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dplay Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dpnet:client - test_enum_hosts() and test_enum_hosts_peer() fail randomly on Windows: client.c:323: Test failed: got 0x80004005 or client.c:753: Test failed: got 0x80004005 https://test.winehq.org/data/patterns.html#dpnet:client In both cases the API that fails is IDirectPlay8Client_CancelAsyncOperation() so this looks like a race condition. The failure rate (~4.4%) is low enough to cause false positives. Strangely enough all but one of the failures happened on w7u, w7pro64 and w10pro64 (21H1). That means none of the failures happened on Windows 10 1507 to 2009! -- 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 54459] New: Transparent windows aren't rendered properly + System Freezes
by WineHQ Bugzilla 07 Feb '23

07 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54459 Bug ID: 54459 Summary: Transparent windows aren't rendered properly + System Freezes Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lunarleafclover(a)outlook.com Distribution: --- When playing the "Unresponsive" Friday Night Funkin' mod, it messes with it's Windows a lot. It moves the windows a lot and has a transparent window to render the antagonist "Fatal Error." Similar to the untitled "No More Innocence" mod with its windows moving at the end of it's one-off song. Playing the Unresponsive mod whilst recording in OBS causes the System to hang quite a while when it's 4 additional windows get created alongside the actual game process, all of which render details as the antagonist with minor background characters. Not tested on Wayland but I'd imagine it'd be somewhat smoother. The video is too big to be linked as an attachment, so I put it in streamable instead. https://streamable.com/espjym -- 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 38673] New: valgrind shows uninitialized memory in dlls/kernel32/sync.c:ConnectNamedPipe()
by wine-bugs＠winehq.org 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=38673 Bug ID: 38673 Summary: valgrind shows uninitialized memory in dlls/kernel32/sync.c:ConnectNamedPipe() Product: Wine Version: 1.7.42 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Fedora ../../../tools/runtest -q -P wine -T ../../.. -M hlink.dll -p hlink_test.exe.so hlink && touch hlink.ok ==14126== Thread 3: ==14126== Syscall param writev(vector[...]) points to uninitialised byte(s) ==14126== at 0x4F7A0F4B: ??? (in /usr/lib/libc-2.21.so) ==14126== by 0x7BC7A9C5: send_request (server.c:228) ==14126== by 0x7BC7AB52: wine_server_call (server.c:309) ==14126== by 0x7BC7B8CD: server_select (server.c:607) ==14126== by 0x7BC85426: NtWaitForMultipleObjects (sync.c:976) ==14126== by 0x7BC85471: NtWaitForSingleObject (sync.c:985) ==14126== by 0x7BC45DFF: server_ioctl_file (file.c:1539) ==14126== by 0x7BC46565: NtFsControlFile (file.c:1786) ==14126== by 0x7B87406B: ConnectNamedPipe (sync.c:1615) ==14126== by 0x49255A5: listen_thread (rpc_transport.c:132) ==14126== by 0x7BC81BB7: ??? (signal_i386.c:2682) ==14126== by 0x7BC81BFE: call_thread_func (signal_i386.c:2741) ==14126== by 0x7BC81B95: ??? (signal_i386.c:2682) ==14126== by 0x7BC88D78: start_thread (thread.c:443) ==14126== by 0x4F88F37F: start_thread (in /usr/lib/libpthread-2.21.so) ==14126== by 0x4F7ABD4D: clone (in /usr/lib/libc-2.21.so) ==14126== Address 0x4cee5c4 is on thread 1's stack ==14126== Uninitialised value was created by a stack allocation ==14126== at 0x7B873FA5: ConnectNamedPipe (sync.c:1601) ==14126== also shows in ieframe/webbrowser, kernel32/pipe, -- 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 3

[Bug 9221] Force Feedback doesn't work but does after little source modification
by WineHQ Bugzilla 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #56 from groybe(a)gmail.com --- (In reply to Rémi Bernon from comment #51) > Sure, it's okay. I don't have the device so it's going to be hard to fix it > unless someone with it and a bit of technical knowledge can debug it > directly. > > Anyway thanks for the log, but would you mind adding the +hid channel too? > Not that it will make it magically fixable but I can have a look and see if > there's anything obvious. > > For instance something like running > `WINEDEBUG=+pid,+tid,+timestamp,+joycpl,+dinput,+hid wine control joy.cpl` > and then try running a couple of force feedback effects. The G25 does work on some very old versions of wine. I also have another wheel but it's from a custom opensource project called OpenFFBoard. Both have the same results though the OpenFFBoard supports more effects. Joy.cpl didn't spin the wheel. A FFB test program called fedit.exe did work with a constant effect. RichardBurnsRally didn't work but it should also be sending a constant effect. I have attached logs for all 3. Thanks. -- 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 9221] Force Feedback doesn't work but does after little source modification
by WineHQ Bugzilla 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #55 from groybe(a)gmail.com --- Created attachment 74010 --> https://bugs.winehq.org/attachment.cgi?id=74010 WINEDEBUG=+pid,+tid,+timestamp,+joycpl,+dinput,+hid RichardBurnsRally -- 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 9221] Force Feedback doesn't work but does after little source modification
by WineHQ Bugzilla 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #54 from groybe(a)gmail.com --- Created attachment 74009 --> https://bugs.winehq.org/attachment.cgi?id=74009 WINEDEBUG=+pid,+tid,+timestamp,+joycpl,+dinput,+hid fedit.exe Working constant force -- 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