December 2025 - Wine-bugs - list.winehq.org

[Bug 58104] New: MPRIS support for programs with background media playback
by WineHQ Bugzilla 03 Dec '25

03 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58104 Bug ID: 58104 Summary: MPRIS support for programs with background media playback Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wmp&wmvcore Assignee: wine-bugs(a)winehq.org Reporter: aaronliu0130(a)gmail.com Distribution: --- Windows has a feature where at least background media playback (through what seems to be the [Windows.Media.Playback.BackgroundMediaPlayer](https://learn.microsoft.com/e… and [Windows.Media.Playback.MediaPlayer](https://learn.microsoft.com/en-us/uwp/a… APIs) sends information about the currently playing audio to the system, where one may control the playback (through buttons or media keys. Play/Pause at minimum) and often view the current track's Title, Artist, Album Art, and the current progress, with "previous" and "next" keys also available. The Linux equivalent for this is [MPRIS](https://specifications.freedesktop.org/mpris-spec/latest/) (Media Player Remote Interfacing Specification), and it would be nice if Wine would gather the data send via these Windows APIs and send MPRIS information. -- 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 2

[Bug 59043] New: Error wine: could not load kernel32.dll
by WineHQ Bugzilla 03 Dec '25

03 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59043 Bug ID: 59043 Summary: Error wine: could not load kernel32.dll Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: winehq(a)hadrian-way.co.uk Distribution: --- Created attachment 79809 --> http://bugs.winehq.org/attachment.cgi?id=79809 Shell output of attemting to launch Memory Map I have used Wine for many years and have previously contributed to WineHQ with test reports for Memory Map. Owing to an unrelated problem, I had to resort to a clean installation of Kubuntu 24.04. Related facts: 1. I had earlier upgraded to Kubuntu 25.10. 2. My /home directory is on a separate partition and was not overwritten. 3. This is a 64 Bit Dell Optiplex 790. 3. On restoration to 24.04, everything worked except wine (see attachment). I vaguely remember seeing this before, (some years ago), but cannot remember what I did. -- 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 59080] New: 64-bit Linux wine-loader requires 32-bit dynamic linker
by WineHQ Bugzilla 03 Dec '25

03 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59080 Bug ID: 59080 Summary: 64-bit Linux wine-loader requires 32-bit dynamic linker Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)list.winehq.org Reporter: alex.franchuk(a)gmail.com Distribution: --- As of https://gitlab.winehq.org/wine/wine/-/commit/8c3f205696571558a6fae42314370f… (since wine 10.2), the loader defaults to the 32-bit loader, however this requires the 32-bit dynamic linker to be present (e.g. `/lib/ld-linux.so.2`). I feel this is undesirable; I had to install multilib files (32-bit glibc) to be able to run wine correctly. Note that I encountered this issue using pre-compiled wine binaries distributed as part of the Firefox cross-compile toolchain. I didn't look too deeply (but didn't see anything as part of that commit), but if there's some wine compile-time checks which determine whether this behavior occurs, perhaps that is to blame (e.g., if the server which compiled the wine toolchain had multilib files). Maybe this behavior should do a quick sanity check (like looking for the presence of `/lib/ld-linux.so.2`) before switching to the 32-bit loader? -- 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 1

[Bug 59036] New: Wine-devel 10.19 - 0ld Win95 game Hellbender crashes on setup.exe / auto.exe / Hellbend.exe
by WineHQ Bugzilla 03 Dec '25

03 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59036 Bug ID: 59036 Summary: Wine-devel 10.19 - 0ld Win95 game Hellbender crashes on setup.exe / auto.exe / Hellbend.exe Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)list.winehq.org Reporter: eick.roberto(a)gmail.com Distribution: --- Created attachment 79798 --> http://bugs.winehq.org/attachment.cgi?id=79798 backtrace bug 1 Old Win95 game (32bit) Hellbender crashes on setup.exe / auto.exe / Hellbend.exe Standard wine folder @ /home/user/.wine Happens persistently, on my Debian Sid x86_64 running Wine-devel 10.19 with the so called Experimental Wow64 mode. Seems to be unable to access file '/usr/src/packages/BUILD/dlls/winmm/waveform.c' Must related to sound, which should start playing but it doesn't, it crashes, after actually drawing/decorating the windows. Attachmed backtrace/details. There's a very strance path it tries to locate the "waveform.c". If I go into /usr/src no "packages" directory nor those subdirectories exist. Maybe it should be looking at a different location. -- 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 43775] New: Heroes of the Storm crash on start with d3d11
by wine-bugs＠winehq.org 03 Dec '25

03 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=43775 Bug ID: 43775 Summary: Heroes of the Storm crash on start with d3d11 Product: Wine Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maxi.cass11(a)gmail.com Distribution: --- Created attachment 59282 --> https://bugs.winehq.org/attachment.cgi?id=59282 terminal Output 2.17-staging with dx11 I don't know if the bug is in the non-staging version because Battlenet crash in non-staging. My game crash on my laptop with d3d11, I need to set the -dx9 argument to correct this. -- 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 48

[Bug 43849] New: Heroes of the Storm; crashes when Call Mech effect is on-screen
by wine-bugs＠winehq.org 03 Dec '25

