https://bugs.winehq.org/show_bug.cgi?id=57134
Bug ID: 57134
Summary: Mouse input does not work properly and mouse spinning
in Valve Deadlock
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: h0tc0d3(a)gmail.com
Distribution: ---
In the game Deadlock the mouse does not work in vanilla wine. The problem is
somehow related to raw input. There is no such problem in proton. This is also
the first game where this problem occurs. I can assume that the game only
understands absolute raw input, and wine sends relative data.
Video:
https://drive.google.com/file/d/1WRZZD0whER3ibOo28fN4rPP-UasMBu93/view?usp=…
--
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=55476
Bug ID: 55476
Summary: Unhandled exception: page fault on read access to
0x0000000000000010 in 64-bit code (0x000000073586a3).
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: masterweb801(a)gmail.com
Distribution: Debian
Created attachment 75038
--> https://bugs.winehq.org/attachment.cgi?id=75038
Wine had given this backtrace file.
I am installing my own application. I build it with python and made it
executable using pyinstaller. Then created MSI Installer of it using Advanced
Installer. Then I installed it with wine on Debian 12. It installed but when I
open it up, it throws an error. But this gives no error in Windows 10. I have
attached some files related this error.
--
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=54656
Bug ID: 54656
Summary: The winscard tests are not run on the GitLab CI
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winscard
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The winscard tests are not run on the GitLab CI:
winscard=dll is missing
See the gitlab-debian-* Linux results on:
http://winetest.dolphin/data/tests/winscard:winscard.html
I'm putting this as a Wine bug rather than a Wine GitLab one because I think
the fix is to update the tools/gitlab/image.docker file.
Also I'd argue this is a regression introduced by the commit that added the
dependency on libpcsclite because the Docker image update should have been made
there.
commit 8490c43f38e306fef7b5fed3ffcb256efd73af58
Author: Hans Leidekker <hans(a)codeweavers.com>
AuthorDate: Thu Feb 16 09:56:12 2023 +0100
winscard: Implement SCardEstablish/ReleaseContext() on top of libpcsclite.
--
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=57123
Bug ID: 57123
Summary: Wine crashes when input devices are plugged /
unplugged
Product: Wine-staging
Version: 9.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: germanapps(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
When I plug or unplug my mouse (or connect / disconnect my bluetooth mouse, it
doesn't matter), wine always crash regardless of the running application.
The bug has developed gradually. First version that crashes only on unplugging
was 9.4. Since version 9.11 wine crashes on both plugging and unplugging.
Tests were done by creating a completely new prefix for each tested version.
The error message wine prints into console:
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 131 (XInputExtension)
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 131 (XInputExtension)
Minor opcode of failed request: 3 (X_OpenDevice)
Device id in failed request: 0x7600001
Serial number of failed request: 262
Current serial number in output stream: 262
Minor opcode of failed request: 3 (X_OpenDevice)
Device id in failed request: 0x8200001
Serial number of failed request: 238
Current serial number in output stream: 238
The last version without the bug is 9.3.
--
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=57132
Bug ID: 57132
Summary: winedevice causes 100% CPU usage after unplugging HID
device
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hid
Assignee: wine-bugs(a)winehq.org
Reporter: winebugzilla(a)tasossah.com
Distribution: ---
Created attachment 77030
--> https://bugs.winehq.org/attachment.cgi?id=77030
Debug log
Unplugging a YubiKey (5 NFC) results in winedevice.exe fully loading a CPU
core.
Enabling the relevant debugging channels (WINEDEBUG=+winusb,+hid) reveals that
it's constantly trying to read a an HID report and failing.
The following message is repeated endlessly:
008c:trace:hid:hidraw_device_read_report Read failed. Likely an unplugged
device 5 Input/output error
Last reproduced in wine-9.16 from the winehq.org repository on Ubuntu 22.04.
Detailed log is attached. This has been happening for a while now.
--
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=57090
Bug ID: 57090
Summary: incorrectly parsing parameters in winevdm
Product: Wine
Version: 9.15
Hardware: x86-64
URL: https://winworldpc.com/product/aldus-photostyler/2x
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: guillere(a)adinet.com.uy
Distribution: Debian
"Aldus PhotoStyler 2.0 SE" installs "KODAC PRECISION Color configure" in the
control panel, when you run it, it does nothing.
Thinking it was a problem with the Control Panel Applet, I debugged kcfg32.cpl
and there I saw that it called kcfg16.exe
kcfg16.exe does nothing in wine, testing in windows I also notice that
kcfg16.exe (win16) does nothing.
I debug the applet again and see that it calls kcfg16.exe with parameters!
If the parameters it expects are not there then it ends silently.
I test in windows7 with the detected parameters. CMD =>
kcfg16.exe 1 "c:\windows\system32\kcfg.hlp" "KODAC PRECISION Color configure"
I try variations of parameters I come to understand the general form
kcfg16.exe $VALUE "$HELP_FILE_in_quotes" "$WINDOWS_TITLE_in_quotes"
$VALUE= 1 OR 2 OR 3 ; 3 is Snooper window
$HELP_FILE_in_quotes= need to be quoted! can be any string ; used to call
winhelp
$WINDOWS_TITLE_in_quotes= need to be quoted! can be any string ; used for
windows title
minimal functional form
kcfg16.exe 1""""
In wine CMD =>
kcfg16.exe 1 "c:\windows\system32\kcfg.hlp" "KODAC PRECISION Color configure"
=> not work
kcfg16.exe 1 "blabla" "blabla" => not work
kcfg16.exe 1 \"blabla\" \"blabla\" => WORK!!!!!!!
Debugging getting insted it call
winedvm.exe --app-name c:\windows\system32\kcfg16.exe
c:\windows\system32\kcfg16.exe 1 "blabla" "blabla" => also not work
winedvm.exe --app-name kcfg16.exe kcfg16.exe 1 \"blabla\" \"blabla\" => THIS
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=56651
Bug ID: 56651
Summary: 3ds max setup error
Product: Wine-staging
Version: 9.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: finenkofedor(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
3DS Max 2024 wasn't launching without pasting bs.odis dlls to system32 folder,
all libs was in setup folder. After setting dll override setup launched but
could not finish installation. Figured out there's problem in main package,
3dsmax.msi, it wasn't launched either. I attached torrent file linked to my
package
--
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=57113
Bug ID: 57113
Summary: File open dialog doesn't show all the filtered file
types
Product: Wine
Version: 9.16
Hardware: x86-64
URL: https://cef-builds.spotifycdn.com/cef_binary_127.3.5%2
Bg114ea2a%2Bchromium-127.0.6533.120_windows64_client.t
ar.bz2
OS: Linux
Status: NEW
Keywords: download, source
Severity: trivial
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
Created attachment 77003
--> https://bugs.winehq.org/attachment.cgi?id=77003
Wine 9.16 console output
Under Windows 10 the file open dialog shows a list of the filtered file types.
As it is such a small area its only use is to let you know that more than one
file type has been filtered.
Under Wine the same area only lists one file type, although the filter itself
does seem to work as expected.
Noticed when trying the "input types - multiple files" test in the CEF sample
application.
--
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=56921
Bug ID: 56921
Summary: MusicBee: Random moments of lag when scrolling,
seemingly related to rendering of rating stars.
Product: Wine-staging
Version: 9.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: v_winebugs(a)outlook.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 76742
--> https://bugs.winehq.org/attachment.cgi?id=76742
Log from terminal
Tested on Wine 9.5-staging, on Fedora 40 KDE Plasma Spin
MusicBee will have these random moments of lag when scrolling on views and
playlists that have rating stars enabled. It seems to be related to how the
stars are being rendered, since when they are hidden the lag goes away, and
this lag is not present when running MusicBee under Windows. To make it worse,
this lag persists after the app is restarted.
Attached is a log from the terminal done while using MusicBee with the lag.
--
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=56715
Bug ID: 56715
Summary: 05cc:fixme:netbios:nbDispatch (0035DCE0): command code
0x91
Product: Wine
Version: 9.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: netapi32
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
I'm trying to run "HASP License Manager as a Service" as describe on page 2 of
this document:
https://www.geocentrix.co.uk/support/downloads/Installing%20HASP%20License%…
The USB dongle is connected to the host system, the software is installed in a
new wineprefix, with dotnet45 installed through winetricks.
When starting the HASP license service, an endless list of messages like the
following is shown:
...
05ec:fixme:netbios:nbDispatch (0035DCE0): command code 0x91
05f0:fixme:netbios:nbDispatch (0035DCE0): command code 0x91
05f4:fixme:netbios:nbDispatch (0035DCE0): command code 0x91
05f8:fixme:netbios:nbDispatch (0035DCE0): command code 0x91
05fc:fixme:netbios:nbDispatch (0035DCE0): command code 0x91
0600:fixme:netbios:nbDispatch (0035DCE0): command code 0x91
...
I was only able to stop this, when running "wineserver -k" from another shell,
or when running the uninstaller "C:\Program Files (x86)\Aladdin\HASP
LM\lmunist.exe"
Obviously, code 0x91 is not implemented in
./dlls/netapi32/netbios.c
./include/nb30.h
I'm using wine v9.9
--
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.