wine-bugs

wine-bugs@winehq.org

1 participants
159269 discussions

[Bug 57251] New: Keepass 2: program crashes when clicking on the User name field to add or change an entry
by WineHQ Bugzilla 03 Oct '25

03 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=57251 Bug ID: 57251 Summary: Keepass 2: program crashes when clicking on the User name field to add or change an entry Product: Wine Version: 9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bouwe(a)westerdijk.info Distribution: --- Created attachment 77169 --> https://bugs.winehq.org/attachment.cgi?id=77169 Saved crash report As described in the Summary. -- 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.

1 8

[Bug 57241] New: Managed COM components fail to load outside of application directory
by WineHQ Bugzilla 03 Oct '25

03 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=57241 Bug ID: 57241 Summary: Managed COM components fail to load outside of application directory Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: bob(a)paradoxlost.com Distribution: --- Managed assemblies are not loaded outside of the "current" directory due to a failure to open the file using the CodeBase path. https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/mscoree/corruntimeho… Here, the incorrect variable is passed to CreateFileW. It should be filename instead of path. -- 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.

1 3

[Bug 9127] Multiple applications require system stream support in the MPEG-I splitter (Drome Racers, Ninki Seiyuu no Tsukukurikata)
by WineHQ Bugzilla 03 Oct '25

03 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=9127 --- Comment #125 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Bob from comment #124) > This issue is still reproducible in Wine 10.14. > After the error message is shown, the cutscene audio works with a black > screen. > The terminal shows: > > 01a8:err:quartz:autoplug Failed to add filter, hr 0x80004005. Please ensure that your 32-bit GStreamer plugins are installed and try again. -- 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.

1 0

[Bug 7115] Need for Speed III installer fails in Win9X mode, reporting "Could not get 'HardWareKey' value" (active PnP device keys in 'HKEY_DYN_DATA\\Config Manager\\Enum' missing)
by WineHQ Bugzilla 03 Oct '25

03 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=7115 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |b2acf5d8568026715101d4509bb | |e043889f0aca1 Status|STAGED |RESOLVED CC| |z.figura12(a)gmail.com Resolution|--- |FIXED --- Comment #29 from Zeb Figura <z.figura12(a)gmail.com> --- Fixed upstream by b2acf5d8568026715101d4509bbe043889f0aca1. -- 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.

1 0

[Bug 58736] New: Commandos: Behind Enemy Lines screen rotated, when playing on Xephyr/Wayland with KWin_x11
by WineHQ Bugzilla 03 Oct '25

03 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58736 Bug ID: 58736 Summary: Commandos: Behind Enemy Lines screen rotated, when playing on Xephyr/Wayland with KWin_x11 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: nintyfan19(a)gmail.com Distribution: --- Created attachment 79358 --> http://bugs.winehq.org/attachment.cgi?id=79358 Logs from GDI Game is launched incorrectly. Screen is rotated. I do not known if GDI is broken or something else. I attached GDI logs, cause I think it is most suspicious. -- 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.

1 3

[Bug 57547] New: All HIDRAW devices stop working after pressing extra button on Logitech G903 mouse
by WineHQ Bugzilla 03 Oct '25

03 Oct '25

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.

1 33

[Bug 57367] New: DLNest crash due to unimplemented function
by WineHQ Bugzilla 03 Oct '25

03 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=57367 Bug ID: 57367 Summary: DLNest crash due to unimplemented function Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: l12436.tw(a)gmail.com Distribution: --- DLNest new 2.0 version use dotnet and shown following message Unimplemented function ntdll.dll.NtCreateWaitCompletionPacket called at address 00006FFFFFC5F038 (thread 0140), starting debugger... which is seems like unimplemented in wine -- 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.

1 15

