- Wine-Bugs - list.winehq.org

[Bug 53192] New: FlexiPDF 3.0.3 crashes when moving window: dlls/ntdll/unix/thread.c:1737: ntdll_set_exception_jmp_buf: Assurance »!jmp || !ntdll_get_thread_data()->jmp_buf« not fulfilled
by WineHQ Bugzilla June 22, 2022

June 22, 2022

https://bugs.winehq.org/show_bug.cgi?id=53192 Bug ID: 53192 Summary: FlexiPDF 3.0.3 crashes when moving window: dlls/ntdll/unix/thread.c:1737: ntdll_set_exception_jmp_buf: Assurance »!jmp || !ntdll_get_thread_data()->jmp_buf« not fulfilled Product: Wine Version: 7.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: postix(a)posteo.eu Distribution: --- Created attachment 72629 --> https://bugs.winehq.org/attachment.cgi?id=72629 Terminal output ### Issue FlexiPDF 3.0.3 crashes when trying to move its window by dragging the titlebar. ### Download link `https://www.softmaker.net/down/flexipdf2022.exe` ### System Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.18.5-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Graphics Processor: AMD RENOIR -- 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 50103] i have a error help me
by WineHQ Bugzilla June 22, 2022

June 22, 2022

https://bugs.winehq.org/show_bug.cgi?id=50103 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |ABANDONED CC| |fgouget(a)codeweavers.com Status|NEEDINFO |RESOLVED --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- No answer to a year-old request for information. -- 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 43347] New: valgrind shows an unintialized read in dlls/iphlpapi/ tests/iphlpapi.c
by wine-bugs＠winehq.org June 22, 2022

June 22, 2022

https://bugs.winehq.org/show_bug.cgi?id=43347 Bug ID: 43347 Summary: valgrind shows an unintialized read in dlls/iphlpapi/tests/iphlpapi.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: iphlpapi Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo ../../../tools/runtest -q -P wine -T ../../.. -M iphlpapi.dll -p iphlpapi_test.exe.so iphlpapi && touch iphlpapi.ok ==10952== Syscall param ioctl(SIOCGIFINDEX) points to uninitialised byte(s) ==10952== at 0x4338F79: ioctl (syscall-template.S:84) ==10952== by 0x435916D: if_nametoindex (if_index.c:47) ==10952== by 0x4B25E43: getInterfaceIndexByName (ifenum.c:143) ==10952== by 0x4B2EC7E: IPHLP_if_nametoindex (iphlpapi_main.c:3233) ==10952== by 0x488198E: test_interface_identifier_conversion (iphlpapi.c:1958) ==10952== by 0x48831AB: func_iphlpapi (iphlpapi.c:2230) ==10952== by 0x4884014: run_test (test.h:603) ==10952== by 0x4884465: main (test.h:687) ==10952== Address 0x4b0f8c0 is on thread 1's stack ==10952== in frame #1, created by if_nametoindex (if_index.c:35) ==10952== Uninitialised value was created by a stack allocation ==10952== at 0x4359141: if_nametoindex (if_index.c:41) ==10952== -- 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 1

[Bug 53241] New: wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits during the test?
by WineHQ Bugzilla June 22, 2022

June 22, 2022

https://bugs.winehq.org/show_bug.cgi?id=53241 Bug ID: 53241 Summary: wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits during the test? Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wtsapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits during the test? Here is the failure: wtsapi.c:78: Test failed: failed to find pid 0x20e4 wtsapi.c:82: this is the last test seen before the exception 0618:wtsapi: unhandled exception c0000005 at 0000000000401848 https://test.winehq.org/data/patterns.html#wtsapi32:wtsapi The crash happens when check_wts_process_info() dereferences the NULL pointer returned by find_nt_process_info(). So presumably the test must check that some API does return information about at least some processes but it seems allowances should be made for processes exiting during the test. -- 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 53200] New: WET (a dotnet45 framework for web printing terminal): black block covered the content. i can edit with libreoffice draw. the content is there, but all covered with black block.
by WineHQ Bugzilla June 22, 2022

June 22, 2022

https://bugs.winehq.org/show_bug.cgi?id=53200 Bug ID: 53200 Summary: WET (a dotnet45 framework for web printing terminal): black block covered the content. i can edit with libreoffice draw. the content is there, but all covered with black block. Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P1 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dejoebad(a)yahoo.com Distribution: --- WET (a dotnet45 framework for web printing terminal): black block covered the content. i can edit with libreoffice draw. the content is there, but all covered with black block. https://www.instagram.com/p/Ce33e8vJ-n0 this is the output from windows and wine https://www.instagram.com/p/CfBo3hVPd2d this is what actually behind the black blocks. i'd print the file to pdf and edit with libreoffice draw. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 44337] New: d3d9/tests/device.ok fails on Nvidia (Nouveau drivers) in test_occlusion_query()
by wine-bugs＠winehq.org June 21, 2022

