https://bugs.winehq.org/show_bug.cgi?id=53975
Bug ID: 53975
Summary: d3drm:d3drm sometimes fails to create an immediate
mode device in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3drm:d3drm sometimes fails to create an immediate mode device in Wine:
d3drm.c:5843: Test failed: Cannot create IM device, skipping tests.
This can happen in either test_create_device_from_d3d2() or
test_create_device_from_d3d3() and always comes with the following winediag
message repeated 3 times in the Wine log:
063c:err:winediag:d3d_device_create The application wants to create a Direct3D
device, but the current DirectDrawRenderer does not support this.
See https://test.winehq.org/data/patterns.html#d3drm:d3drm
So far this has only been seen on debian11 and debiant so it may be related to
their dual-screen configuration. Also this failure first happened on 2022-11-07
and there are 4 known instances so far (2 in the nightly runs and 2 TestBot job
false positives). So it is probably caused by some recent Wine change.
--
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=53270
Bug ID: 53270
Summary: test_WSARecv() fails when using wow64 thunks
[Wow64ApcRoutine() overwrites return value set by
NtContinue()]
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: source, testcase
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
Created attachment 72642
--> https://bugs.winehq.org/attachment.cgi?id=72642
test diff
This might be a bit early since the wow64 path isn't exactly supported, but
(with a couple patches to ntdll to enable it in the first place) it works well
enough to expose a bug in its own implementation, which is more than a little
tricky to solve.
I'm attaching a diff to the tests, which I will submit upstream, which
demonstrates the root of the problem.
KiUserApcDispatcher can be called from three-ish places: wait functions,
NtTestAlert, and NtContinue. In the case of the former two KiUserApcDispatcher
will be passed a wow64 context which, among other things, has its %rax/%eax set
to STATUS_USER_APC or STATUS_SUCCESS respectively. In the latter case %rax/%eax
comes from the passed-in context.
Wow64ApcRoutine tries to translate the %rax from the 64-bit context into the
%eax that the 32-bit context will restore to. In the former two cases this is
STATUS_USER_APC or STATUS_SUCCESS and things work fine. In the latter case,
however, this overwrites %eax from the passed-in 32-bit context. Note that we
don't get the right %eax from ntdll either, because (a) ntdll gives us a 64-bit
context anyway, and (b) we don't use NtContinue but rather NtTestAlert. That
does mean we could fix it by using NtContinue and putting the %eax value into
%rax, which is a bit weird but I don't know if there's a better option.
This is wrong inherently, as the attached tests show, but it more saliently
ends up breaking LdrInitializeThunk, because on i386 RtlUserThreadStart is
called with %eax pointing to the thread procedure, and we then overwrite that
with zero.
--
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=49266
Bug ID: 49266
Summary: Amazon Games installs but won't start
Product: Wine
Version: 5.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 67270
--> https://bugs.winehq.org/attachment.cgi?id=67270
Console Output (wine 5.8)
Hello everyone,
I download the Amazon games installer from:
https://download.amazongames.com/AmazonGamesSetup.exe
and got it installed with wine 5.8 - Unfortunately the application doesn't
launch. Console output is attached.
--
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=54168
Bug ID: 54168
Summary: kernel32:console - test_wait() sometimes fails on
Windows 8+
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:console - test_wait() sometimes fails on Windows 8+:
console.c:1198: Test failed: WaitForSingleObject returned 0
console.c:1200: Test failed: WaitForSingleObject returned 0
console.c:1202: Test failed: WaitForSingleObject returned 0
console.c:1204: Test failed: WaitForSingleObject returned 0
console.c:1206: Test failed: WaitForSingleObject returned 0
console.c:1208: Test failed: NtWaitForSingleObject returned 0
console.c:1211: Test failed: NtWaitForSingleObject returned 0
See https://test.winehq.org/data/patterns.html#kernel32:console
This happens a bit less that twice per month.
--
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=53236
Bug ID: 53236
Summary: d3d9:device - test_wndproc() sometimes gets an
unexpected WM_DISPLAYCHANGE in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d9:device - test_wndproc() sometimes gets an unexpected WM_DISPLAYCHANGE in
Wine:
device.c:4349: Test failed: Expected message 0x7e for window 0x1, but didn't
receive it, i=1.
device.c:4359: Test failed: Got unexpected hr 0x88760869.
https://test.winehq.org/data/patterns.html#d3d9:device
Where 0x007e == WM_DISPLAYCHANGE.
The second failure is not always present but does not seem to happen without
the first one so they are probably related.
These failures:
* Happen on my Debian 11 + Intel + KDE box (fg-deb64)
* Don't seem to happen on my Debian 11 + QXL + fvwm + single monitor VM
* Happen on the TestBot's Debian 11 + QXL + fvwm + dual monitor VM
* Happen on the TestBot's Debian Testing + QXL + fvwm + dual monitor VM
(very rarely but two wow64 instance have been seen)
--
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=47407
Bug ID: 47407
Summary: Hard Truck 2: King of The Road (GOG version): movies
don't play
Product: Wine
Version: 4.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: t6zm3v62fkp7fe5(a)yandex.ru
Distribution: ---
Created attachment 64755
--> https://bugs.winehq.org/attachment.cgi?id=64755
Screenshot from intro movie
In Hard Truck 2: King of The Road (GOG version), movies don't play: e.g. intro
logos and movie (screenshot-from-intro-movie.png) and movies when you're
arrested or robbed by mafia.
Lubuntu 18.04.2, Wine 4.11 from official PPA.
--
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=54058
Bug ID: 54058
Summary: user32:input - test_ToAscii() fails in the Hindi UTF-8
locale
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
Created attachment 73613
--> https://bugs.winehq.org/attachment.cgi?id=73613
user32/tests: Skip a ToAscii() test in UTF-8 code pages.
user32:input - test_ToAscii() fails in the Hindi UTF-8 locale:
input.c:3133: Test failed: ToAscii for character 'A' didn't return 1 (was 0)
See https://test.winehq.org/data/patterns.html#user32:input
Note that this did not happen before 2022-11-21 because some unknown Windows
quirk caused the UserDefaultLCID and ThreadLocale to be reset to English before
the test was started.
In any case it seems ToAscii() does not depend just on the keyboard layout but
also on the current code page which makes sense. So then maybe we should limit
the test to non-UTF-8 code pages as in the attached patch?
--
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=54020
Bug ID: 54020
Summary: The 32-bit ntdll:wow64 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
The 32-bit ntdll:wow64 fails on Windows 11:
wow64.c:254: Test failed: wrong len 0
wow64.c:255: Test failed: wrong teb 0000004C / 00000000
wow64.c:258: Test failed: GdiBatchCount not set
wow64.c:282: Test failed: wrong peb 00000000 / 00000002
wow64.c:285: Test failed: wrong len 0
wow64.c:295: Test failed: wrong len 0
wow64.c:301: Test failed: wrong ImagePathName ptr 00000000 / 00000000-00000000
wow64.c:302: Test failed: wrong CommandLine ptr 00000000 / 00000000-00000000
wow64.c:303: Test failed: wrong WindowTitle ptr 00000000 / 00000000-00000000
wow64.c:304: Test failed: wrong Desktop ptr 00000000 / 00000000-00000000
wow64.c:305: Test failed: wrong ShellInfo ptr 00000000 / 00000000-00000000
wow64.c:331: Test failed: debugging failed
wow64.c:333: Test failed: wrong len 0
wow64.c:460: cs 0023 ss 002b fs 0053
wow64.c:782: Test failed: unknown module 7ffb1ed00000 L"wow64base.dll" found
wow64.c:782: Test failed: unknown module 7ffb20100000 L"wow64con.dll" found
See https://test.winehq.org/data/patterns.html#ntdll:wow64
The values are pretty stable from one run to the next but do change from time
to time (causing false positives). Note also that the 64-bit version fails on
Windows 11 too but the failures there are pretty different (see bug 54019).
--
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=53818
Bug ID: 53818
Summary: foobar2000 crashes shortly after startup
Product: Wine
Version: 7.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matthias.grobarek(a)posteo.de
Distribution: ---
Created attachment 73344
--> https://bugs.winehq.org/attachment.cgi?id=73344
winedbg output
After starting foobar2000, it quickly crashes after a few seconds, no matter
what you do. Wine 7.18 and 7.17 are not affected.
I’m using wine-staging (no matter the version) on Gentoo Linux (kernel 6.0.2),
compiled for both 32bit and 64bit, with the following flags activated: x, alsa,
fontconfig, mshtml, gstreamer, mingw, mscoree, gettext, openal, opengl, sdl,
gnutls, freetype, udev, dbus, unwind, usb, vulkan, xcomposite.
I attached the output of winedbg and also the crash log and dump that
foobar2000 itself produces. If you need any more information, please tell me
what exactly I should do.
--
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=53526
Bug ID: 53526
Summary: kernel32:sync - test_timer_queue() occasionally fails
to delete the timer on Windows 10
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:sync - test_timer_queue() occasionally fails to delete the timer on
Windows 10:
sync.c:1135: Test failed: DeleteTimerQueueTimer
https://test.winehq.org/data/patterns.html#kernel32:sync
This failure happened twice:
* 2022-05-27 w10pro64-de-64
* 2022-08-04 w10pro64-he-64
--
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.