https://bugs.winehq.org/show_bug.cgi?id=57547
Bug ID: 57547
Summary: All HIDRAW devices stop working after pressing extra
button on Logitech G903 mouse
Product: Wine
Version: 10.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hid
Assignee: wine-bugs(a)winehq.org
Reporter: dixonte+winehq(a)stc-networks.com
Distribution: ---
Created attachment 77615
--> https://bugs.winehq.org/attachment.cgi?id=77615
WINEDEBUG=+hid,+plugplay,+dinput,+rawinput WINEPREIF=$HOME/Games/star-citizen
/usr/lib/wine-staging-10.0_rc2/bin/wine control
I have my G903 configured such that pressing one of the extra buttons emulates
pressing F14 on a keyboard. I have also built a foot pedal using a
microcontroller that does the same thing. I use this for push-to-talk in
Discord.
When I press the extra button on my mouse, this seems to cause an error in wine
that stops all HIDRAW devices from working until I restart wineserver. Oddly
and importantly, the foot pedal does not cause the same issue. (I'm vaguely
aware this mouse is what Logitech calls 'HID++', so I wouldn't be surprised if
they are doing something weird that is tripping wine up.)
I've attached a log of reproducing the issue by running 'wine control' with
WINEDEBUG=+hid,+plugplay,+dinput,+rawinput
Now that I know how to do it I can reproduce the issue 100% of the time.
--
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=58023
Bug ID: 58023
Summary: Meld-3.22.2 fails to start with errormessagebox
(retrieves incorrect path via XDG_DATA_HOME env var)
Product: Wine
Version: 10.4
Hardware: x86-64
URL: https://download.gnome.org/binaries/win32/meld/3.22/Me
ld-3.22.2-mingw.msi
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
This very newest version of Meld fails with a FileNotFound error.
Workaround: XDG_DATA_HOME="" wine Meld.exe
Similar bug like https://bugs.winehq.org/show_bug.cgi?id=49987 which was about
XDG_DATA_DIRS. You also need the patch from that bug
Problem: XDG_DATA_HOME is also used in recycle.bin and winemenubuilder.
I gues we need a more general solution/rewrite ?
--
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=48291
Bug ID: 48291
Summary: Detroit: Become Human crashes on launch
Product: Wine
Version: 5.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
Distribution: ---
Created attachment 65990
--> https://bugs.winehq.org/attachment.cgi?id=65990
backtrace
For now I've only uploaded a backtrace, but it's a bit unusual:
0x0000000000000000: -- no code accessible --
Let me know if you need anything else.
--
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=57567
Bug ID: 57567
Summary: Punishing gray raven fails to launch
Product: Wine
Version: 10.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: francisco278herrera(a)gmail.com
Distribution: ---
Created attachment 77665
--> https://bugs.winehq.org/attachment.cgi?id=77665
debug log with WINEDEBUG=PGR.exe:+all
Punishing gray raven fails to launch, presumably due to failiing call to
2771.744:00f0:00f4:trace:reg:RegQueryValueExA
(000000000000014C,"SystemBiosVersion",0000000000000000,0000000000000000,00000000001058E0,0000000000105890=260)
with OBJECT_NAME_NOT_FOUND and several other registry keys fail with the same
error
and
failing call 2769.893:00f0:00f4:fixme:toolhelp:CreateToolhelp32Snapshot
Unimplemented: heap list snapshot
2769.910:00f0:00f4:fixme:toolhelp:Heap32ListFirst : stub
the game's anticheat does seem to scan memory after 2769.910:00f0:00f4:Ret
KERNEL32.CreateToolhelp32Snapshot() retval=0000014c ret=6ffff991a22d and scan
threads with Thread32Next so maybe the game is intentionally refusing to run in
wine, in which case the bug is invalid.
--
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=58025
Bug ID: 58025
Summary: winewayland: Not working functions
SetLayeredWindowAttributes and SetWindowRgn
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: viorca(a)ukr.net
Distribution: ---
When using winewayland driver not working functions SetLayeredWindowAttributes
and SetWindowRgn.
SetLayeredWindowAttributes - alpha blending ignored
SetWindowRgn - black window is displayed outside the region
--
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=49108
Bug ID: 49108
Summary: Error when starting application LTspice XVII
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 2010tch(a)gmail.com
Distribution: ---
Created attachment 67081
--> https://bugs.winehq.org/attachment.cgi?id=67081
System generated error report
When starting LTspice XVII a "serious error" is encounterd.
After 30 - 90 seconds, LTspice XVII will start as normal but at some point the
program will hang. I have to use a Ctrl-alt-del to restart my computer.
--
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=58019
Bug ID: 58019
Summary: All HKCU\Software\Wine keys should also work when put
into HKLM
Product: Wine
Version: 10.3
Hardware: aarch64
OS: MacOS
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: registry
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)agowa338.de
Hi,
I originally just wanted to swap my Control and Command key. After a while I
finally made my way to Bug #35351. (note: I didn't find any documentation about
this besides that issue and a bunch of websites with outdated statements like
it isn't possible and one has to use 3rd-party hotkey tools).
I then noticed the solution https://bugs.winehq.org/show_bug.cgi?id=35351#c6
but accidentally at first configured these settings within HKLM instead of HKCU
as the key "HKLM\Software\Wine\Mac Driver" did already existed where as
"HKCU\Software\Wine\Mac Driver" did not. And to my surprise it didn't work
then.
I think this is a bit unintuitive and therefore would like to suggest that
everything that currently checks for a value within "HKCU\Software\Wine\*"
should fall back onto "HKLM\Software\Wine\*" if it is absent.
Would this be possible to implement in a kinda generic way? It is also more or
less what Microsoft Windows does (for the most part at least).
--
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=57983
Bug ID: 57983
Summary: getaddrinfo cannot handle "https" as the service
string, but windows 10 can
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: katharine.chui(a)gmail.com
Distribution: ---
Created attachment 78236
--> https://bugs.winehq.org/attachment.cgi?id=78236
test/reproduce code
test code that can be built with mingw-w64 gcc attached, on linux wine, the
current output is:
getaddrinfo("google.com", "https", NULL, &res) failed with 10109
aka WSATYPE_NOT_FOUND
on windows, both "443" and "https" service strings 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=57985
Bug ID: 57985
Summary: lots of errors when running winecfg for the first time
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gamestar15(a)proton.me
Distribution: ---
Hello, when I run winecfg in the first time (no .wine directory is present), I
get the following errors:
winecfg
wine: created the configuration directory '/home/kali/.wine'
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
004c:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0054:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0054:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr
0x80004002
0054:err:ole:CoMarshalInterface Failed to marshal the interface
{6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
0054:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0054:err:ole:start_rpcss Failed to open RpcSs service
004c:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr
0x80004002
004c:err:ole:CoMarshalInterface Failed to marshal the interface
{6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
004c:err:ole:apartment_get_local_server_stream Failed: 0x80004002
009c:fixme:urlmon:InternetBindInfo_GetBindString not supported string type 20
009c:fixme:file:NtLockFile I/O completion on lock not implemented yet
009c:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
00b0:fixme:file:NtLockFile I/O completion on lock not implemented yet
00b0:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
00b0:fixme:msi:internal_ui_handler internal UI not implemented for message
0x0b000000 (UI level = 5)
00b0:fixme:msi:internal_ui_handler internal UI not implemented for message
0x0b000000 (UI level = 5)
009c:fixme:msi:internal_ui_handler internal UI not implemented for message
0x0b000000 (UI level = 1)
009c:fixme:msi:internal_ui_handler internal UI not implemented for message
0x0b000000 (UI level = 1)
011c:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10
002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10
0148:err:setupapi:do_file_copyW Unsupported style(s) 0x10
002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10
0148:err:setupapi:do_file_copyW Unsupported style(s) 0x10
Also, in the middle of the errors, I got a prompt to install wine mono
installer, and I clicked on "install", but the errors happen also without
installing it.
At the end of the errors,the configuration of wine finally does open, which is
the good part.
Few important points to mention:
1. I tested this on kali linux 2025.1, but also on linux mint 22.1, so it has
nothing to do with kali linux.
2. I tested this on winehq-devel version 10.3 (the latest version up to date)
3. I installed winehq-devel exactly by the steps written in
https://gitlab.winehq.org/wine/wine/-/wikis/Debian-Ubuntu
4. In the error log, I am not referring to the "fixme" messages, I know they
are
features that will be added in the future.
If there is anything you need more that is missing, please tell me.
--
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=58021
Bug ID: 58021
Summary: Wreckfest 2 shows a black screen after launch
Product: vkd3d
Version: 1.15
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Fatal Error: D3D12CreateDeviceAndSwapChain() failed, result: 0x80070057
--
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.