03 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=43849 Bug ID: 43849 Summary: Heroes of the Storm; crashes when Call Mech effect is on-screen Product: Wine Version: 2.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jonathan(a)pearce.name Distribution: --- Steps to reproduce: Start Heroes of the Storm. Enter Try mode with D.Va. Take tower damage until your mech is dead. Shoot enemies until your Call Mech cooldown is activated. Use Call Mech 'E'. The mech arrival effect will begin but the game will crash before the mech becomes visible on-screen. A dialog box pops up with a e_gfxerrorshadercompilefailed error. Relevant wine stdout: fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x80004. fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x80004. fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2 fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2 fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2 fixme:hlsl_parser:hlsl_parse Check for valued return on void function. fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if needed, error out if conversion not possible. err:d3dcompiler:compile_shader HLSL shader parsing failed. fixme:dbghelp:elf_search_auxv can't find symbol in module fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x80004. fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub I experimented with winetricks d3dx9_43 but that didn't fix the crash (it does change the error signature). I also tried d3dcompiler_43 (native) but it didn't seem to matter. -- 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 29

[Bug 58988] New: [regression] Battle.net fails to start
by WineHQ Bugzilla 03 Dec '25

03 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58988 Bug ID: 58988 Summary: [regression] Battle.net fails to start Product: Wine-staging Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: mboquien(a)free.fr CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 79711 --> http://bugs.winehq.org/attachment.cgi?id=79711 Crash log Since wine-staging 10.19, Battle.net fails to start. It displays the connection window for a brief moment then it displays a crash reporting interface for Blizzard. Downgrading to wine-staging 10.18 fixes the issue. -- 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

[Bug 59048] New: Wine 10.19 with wow64 breaks RPGM games
by WineHQ Bugzilla 03 Dec '25

03 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59048 Bug ID: 59048 Summary: Wine 10.19 with wow64 breaks RPGM games Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: coco.claudio(a)postme.pm Distribution: --- Created attachment 79819 --> http://bugs.winehq.org/attachment.cgi?id=79819 wine Game.exe command output I'm using ArchLinux (package `wine-staging`, but the `wine` package doesn't work either) so it *could* be a PKGBUILD problem, but I doubt it since I compared the dependencies for both the 10.18.1 and the 10.19.1 and they are the same. I've recreated the prefix, in both my tests for either versions, and the 10.18.1 always work while the other doesn't. At first I thought it was an architecture problem, but I tried to run the 32bit version of a renpy game and it 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.

1 5

[Bug 58865] New: duke nukem 3d
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58865 Bug ID: 58865 Summary: duke nukem 3d 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: lars_martin4(a)hotmail.com Distribution: --- larsmartinhambro(a)fedora-linux:~/.wine/drive_c/Program Files (x86)/GOG.com/Duke Nukem 3D$ wine duke3d.exe 002c:fixme:winediag:loader_init wine-staging 10.15 is a testing version containing experimental patches. 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 009c:err:environ:init_peb starting L"C:\\Program Files (x86)\\HDD Health\\HDDHealthService.exe" in experimental wow64 mode 009c:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented! 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 00bc:err:environ:init_peb starting L"C:\\Program Files (x86)\\ASUS\\AXSP\\4.00.38\\atkexComSvc.exe" in experimental wow64 mode 00bc:fixme:ole:CoInitializeSecurity 00000000, -1, 00000000, 00000000, 6, 3, 00000000, 2, 00000000 stub 00bc:fixme:wbemprox:client_security_SetBlanket 79273934, 00C145B8, 10, 0, (null), 4, 3, 00000000, 0 00bc:fixme:wbemprox:client_security_Release 79273934 00bc:fixme:wbemprox:client_security_Release 79273934 00bc:fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x10 wine: Unhandled page fault on read access to 00000000 at address 793A43CD (thread 00bc), starting debugger... 00d4:err:environ:init_peb starting L"C:\\windows\\syswow64\\winedbg.exe" in experimental wow64 mode 00a4:err:ole:start_rpcss Failed to start RpcSs service 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 00e8:err:ole:start_rpcss Failed to start RpcSs service 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 003c:err:service:process_send_start_message service L"asComSvc" failed to start 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"asComSvc" failed to start: 1053 0104:err:environ:init_peb starting L"C:\\windows\\syswow64\\winedevice.exe" in experimental wow64 mode 0110:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\win32k.sys" 0110:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgkrnl.sys" 0110:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgmms1.sys" 010c:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\SecDrv": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"SecDrv" failed to start: 1114 00a4:err:ole:start_rpcss Failed to start RpcSs service 0024:fixme:winediag:loader_init wine-staging 10.15 is a testing version containing experimental patches. 0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 01d0:err:environ:init_peb starting L"C:\\windows\\syswow64\\winevdm.exe" in experimental wow64 mode 01d0:fixme:wow:wow64_NtSetLdtEntries 0107 0488323f 0000f39a 0000 00000000 00000000: stub 01d0:err:module:loader_init "krnl386.exe16" failed to initialize, aborting 01d0:err:module:loader_init Initializing dlls for L"C:\\windows\\syswow64\\winevdm.exe" failed, status c0000005 larsmartinhambro(a)fedora-linux:~/.wine/drive_c/Program Files (x86)/GOG.com/Duke Nukem 3D$ 01d4:fixme:winediag:loader_init wine-staging 10.15 is a testing version containing experimental patches. 01d4:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) -- 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 58991] New: Launching Need for Speed Underground 2 with a full path breaks KDE X11
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58991 Bug ID: 58991 Summary: Launching Need for Speed Underground 2 with a full path breaks KDE X11 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: user.pecheniok(a)gmail.com Distribution: --- I launched the game the same way I launched MW here: https://bugs.winehq.org/show_bug.cgi?id=58797#add_comment Most Wanted creates a window and hangs, you can still close it. Underground 2 on the other hand does something so that the screen goes permanently black. Rebooting the PC does not help. Still searching for a solution. Of course, this is caused by an application bug, but it doesn't leave windows unusable. I think this has to be fixed as soon as possible, as this is a pretty serious issue. (Using the system on wayland now. Maybe it affects wayland too, but don't want to check for now or at least until I find a fix for the x11 issue) -- 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 2