June 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=44337 Bug ID: 44337 Summary: d3d9/tests/device.ok fails on Nvidia (Nouveau drivers) in test_occlusion_query() Product: Wine Version: 3.0-rc5 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- with the following lines: device.c:5915: Test failed: Got unexpected hr 0x1. device.c:5919: Test failed: Got unexpected hr 0x1. device.c:5920: Test failed: Got unexpected query result 0xffffffffffffffff. It would be nice to fix this as this is currently the only D3D test failure on the cw2 test machine. -- 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 48820] New: user32:win "unexpected 0x7fff message" Japanese Windows 10 failures
by WineHQ Bugzilla June 21, 2022

June 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=48820 Bug ID: 48820 Summary: user32:win "unexpected 0x7fff message" Japanese Windows 10 failures Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: major Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The TestBot's w1064v1809-zh_CN configuration runs the tests on Windows 10 1809 in a Chinese locale. This test configuration gets unique failures in user32:win: win.c:3852: Test failed: hwnd 007404D2 message 7fff win.c:3858: Test failed: message 7fff available win.c:3931: Test failed: hwnd 007404D2/0054050A message 7fff win.c:3934: Test failed: hwnd 007404D2/0054050A message 7fff Note how these messages are very similar to the IME messages in bug 48819. However 0x7fff is a totally unknown message: all I can say about it is that it's WM_APP-1. So maybe it's another IME system. Maybe not? See: https://test.winehq.org/data/tests/user32:win.html However note that quite often WineTest fails to submit its results to test.winehq.org, typically because it times out. So you can more easily find the latest failure by looking for the "32 bit WineTest: base VMs" jobs on the TestBot. Finally, three of these messages include the window handles which means they are "always new". Because of this the TestBot will mistakenly attribute the failure to any user32 patch submitted to wine-devel, which should cause them to be rejected. So I bumped the priority on this 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 7

[Bug 53228] New: dxgi:dxgi - test_swapchain_window_styles() sometimes fails on Windows 10
by WineHQ Bugzilla June 21, 2022

June 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=53228 Bug ID: 53228 Summary: dxgi:dxgi - test_swapchain_window_styles() sometimes fails on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dxgi:dxgi - test_swapchain_window_styles() sometimes fails on Windows 10: dxgi.c:6125: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. dxgi.c:6141: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. dxgi.c:6169: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. dxgi.c:6196: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. dxgi.c:6212: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100. https://test.winehq.org/data/patterns.html#dxgi:dxgi This failure has been seen on Windows 10 1507 to 21H2. Furthermore, because of the test's multi-threading it has an elevated risk of causing 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 1

[Bug 53209] New: GTA San Andreas. Audio bug
by WineHQ Bugzilla June 21, 2022

June 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=53209 Bug ID: 53209 Summary: GTA San Andreas. Audio bug Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jon9097(a)gmail.com Distribution: --- When you rotate the camera around the character, the sound almost completely goes from one speaker to the other and back again. I did not find anything strange in the logs. This problem has been in wine for as long as I can remember, no such thing on windows. I wish that it was solved and the sound was distributed normally. -- 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 53173] New: user32:input - test_Input_mouse() randomly fails to get the expected mouse button or hit-test messages
by WineHQ Bugzilla June 21, 2022

June 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=53173 Bug ID: 53173 Summary: user32:input - test_Input_mouse() randomly fails to get the expected mouse button or hit-test messages Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:input - test_Input_mouse() randomly fails to get the expected mouse button or hit-test messages: input.c:3398: Test failed: expected WM_LBUTTONDOWN message input.c:3399: Test failed: expected WM_LBUTTONUP message input.c:3426: Test failed: expected WM_NCHITTEST message input.c:3427: Test failed: expected WM_RBUTTONDOWN message input.c:3428: Test failed: expected WM_RBUTTONUP message input.c:3457: Test failed: expected WM_LBUTTONDOWN message input.c:3458: Test failed: expected WM_LBUTTONUP message input.c:3511: Test failed: expected loop with WM_NCHITTEST messages input.c:3564: Test failed: expected WM_LBUTTONDOWN message input.c:3565: Test failed: expected WM_LBUTTONUP message https://test.winehq.org/data/patterns.html#user32:input The failure list is always the same except for the first two which are not always present. This happened on w7u-2qxl, w86 and most Windows 10 1607+ test configurations up to 21H2. So it's not a quirk of a specific Windows version. -- 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