[Bug 58698] New: Application goes into an infinite loop under new wow64 but works okay under old wow64
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58698 Bug ID: 58698 Summary: Application goes into an infinite loop under new wow64 but works okay under old wow64 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: dkk089(a)gmail.com Distribution: --- Created attachment 79297 --> http://bugs.winehq.org/attachment.cgi?id=79297 WINEDEBUG=+virtual under "new wow64" Application goes into an infinite loop under new wow64 but works okay under old wow64 I have an application that enters an infinite loop under "new wow64" but works okay with "old wow64". Running under actual 64-bit Windows is okay too. The problem seems to be caused by application logic which calls VirtualAlloc() repeatedly in order to (presumably) find out the maximum available amount of memory that the application is able to allocate. The first hint that this might be somehow related to memory were the error messages reported when running under "old wow64" : 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x74010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 74000000 Running the application with WINEDEBUG=+virtual showed the NtAllocateVirtualMemory calls that are made by the application, starting with a size of 0x7fffffff, exploring a number of different sizes, and then eventually settling on 0x701f0000 : 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 7fffffff 2000 00000004 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 3fffffff 2000 00000004 01a0:trace:virtual:map_view got mem in reserved area 0x11050000-0x51050000 01a0:trace:virtual:dump_view View: 0x11050000 - 0x5104ffff (valloc) 01a0:trace:virtual:dump_view 0x11050000 - 0x5104ffff --rw- 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff 0x11050000 00000000 8000 -- snip : successful calls after that with sizes 0x5fffffff , 0x6fffffff -- 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 77ffffff 2000 00000004 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 -- snip : goes on to try sizes starting with 0x70 ... -- 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 701f0001 2000 00000004 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x70201000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 701f1000 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 701f0000 2000 00000004 01a0:trace:virtual:map_view got mem with anon mmap 0x80000000-0xf01f0000 01a0:trace:virtual:dump_view View: 0x80000000 - 0xf01effff (valloc) 01a0:trace:virtual:dump_view 0x80000000 - 0xf01effff --rw- 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 The application makes the same calls under "new wow64", but since none of those calls ever fail, it seems to get confused, reaches size=0, and then gets stuck on that size : 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 7fffffff 2000 00000004 016c:trace:virtual:map_view got mem with map_free_area 0x7fff0000-0xffff0000 016c:trace:virtual:dump_view View: 0x7fff0000 - 0xfffeffff (valloc) 016c:trace:virtual:dump_view 0x7fff0000 - 0xfffeffff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x7fff0000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 3fffffff 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x11050000-0x51050000 016c:trace:virtual:dump_view View: 0x11050000 - 0x5104ffff (valloc) 016c:trace:virtual:dump_view 0x11050000 - 0x5104ffff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x11050000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 1fffffff 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x11050000-0x31050000 016c:trace:virtual:dump_view View: 0x11050000 - 0x3104ffff (valloc) 016c:trace:virtual:dump_view 0x11050000 - 0x3104ffff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x11050000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 0fffffff 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x11050000-0x21050000 016c:trace:virtual:dump_view View: 0x11050000 - 0x2104ffff (valloc) 016c:trace:virtual:dump_view 0x11050000 - 0x2104ffff --rw- -- snip : repeated calls with size right-shifted by 1 -- 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 0000000f 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000007 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000003 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000001 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 It then loops on the call with size=0 indefinitely and keeps running until I kill the wineserver. Unfortunately, this is a proprietary legacy application so I can't share it, however I'll be more than glad to accept pointers on which debug channels to activate, any other further debugging steps, or changes to the code that might fix this. Thanks in advance. -- 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.

1 4

[Bug 35648] New: Anthem Room Correction 2 v1.0.1: crash when connecting to A/V receiver in auto mode
by wine-bugs＠winehq.org 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=35648 Bug ID: 35648 Summary: Anthem Room Correction 2 v1.0.1: crash when connecting to A/V receiver in auto mode Product: Wine Version: 1.7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tristan.schmelcher(a)gmail.com Created attachment 47607 --> http://bugs.winehq.org/attachment.cgi?id=47607 Console output The application Anthem Room Correction 2 v1.0.1 crashes when trying to connect to an A/V receiver if run in automatic mode (with "/Auto" specified on the command line). The application also fails in manual mode at the same spot, but it doesn't crash; instead it hangs with 100% CPU usage. The console output with stack trace from the crash in automatic mode is attached. The application can be downloaded at http://anthemav.com/downloads/ARC-2%20Setup.zip, but you must have an Anthem A/V receiver in order to get this far in it. I am happy to carry out suggested testing/debugging. 74dc2107ca936dddbd0fc6abbb2baf74e387c163 ARC-2 Setup.zip -- 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.

2 8

[Bug 58734] New: How to disable usage of wayland and use x11 (xwayland) instead
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58734 Bug ID: 58734 Summary: How to disable usage of wayland and use x11 (xwayland) instead Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: euloanty(a)live.com Distribution: --- After 9.22 it enforces wayland but it does not work correctly on my machine (like UI issues, keyboard issues, no touch support etc). How to disable it? -- 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.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs