https://bugs.winehq.org/show_bug.cgi?id=53131
Bug ID: 53131
Summary: ntdll:threadpool - test_tp_multi_wait() fails (rarely)
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_tp_multi_wait() fails (rarely) in Wine:
threadpool.c:1960: Test failed: WaitForSingleObject returned 258
https://test.winehq.org/data/patterns.html#ntdll:threadpool
The failure is pretty rare, about 3.2%, 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=52872
Bug ID: 52872
Summary: vbscript:run fails in Wine in Hindi
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
vbscript:run fails in Wine in Hindi
run.c:1874: Error in line 1813: 0 L"Invalid procedure call or argument"
run.c:1888: Test failed: unexpected call OnScriptError
run.c:2933: Test failed: expected global_success_d
run.c:2934: Test failed: expected global_success_i
run.c:2936: Test failed: parse_script failed: 800a0005
https://test.winehq.org/data/patterns.html#vbscript:run
A bisect shows that these failures started happening with the following commit:
commit e81327358a26b160740b3421a4c7f300b4d2f06f
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Apr 13 15:13:16 2022 +0200
kernelbase: Move codepage initialization to ntdll.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=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.
https://bugs.winehq.org/show_bug.cgi?id=53268
Bug ID: 53268
Summary: urlmon:protocol - test_protocol_terminate() fails on
Windows and Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
urlmon:protocol - test_protocol_terminate() fails on Windows and Wine:
protocol.c:1188: Test failed: unexpected call ReportResult
protocol.c:1196: Test failed: hrResult = 00000000, expected: 80004004
protocol.c:3334: Test failed: Read failed: 00000001
https://test.winehq.org/data/patterns.html#urlmon:protocol
Where 80004004 == E_ABORT.
These three failures always happen together. The last one is in
test_protocol_terminate() while the first two are in
ProtocolSink_ReportResult().
These failures happen on all Windows versions and in Wine too with varying
frequency (frequent on Windows 7 and less on 21H1, etc.).
--
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=53266
Bug ID: 53266
Summary: Syberia: game crashes frequently
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: memax(a)gmx.fr
Distribution: Ubuntu
Created attachment 72641
--> https://bugs.winehq.org/attachment.cgi?id=72641
terminal output
Ubuntu 20.04.4 LTS 64bit
NVIDIA GeForce 940MX with driver 510.73.05
Wine staging 7.11 (WineHQ binary package) with a clean Wine directory and the
default Wine configuration
Syberia (2002 game) GOG.com french version
syberia_1.0.0_hotfix4_(53936)
39e9e778c755c081f3e4b12dc5f6ef4260cbfb14 Game.exe
Level of detail: high
Screen depth: 32bit
Anti-aliasing: on
The game crashes frequently and randomly, each time at a different point in the
game. This doesn't seem to be triggered by any particular action in the game.
--
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.