https://bugs.winehq.org/show_bug.cgi?id=43185
Bug ID: 43185
Summary: "Battle Bugs" game in unresponsive once game starts
Product: Wine
Version: 2.9
Hardware: x86-64
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matt(a)nightrealms.com
Distribution: ---
Created attachment 58457
--> https://bugs.winehq.org/attachment.cgi?id=58457
Wine output from before starting the game
When playing the free game "Battle Bugs"
(https://ldjam.com/events/ludum-dare/38/battle-bugs) on 64 bit Linux, the game
start screen loads just fine, and pressing an indicated key starts the game
just fine, but once the game starts nothing is moving and the game doesn't
respond to any keys. Got the same results with both versions of the
executable, and both WINEARCH unspecified or set to win32
--
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=55656
Bug ID: 55656
Summary: user32:dialog - test_IsDialogMessage() fails in the
hi-u8 and mx-MX locales 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:dialog - test_IsDialogMessage() fails in the hi-u8 and mx-MX locales on
Windows:
w10pro64-hi-u8:
dialog.c:869: Test failed: Got unexpected wparam 0x97ade5.
dialog.c:580: Test failed: Got unexpected wparam 0xfffd.
w10pro64-mx-MX:
dialog.c:867: Test failed: Got unexpected wparam 0x3f.
dialog.c:578: Test failed: Got unexpected wparam 0x3f.
See https://test.winehq.org/data/patterns.html#user32:dialog
The 'mx-MX' locale is a mix of locales and may indicate the test only succeeds
when all the Windows locales match. For reference, mx-MX uses the following
settings:
SystemDefaultLCID 0411
UserDefaultLCID 040c
ThreadLocale 0411
SystemPreferredUILanguages 0412,0409
UserDefaultUILanguage 0412
ThreadUILanguage 0412
KeyboardLayout 00000000040A0C0A
Country 231
ACP 932
A bisect shows that both sets of failures started with the commit below:
commit fe594a83d4a87fccaced20372a83ecb2ef28de6c
Author: Zhiyi Zhang <zzhang(a)codeweavers.com>
Date: Fri Aug 18 11:39:19 2023 +0800
user32/tests: Test IsDialogMessageA() converting ASCII WM_CHAR messages.
--
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=55236
Bug ID: 55236
Summary: scrrun:dictionary - test_hash_value() gets bad hashes
on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: scrrun
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
scrrun:dictionary - test_hash_value() gets bad hashes on Windows:
dictionary.c:676: Test failed: got hash 0x2eb, expected 0x2ea
dictionary.c:686: Test failed: got hash 0x2eb, expected 0x2ea
dictionary.c:695: Test failed: got hash 0x2db, expected 0x2da
dictionary.c:721: Test failed: got hash 0x2eb, expected 0x2ea
dictionary.c:732: Test failed: got hash 0x2eb, expected 0x2ea
dictionary.c:742: Test failed: got hash 0x2db, expected 0x2da
See https://test.winehq.org/data/patterns.html#scrrun:dictionary
Note that the hash values change with every run 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=54791
Bug ID: 54791
Summary: explorerframe:nstc - test_events() sometimes gets
unexpected events on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: explorerframe
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
explorerframe:nstc - test_events() sometimes gets unexpected events on Windows
7. This can either be a single event but it can also happen multiple times for
multiple events:
nstc.c:2265: Test failed: Got event 4, count 1
or
nstc.c:1906: Test failed: Got event 7, count 0
nstc.c:1908: Test failed: Got event 4, count 0
nstc.c:1912: Test failed: Got event 4, count 1
nstc.c:1912: Test failed: Got event 7, count 1
nstc.c:1912: Test failed: Got event 12, count 8
See https://test.winehq.org/data/patterns.html#explorerframe:nstc
This first happened on 2022-12-07 and has been happening roughly once every
three week since. So it's probably caused by a commit in the fall of 2022.
--
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=54441
Bug ID: 54441
Summary: windows.media.speech:speech - test_Recognition()
sometimes gets unexpected recognizer state 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
windows.media.speech:speech - test_Recognition() sometimes gets unexpected
recognizer state on Windows 10:
speech.c:1775: Test failed: recog_state was 0.
See https://test.winehq.org/data/patterns.html#windows.media.speech:speech
This failure started on 2023-01-25.
--
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=54156
Bug ID: 54156
Summary: comctl32:edit & user32:edit - test_paste() sometimes
gets an empty string on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
comctl32:edit - test_paste() sometimes gets an empty string on Windows
edit.c:3238: Test failed: got 0
See https://test.winehq.org/data/patterns.html#comctl32:edit
This happens on Windows 10 1809 to 21H2 a bit less than 3 times per month.
Where 0 is the length of the string in the field we pasted to. So that field is
empty instead of having received the string we pasted.
We can also get this failure in user32:edit (2022-11-15 w10pro64v1809):
edit.c:3211: Test failed: got 0
See https://test.winehq.org/data/patterns.html#user32:edit
But the case above is for the single-line to single-line case and there is also
the same issue happening in the multi-line to multi-line case (2022-10-25
w11pro64-amd):
edit.c:3240: Test failed: got 0
So it's a pretty general, if rare (only 4 known instances in 6 months),
problem.
Note that while one could expect this to be caused by yet another
OpenClipboard() failure, like in bug 53276, there is no failure message
indicating this to be the case.
--
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=53276
Bug ID: 53276
Summary: user32:edit - test_paste() sometimes fails to access
the clipboard 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:edit - test_paste() sometimes fails to access the clipboard on Windows:
edit.c:3222: Test failed: expected 1, got 0 le=5
edit.c:3224: Test failed: expected 1, got 0
edit.c:3226: Test failed: expected 00000000008500A8, got 0000000000000000
edit.c:3228: Test failed: expected 1, got 0
edit.c:3234: Test failed: got 21
edit.c:3240: Test failed: got 21
https://test.winehq.org/data/patterns.html#user32:edit
Where 5 is ERROR_ACCESS_DENIED and indicates that the clipboard has already
been opened in another thread, process, etc.
This happens a lot on machines with an AMD GPU due to known interference from
the Radeon driver (see bug 47888).
But it also happens sometimes on machines with an Nvidia GPU (cw-gtx560) and
even on pure QEmu VMs such as w1064-1qxl (or fgtb-w10pro64). So there is either
some other source of interference, maybe from some Windows component, or an
issue (a race condition?) in the test itself.
It would be nice to identify the source of interference, if any, to see if it
can be neutralized. But maybe the only solution is to work around the issue as
in user32:clipboard (see commit 316eec8f6658).
--
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=55606
Bug ID: 55606
Summary: Finale 27 printing - incorrect linecap
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineps.drv
Assignee: wine-bugs(a)winehq.org
Reporter: davech(a)t-online.de
Distribution: ---
Wine 8.16 uses 'setlinecap' incorrectly in the postscript output. This is
correct in wine 7.0.2
--
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=55272
Bug ID: 55272
Summary: The 64-bit ntdll:exception crashes on Windows 10 1607
& 1709
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
The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709:
exception.c:3537: vect. handler c0000005 addr:000002858E4C0000
exception.c:3537: vect. handler c0000005 addr:000002858E4C0000
ntdll:exception:0dd8 done (-1073741819) in 0s 6581B
See https://test.winehq.org/data/patterns.html#ntdll:exception
Where -1073741819 == 0xC0000005 == STATUS_ACCESS_VIOLATION
The crashes started with GitLab CI's switch to Debian 12 for the WineTest
builds which are used in the WineTest nightlies. However they also happen with
binaries built on Debian 11 in this case it is just a coincidence.
Note that before that ntdll:exception was exiting silently on Windows 8 & 10 <=
1809, see bug 55111. These two issues may be one and the same, just producing
different results due to changes in the binary layout.
--
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.