https://bugs.winehq.org/show_bug.cgi?id=53967
Bug ID: 53967
Summary: Running anything hangs on start up
Product: Wine
Version: 7.21
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
CC: piotr(a)codeweavers.com
Regression SHA1: 1cf1412a12c6ee6191d387162fecb456f0df2d89
Distribution: ---
$ wine winver
0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
003c:err:service:process_send_command service protocol error - failed to write
pipe!
003c:fixme:service:scmdatabase_autostart_services Auto-start service
L"PlugPlay" failed to start: 1053
0108:err:winediag:nodrv_CreateWindow Application tried to create a window, but
no driver could be loaded.
0108:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
+seh,+dc,+gdi,+winspool shows this as the reason of the hang:
0098:trace:seh:handle_syscall_fault code=c0000005 flags=0 addr=0x7e35fdef
ip=7e35fdef
0098:trace:seh:handle_syscall_fault info[0]=00000000
0098:trace:seh:handle_syscall_fault info[1]=0000000c
0098:trace:seh:handle_syscall_fault eax=00000000 ebx=7e3f4000 ecx=00000000
edx=7d74a1f0 esi=00000000 edi=7e407520
0098:trace:seh:handle_syscall_fault ebp=0031fbf8 esp=0031fbb0 cs=0023 ds=002b
es=002b fs=0063 gs=006b flags=00010246
0098:trace:seh:handle_syscall_fault returning to user mode ip=7e64c6fc
ret=c0000005
0098:trace:gdi:NtGdiCreatePatternBrushInternal 0xc0000005
NtGdiCreatePatternBrushInternal looks weird, commenting out OpenPrinterW()
and other winspool APIs in CreateDCW() fixes the crashes.
Both clang in msvc mode or ELF build show the same behaviour.
This is a regression:
1cf1412a12c6ee6191d387162fecb456f0df2d89 is the first bad commit
commit 1cf1412a12c6ee6191d387162fecb456f0df2d89
Author: Piotr Caban <piotr(a)codeweavers.com>
Date: Mon Nov 21 12:45:33 2022 +0100
gdi32: Get printer output file name in StartDoc.
dlls/gdi32/Makefile.in | 2 +-
dlls/gdi32/dc.c | 57 +++++++++++++++++++++++++++++++++++++++++++-------
include/ntgdi.h | 2 ++
3 files changed, 53 insertions(+), 8 deletions(-)
--
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=53923
Bug ID: 53923
Summary: tools/makedep during wine-7.21 build segfaults
Product: Wine
Version: 7.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bugzilla(a)uwe-dueffert.de
Distribution: ---
Created attachment 73479
--> https://bugs.winehq.org/attachment.cgi?id=73479
valgrind analysis of segfaulting tools/makedep
While wine-7.20 builds perfectly fine, the build of wine-7.21 reproducibly
fails for me due to the newly generated tools/makedep segfaulting. As makedep.c
was modified since 7.20, I figured you could be interested in what valgrind
says about that segfault (attached).
Let me know if I can provide further details that could help you.
Regards
Uwe
--
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=53130
Bug ID: 53130
Summary: ntdll:threadpool - test_tp_instance() fails (rarely)
on Windows 8+
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:threadpool - test_tp_instance() fails (rarely) on Windows 8+:
threadpool.c:1170: Test failed: WaitForSingleObject returned 0
threadpool.c:1210: Test failed: WaitForSingleObject returned 258
https://test.winehq.org/data/patterns.html#ntdll:threadpool
These two failures always go together.
The failure is pretty rare, about 4.1%, so it can easily be missing from a test
configuration's WineTest runs which results in 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=41989
Bug ID: 41989
Summary: program will not load and run
Product: Wine
Version: 2.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mark_crn(a)yahoo.com
Distribution: ---
Created attachment 56396
--> https://bugs.winehq.org/attachment.cgi?id=56396
save bug file
Musette encounter a fatal exception
--
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=53954
Bug ID: 53954
Summary: Saints Row 2022 fails with Unimplemented function
KERNEL32.dll.SetProcessInformation
Product: Wine
Version: 7.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mo78(a)abv.bg
Distribution: ---
Created attachment 73529
--> https://bugs.winehq.org/attachment.cgi?id=73529
Saints Row 2022 wine log
Saints Row 2022 fails with Unimplemented function
KERNEL32.dll.SetProcessInformation and it can't be started at all.
--
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=53741
Bug ID: 53741
Summary: Gothic 2 - Night of the Raven 2.7 - Msdbi.dll failed
to initialize
Product: Wine
Version: 7.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: VladimirVSC(a)yandex.ru
Distribution: ---
Created attachment 73183
--> https://bugs.winehq.org/attachment.cgi?id=73183
Gothic 2 msdbi.dll error report
The game doesn't start with "msdbi.dll failed to initialize" error. The same
game copy starts fine in stable 7.0 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.
https://bugs.winehq.org/show_bug.cgi?id=53288
Bug ID: 53288
Summary: Application compiled with MSVC 2022 ASan does not
start, needs QueryVirtualMemoryInformation
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: rpisl(a)seznam.cz
Distribution: ---
Application compiled with MSVC 2022 ASan does not start in Wine 7.11 as it
needs implementation of QueryVirtualMemoryInformation.
Console output:
==808==AddressSanitizer CHECK failed:
D:\a\_work\1\s\src\vctools\crt\asan\llvm\compiler-rt\lib\sanitizer_common\sanitizer_win.cpp:1108
"((QueryVirtualMemoryInformation &&
"ASan requires the Windows 10-only API, QueryVirtualMemoryInformation")) !=
(0)" (0x0, 0x0)
<empty stack>
--
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=53387
Bug ID: 53387
Summary: Vernier USB sensors are not usable in WINE
Product: Wine
Version: 7.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tuomas.nurmi(a)opinsys.fi
Distribution: ---
Created attachment 72775
--> https://bugs.winehq.org/attachment.cgi?id=72775
Logs from various situations described in the bug report
Vernier USB student laboratory sensors (
https://www.vernier.com/products/go-direct/ ) are not usable with WINE. Tested
on Debian 11 Bullseye (equivalent), kernel 5.10, wine 7.13 from
https://wiki.winehq.org/Debian . (Earlier tests with previous wine versions
have also been negatives, however, they haven't been as comprehensive and
well-documented as this)
Tested with an earlier sensor model, a Go! Temp ver 1.53 and a later Go Direct
Sensor (idVendor 08f7, idProducts 0002 and 0010, respectively). They show up in
Linux syslog as shown in attachment section 1.
Udev rules for the devices are in place, as described by (the somewhat
outdated) https://wiki.winehq.org/Hid and Vernier's native library guidelines
at https://github.com/VernierST/godirect-examples/tree/main/python , as
follows:
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", GROUP="plugdev", MODE="0666"
KERNEL=="hiddev*", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="08f7", MODE="0666"
SUBSYSTEM=="usb_device", ATTRS{idVendor}=="08f7", MODE="0666"
resulting into following permissions with plugged devices
crw-rw-rw- 1 root plugdev 242, 0 20. 7. 13:36 /dev/hidraw0
crw-rw-rw- 1 root root 180, 0 20. 7. 13:36 /dev/usb/hiddev0
Resulting in functioning sensors with the native library example software from
Vernier (attachment section 2), as well as with an earlier discontinued Linux
version of LoggerPro, and the Vernier Graphical Analysis Chrome app (
https://chrome.google.com/webstore/detail/vernier-graphical-analysi/dncgedb…
)
The sensors were tested also Windows 10, and were visible/detected by both the
Microsoft hid example application hclient.exe and Vernier LoggerPro3.
However, the devices are not recognized by LoggerPro3 nor hclient.exe run
through wine-7.13. Logs with WINEDEBUG=+hid,+wineusb,+plugplay of these are
shown in attachment sections 3, 4, and 5.
Not a specialist in any of the related fields, but the logs show seemingly
correctly recognized plugging of the device,
00cc:trace:wineusb:add_usb_device Adding new device 0x7f9330001f80, vendor
08f7, product 0010.
00d0:trace:wineusb:add_unix_device Adding new device 00007F934C016ED0, vendor
08f7, product 0010.
...
00c8:trace:plugplay:enumerate_new_device Creating new device
L"USB\\VID_08F7&PID_0010\\0".
but the device is not recognized by LoggerPro, nor listed by hclient.exe.
(I don't know if the plugplay:install_device_driver error following in the logs
is related)
--
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.