https://bugs.winehq.org/show_bug.cgi?id=55227
Bug ID: 55227
Summary: wtsapi32:wtsapi - check_wts_process_info() fails to
get the user token on Windows 7
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 - check_wts_process_info() fails to get the user token on
Windows 7:
wtsapi.c:94: Test failed: pid 0x544: failed to get token user, error 998
wtsapi.c:95: this is the last test seen before the exception
0fc0:wtsapi: unhandled exception c0000005 at 772ADF96
See https://test.winehq.org/data/patterns.html#wtsapi32:wtsapi
Where 998 == ERROR_NOACCESS
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55225
Bug ID: 55225
Summary: kernel32:thread - test_stack() gets an unexpected
values for -2 & -3 indexes on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:thread - test_stack() gets an unexpected stack[-2] value on Windows:
thread.c:1180: Test failed: wrong data 0358FFF8 = 00000000
thread.c:1181: Test failed: wrong data 0358FFF4 = 00000000
See https://test.winehq.org/data/patterns.html#kernel32:thread
Where the first value depends on the stack pointer and changes with every run,
thus causing false positives.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54683
Bug ID: 54683
Summary: shlwapi:ordinal - test_SHFormatDateTimeA() fails due
to daylight saving time on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shlwapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shlwapi:ordinal - test_SHFormatDateTimeA() fails due to daylight saving time on
Windows:
ordinal.c:1734: Test failed: expected (12:00 PM), got (11:00 AM)
ordinal.c:1741: Test failed: expected (12:00:00 PM), got (11:00:00 AM)
ordinal.c:1749: Test failed: expected (12:00:00 PM), got (11:00:00 AM)
ordinal.c:1779: Test failed: expected (12:00 PM), got (11:00 AM) for time part
ordinal.c:1793: Test failed: expected (12:00:00 PM), got (11:00:00 AM) for time
part
ordinal.c:1811: Test failed: expected (2/14/2023 12:00 PM), got (2/14/2023
11:00 AM)
ordinal.c:1822: Test failed: expected (2/14/2023 12:00:00 PM), got (2/14/2023
11:00:00 AM)
See https://test.winehq.org/data/patterns.html#shlwapi:ordinal
The AM/PM translations can change the failure messages slightly but it's always
the same issue, on all Windows versions... except w10pro64v2004!
This set of failures started on 2023-03-13 which, together with the 1 hour
offset, clearly corresponds to the switch from CST to CDT (there was no
WineTest run on Sunday).
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55532
Bug ID: 55532
Summary: kernel32:actctx - test_two_dlls_at_same_time() crashes
on Windows 7+ and Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:actctx - test_two_dlls_at_same_time() crashes on Windows 7+ and Wine:
actctx.c:3236: manifest_other_guid
actctx.c:3452: Test failed: GetProcAddress failed
actctx.c:3452: Test failed: GetProcAddress failed
actctx.c:3505: this is the last test seen before the exception
1fc8:actctx: unhandled exception c0000005 at 00000000
actctx.c:4167: unhandled exception c0000005 in child process 1fc8
actctx.c:3452: Test failed: GetProcAddress failed
actctx.c:3542: this is the last test seen before the exception
034c:actctx: unhandled exception c0000005 at 00000000
actctx.c:4167: unhandled exception c0000005 in child process 034c
actctx.c:3452: Test failed: GetProcAddress failed
actctx.c:3582: this is the last test seen before the exception
16c0:actctx: unhandled exception c0000005 at 00000000
actctx.c:4167: unhandled exception c0000005 in child process 16c0
See https://test.winehq.org/data/patterns.html#kernel32:actctx
This started on 2023-09-05 and the failures happen on Windows 7+ and also Wine.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55317
Bug ID: 55317
Summary: user32:msg - test_hotkey() finds no free WinKey+letter
on Windows 11
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:msg - test_hotkey() finds no free WinKey+letter on Windows 11:
msg.c:18487: Test failed: Couldn't find any free Windows Key + letter
combination
See https://test.winehq.org/data/patterns.html#user32:msg
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54368
Bug ID: 54368
Summary: ::DrawGeometry doesn't respect stroke style
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
Distribution: ---
Created attachment 73938
--> https://bugs.winehq.org/attachment.cgi?id=73938
thick lines
There's an application that uses d2d1 to draw its UI, and when the app scales
its workspace the lines get very thick shapes. This seems to be related to
00d8:fixme:d2d:d2d_stroke_style_init transformType 1 is not supported
00d8:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style
000000001F3D8C80.
According to MSDN transformType 1 refers to D2D1_STROKE_TRANSFORM_TYPE_FIXED:
The stroke does not respect the world transform but it does respect the dpi and
stroke width.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53435
Bug ID: 53435
Summary: user32:msg - test_SendMessage_other_thread() sometimes
fails on Windows 7
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:msg - test_SendMessage_other_thread() sometimes fails on Windows 7:
msg.c:18505: Test failed: wrong status 00400040
https://test.winehq.org/data/patterns.html#user32:msg
Where 0x00400040 that there are still QS_SENDMESSAGE messages in the queue and
that one was added since the last call.
This is similar to the Windows 10-only bug 53434 but the status is different
and this failure only happens on Windows 7.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=52196
Bug ID: 52196
Summary: Program desinger.exe stop after starting with error
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: werbung(a)itssh.de
Distribution: ---
Created attachment 71249
--> https://bugs.winehq.org/attachment.cgi?id=71249
Bugreport
The install of this program was completed with no errors. It was installed
along with another program. The main program works wonderfully, but the
sub-program (desinger.exe) does not.
The OS is up to date. Wine is up to date.
In OS windows7 the program works.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54998
Bug ID: 54998
Summary: DnsQuery(DNS_TYPE_SRV) fails to parse some of the
server answers
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: patch, source
Severity: normal
Priority: P2
Component: dnsapi
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
Distribution: ---
Created attachment 74551
--> https://bugs.winehq.org/attachment.cgi?id=74551
patch
An application that uses ActiveDs sometimes fails to get domain DC using
DsGetDcNameW(). That's caused by a failing call to
DnsQuery("_ldap._tcp.dc._msdcs.domain.com", DNS_TYPE_SRV)
which in turn fails because DnsExtractRecordsFromMessage_UTF8() fails to parse
some of the server answers.
It looks like this happens because in the DNS_TYPE_SRV record name is the last
element, and in that case get_name() uses wrong boundary check and returns
NULL.
Just in case it will be useful I'm attaching my version of the fix with some
tests.
It seems that skip_name() also uses wrong boundary check, however usually some
other data follows the skipped name, so it currently doesn't cause failures.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54655
Bug ID: 54655
Summary: user32:msg - test_InSendMessage() sometimes gets
unexpected flags on Windows
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:msg - test_InSendMessage() sometimes gets unexpected flags on Windows:
msg.c:11738: Tests skipped: cannot set global hook
msg.c:19232: Failed sequence SendMessage from other thread 1:
msg.c:19232: 0: expected: msg 0402 - actual: MsgCheckProc: 00000000008B03E8
0402 wp 00000000 lp 00000000 (flags 19)
msg.c:19232: 1: expected: msg 0400 - actual: MsgCheckProc: 00000000008B03E8
0400 wp 00000000 lp 00000000 (flags 19)
msg.c:19252: Failed sequence SendMessage from other thread 3:
msg.c:19252: 0: expected: msg 0403 - actual: MsgCheckProc: 00000000008B03E8
0403 wp 00000000 lp 00000000 (flags 19)
msg.c:19252: 1: expected: msg 0401 - actual: MsgCheckProc: 00000000008B03E8
0401 wp 00000000 lp 00000000 (flags 19)
msg.c:19264: Failed sequence SendMessage from other thread 5:
msg.c:19292: Test failed: wrong flags a
msg.c:18660: Failed sequence SetFocus on a desktop window:
See https://test.winehq.org/data/patterns.html#user32:msg
Where 0xa == ISMEX_NOTIFY | ISMEX_REPLIED
and the test expected 0x9 == ISMEX_SEND | ISMEX_REPLIED
This happens about once per month and impacts at least Windows 7 & 10,
regardless of locale:
* 2022-08-31 on w7u-pt-PT 32-bit
* 2022-08-31 on w7u 32-bit
* 2022-09-06 on w7u 32-bit
* 2022-09-15 on w7u-pt-PT 32-bit
* 2022-12-12 on w1064 32-bit
* 2023-02-20 on w10pro64-ar 64-bit
* 2023-03-02 on w7u-de 32-bit
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54202
Bug ID: 54202
Summary: user32:msg - subtest_hvredraw() fails on most Windows
7 test configurations
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:msg - subtest_hvredraw() fails on most Windows 7 test configurations
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #0 (0, 0, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #1 (0, 0, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #2 (0, 0, 50, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #3 (0, 0, -50, -50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #4 (-50, -50, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #0 (0, 0, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #1 (0, 0, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #2 (0, 0, 50, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #3 (0, 0, -50, -50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #5 (-50, -50, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos
redraw #0 (0, 0, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos
redraw #1 (0, 0, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos
redraw #2 (0, 0, 50, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos
redraw #3 (0, 0, -50, -50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 40800000 SetWindowPos
redraw #0 (0, 0, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 40800000 SetWindowPos
redraw #4 (-50, -50, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 40800000 SetWindowPos
redraw #1 (0, 0, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 40800000 SetWindowPos
redraw #5 (-50, -50, 50, 0): Update region shall match expected region
msg.c:9764: Test failed: destroy child on thread exit: 1: the msg sequence is
not complete: expected 000f - actual 0000
msg.c:9764: Failed sequence destroy child on thread exit:
msg.c:9764: 0: expected: msg 0082 - actual: MsgCheckProc: 00BC00A0 0082 wp
00000000 lp 00000000 (flags 19)
msg.c:9764: 1: expected: msg 000f - actual: nothing
See https://test.winehq.org/data/patterns.html#user32:msg
These failures appeared as soon as the corresponding tests were introduced but
somehow the TestBot did not detect them when MR!1874 was submitted. So maybe
they are caused by interference from a previous Wine test.
commit b2a9445e155487f1b47a646b70edbe181a905454
Author: Jinoh Kang <jinoh.kang.kr(a)gmail.com>
Date: Thu Dec 22 01:20:59 2022 +0900
user32/tests: Add tests for CS_HREDRAW and CS_VREDRAW.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55354
Bug ID: 55354
Summary: user32:msg - test_dialog_messages() sometimes gets a
bad sequence on Windows 7
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:msg - test_dialog_messages() sometimes gets a bad message sequence on
Windows 7:
msg.c:15393: Test failed: CreateDialogParam_1: 17: the msg 0x001c was expected,
but got msg 0x000d instead
msg.c:15393: Test failed: CreateDialogParam_1: 18: the msg 0x0086 was expected,
but got msg 0x0083 instead
msg.c:15393: Test failed: CreateDialogParam_1: 19: the msg 0x0006 was expected,
but got msg 0x800b instead
msg.c:15393: Test failed: CreateDialogParam_1: 20: the msg 0x8005 was expected,
but got msg 0x001c instead
msg.c:15393: Test failed: CreateDialogParam_1: 21: the msg 0x0007 was expected,
but got msg 0x0086 instead
msg.c:15393: Test failed: CreateDialogParam_1: 23: the msg sequence is not
complete: expected 0000 - actual 0006
See https://test.winehq.org/data/patterns.html#user32:msg
Where: 0x0006 == WM_ACTIVATE
0x000d == WM_GETTEXT
0x001c == WM_ACTIVATEAPP
0x0083 == WM_NCCALCSIZE
0x0086 == WM_NCACTIVATE
0x8005 == EVENT_OBJECT_FOCUS
0x800b == EVENT_OBJECT_LOCATIONCHANGE
This first happened on 2023-06-22 and there has been about one instance per
week since, always receiving the same unexpected message sequence:
* 2023-06-22 win7_newtb-w7u-2qxl
* 2023-06-28 win7_newtb-w7u-es
* 2023-07-05 win7_newtb-w7u-2qxl
* 2023-07-27 win7_newtb-w7u-2qxl
--
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.
https://bugs.winehq.org/show_bug.cgi?id=51995
Bug ID: 51995
Summary: Roblox's bad performance on Wine
Product: Wine
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: penguinbotonline(a)protonmail.com
Distribution: ---
Created attachment 70986
--> https://bugs.winehq.org/attachment.cgi?id=70986
Stderr log from Wine
There is a common problem that occurs to the majority of RoL players, which is
bad performance. There 2 things that people usually have, frame drops and
performance degradation.
When a frame drop happens, with +seh these things appear in the logs
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55508
Bug ID: 55508
Summary: Wine 8.15: compiles successfully in Flatpak but fails
during runtime with a SIGSEGV
Product: Wine
Version: 8.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lunar.lattice0(a)gmail.com
Distribution: ---
Created attachment 75070
--> https://bugs.winehq.org/attachment.cgi?id=75070
partial stacktrace with gdb
Wine compiles in a Flatpak environment but fails to run any application (e.g.
wine explorer.exe). This problem did not exist on Wine 8.5 and our software is
currently halted on that Wine version. Wine crashes with a segfault before
throwing an error, "could not load kernel32.dll, status c0000135".
Our flatpak build for Wine 8.15 can be found at
https://github.com/flathub/io.github.vinegarhq.Vinegar/pull/32#issuecomment….
I have also tested with org.winehq.Wine by upgrading that Flatpak's manifest to
use wine 8.15, only to encounter the same 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.
https://bugs.winehq.org/show_bug.cgi?id=55238
Bug ID: 55238
Summary: ntdll:exception - The 64-bit test_nested_exception()
fails on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:exception - The 64-bit test_nested_exception() fails on Windows 11:
exception.c:4842: nested_exception_handler Rip 000001E4AD6D0007, Rsp
00000012F5BFFAB0, code 0x80000003, flags 0, ExceptionAddress 000001E4AD6D0007.
exception.c:4842: nested_exception_handler Rip 00007FFA236D428C, Rsp
00000012F5BFEAC0, code 0xdeadbeef, flags 0x90, ExceptionAddress
00007FFA236D428C.
exception.c:4867: Test failed: Got unexpected exception code 0xdeadbeef, flags
0x90.
exception.c:4870: Test failed: Got unexpected frame 00000012F5BFFAB0.
exception.c:4891: Test failed: Did not get nested exception.
See https://test.winehq.org/data/patterns.html#ntdll:exception
This failure is specific to the 64-bit tests and only happen on the Windows 11
VM, with out without the AMD/NVidia GPUs (but the nightlies only run the 32-bit
tests on the base configuration).
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54944
Bug ID: 54944
Summary: ntdll:exception - test_extended_context() crashes on
Window 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:exception - test_extended_context() crashes on Window 11:
exception.c:9542: Test failed: Got unexpected result ret 0, length 0x4ff.
exception.c:9556: Test failed: Got unexpected result ret 0, length 0x4ff, flags
0x00100001.
exception.c:9590: Test failed: Got unexpected bret 0, GetLastError() 122, flags
0x100001.
exception.c:9592: Test failed: Got unexpexted length 0x4ff.
exception.c:9593: Test failed: Got unexpected context 00000000DEADBEEF, flags
0x100001.
exception.c:9596: Test failed: Got unexpected ContextFlags 0xcccccccc, flags
0x100001.
exception.c:9599: Test failed: Got unexpected Offset -858993460, flags
0x100001.
exception.c:9601: Test failed: Got unexpected Length 0xcccccccc, flags
0x100001.
exception.c:9604: Test failed: Got unexpected Offset -858993460, flags
0x100001.
exception.c:9608: Test failed: Got unexpected Length 0xcccccccc, flags
0x100001.
exception.c:9611: Test failed: Got unexpected Offset -858993460, flags
0x100001.
exception.c:9613: Test failed: Got unexpected Length 0xcccccccc, flags
0x100001.
exception.c:9622: Test failed: Got unexpected p FFFFFFFFCD43BDDC, flags
0x100001.
exception.c:9625: Test failed: Got unexpected p FFFFFFFFCD43BDDC, length
0xcccccccc, flags 0x100001.
ntdll:exception:0974 done (-1073741819) in 0s 9642B
See https://test.winehq.org/data/patterns.html#ntdll:exception
The crash is systematic and happens in both the 32- and 64-bit tests. More
specifically the crash happens in the first call to GetXStateFeaturesMask() but
the real issue is the failure on line 9593 which indicates that the context
parameter is wrong.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55461
Bug ID: 55461
Summary: directmanipulation:manipulation sometimes times out on
Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
directmanipulation:manipulation sometimes times out on Windows 10:
directmanipulation:manipulation:2190 done (258) in 120s 0B
See https://test.winehq.org/data/patterns.html#directmanipulation:manipulation
The test normally runs in under 1 second which means the time out is caused by
a deadlock. However this is pretty rare and has only happened twice in the past
8 months:
* 2023-04-06 win21H1_newtb-w10pro64-hi-u8-64 (followed out-of-memory failures
in previous tests)
* 2023-08-18 win21H1_newtb-w10pro64-de-64 (followed dinput:joystick8 failures)
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55477
Bug ID: 55477
Summary: shell32:autocomplete - test_prefix_filtering()
sometimes fails on Windows because the AutoComplete
DropDown is visible
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shell32:autocomplete - test_prefix_filtering() sometimes fails on Windows
because the AutoComplete DropDown is visible:
autocomplete.c:671: Test failed: AutoComplete DropDown visible
See https://test.winehq.org/data/patterns.html#shell32:autocomplete
This is pretty rare and did not happen for 4 months but has started happening
again:
* 2023-01-16 win21H1_newtb-w10pro64-ar-64
* 2023-01-19 win22H2_newtb-w1064-tsign-64
* 2023-02-14 win1507_newtb-w1064v1507-64
* 2023-07-03 win21H1_newtb-w10pro64-he-64
* 2023-08-22 win7_newtb-w7u-2qxl
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55492
Bug ID: 55492
Summary: ntdll:threadpool - test_RtlRegisterWait() sometimes
fails in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntdll:threadpool - test_RtlRegisterWait() sometimes fails in Wine. There are
three variants which look like they are probably related:
(1)
threadpool.c:354: Test failed: expected info.userdata = 1, got 0
threadpool.c:370: Test failed: expected info.userdata = 1, got 0
threadpool.c:371: Test failed: expected info.threadid != 0, got 0
threadpool.c:373: Test failed: OpenThread failed with 87
threadpool.c:376: Test failed: QueueUserAPC failed with 6
(2)
threadpool.c:290: Test failed: expected info.userdata = 0, got 65536
threadpool.c:294: Test failed: expected info.userdata = 1, got 65536
threadpool.c:296: Test failed: WaitForSingleObject returned 0
(3)
threadpool.c:292: Test failed: expected info.userdata = 1, got 65536
threadpool.c:294: Test failed: WaitForSingleObject returned 0
See https://test.winehq.org/data/patterns.html#ntdll:threadpool
(1) This is the most common variant and it happens in both the GitLab and other
non-TestBot VMs:
* 2023-06-30 linux_fgtb-debian11-x86-64
* 2023-06-18 MR!3094
* 2023-06-06 linux_rbernon-vulkan-win64
* 2023-05-29 linux_fg-deb64-wow32
* 2023-05-24 MR!2628
* 2023-01-31 linux_fg-deb64-wow64
* 2023-01-11 MR!1940
(2) Only happened once and on the GitLab CI.
* 2023-04-28 MR!2682
(3) Only happened on the GitLab CI.
* 2023-08-25 linux_gitlab-debian-32
* 2023-06-02 MR!2954
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55579
Bug ID: 55579
Summary: kernel32:loader - test_ExitProcess() sometimes fails
on the 32-bit w8 VM
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:loader - test_ExitProcess() sometimes fails on the 32-bit w8 VM:
loader.c:3529: Test failed: GetThreadContext should fail
loader.c:3530: Test failed: expected ERROR_INVALID_PARAMETER, got -559038737
loader.c:3538: Test failed: SetThreadContext should fail
loader.c:3539: Test failed: expected ERROR_ACCESS_DENIED, got -559038737
See https://test.winehq.org/data/patterns.html#kernel32:loader
This started on 2023-09-04 and happens in about 50% of the WineTest runs and is
most likely caused by the commit below:
commit d64200805b1848f782c8a4ce1fdbcb9292fffe51
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Thu Aug 31 18:08:50 2023 +0200
kernel32/tests: Remove some workarounds for old Windows versions.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=49868
Bug ID: 49868
Summary: Hedgewars 1.0.0 crashes when a game against the
computer is started
Product: Wine
Version: 5.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)eclipso.eu
Distribution: ---
Created attachment 68209
--> https://bugs.winehq.org/attachment.cgi?id=68209
The console messages
Hedgewars crashes when the following steps are taken:
1) remove .wine directory
2) run wineboot
3) run the Hedgewars installer, accept the defaults. This will start Hedgewards
at the end of the installer
4) Press "Play a game on a single computer"
5) Press "Play a quick game against the computer with random settings"
6) Sometimes, the game now shows the error "The program hedgewars.exe has
encountered a serious problem and needs to close"
7) if the game does not crash, press escape and Y, and repeat step 5
My versions:
$ wine --version
wine-5.17 (Staging)
$ uname -a
Linux cedric-p4 5.8.10-arch1-1 #1 SMP PREEMPT Thu, 17 Sep 2020 18:01:06 +0000
x86_64 GNU/Linux
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55585
Bug ID: 55585
Summary: Redraw problem at Notepad++
Product: Wine
Version: 6.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: temp2004(a)freenet.de
Distribution: ---
Created attachment 75114
--> https://bugs.winehq.org/attachment.cgi?id=75114
Movie showing influence of left mouse button clicks at the degenerated document
list
There seems to be a problem affecting the Doc Switcher dialog of Notepad++:
When running Notepad++ for a long period inside Wine, file names are displayed
at wrong positions or appear multiple, sometimes only half lines are displayed.
Resizing Notepad++ main windows sometimes temporary corrects the complete file
list, but not always.
Clicking at a file name at his list always leads to a correct redraw of this
one file name
(watch attached movie).
Only the Doc Switcher dialog is affected: all other Notepad++ sub windows seem
to be correctly redrawn.
Seen at any releases of SuSE and Ubuntu during the last years. Also at
different computer hardware.
Seems to affect any Notepad++ releases (current I use 8.1.2).
At MS Windows this problem does not occur.
Steps:
Enable "Document List Panel=Show" at Menu Settings/Preferences/General.
Open and close some text files over a long period .
Right after start of Notepad++ everything seems to be OK.
The redraw problem needs some time (hours?) to appear.
Possibly computers Stand-By mode also has an influence.
If the problem appears, it will not go away until Notepad++ is restarted.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54530
Bug ID: 54530
Summary: Unable to find an entry point named
'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll'
Product: Wine
Version: 8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: uiautomationcore
Assignee: wine-bugs(a)winehq.org
Reporter: hunt3rgz(a)protonmail.com
Distribution: ---
Created attachment 74074
--> https://bugs.winehq.org/attachment.cgi?id=74074
Wine log
I runned a .NET 5.0 application written with Windows Forms
https://github.com/X-Hax/sa_tools
When i close the 'create gradient' window, it gives me this error
System.EntryPointNotFoundException: Unable to find an entry point named
'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll'.
at Interop.UiaCore.UiaDisconnectProvider(IRawElementProviderSimple provider)
at System.Windows.Forms.Control.ReleaseUiaProvider(IntPtr handle)
at System.Windows.Forms.Control.WmDestroy(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr
wparam, IntPtr lparam)
--
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.