wine-bugs

wine-bugs@winehq.org

1 participants
159325 discussions

[Bug 58648] New: Wine Regedit window flickers with Wayland driver- possible regression
by WineHQ Bugzilla 21 Oct '25

21 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58648 Bug ID: 58648 Summary: Wine Regedit window flickers with Wayland driver- possible regression Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: agarplayerarlon(a)gmail.com Distribution: --- Created attachment 79221 --> http://bugs.winehq.org/attachment.cgi?id=79221 video of the issue If I remember correctly this wasn't happening with Wine 10.13, basically now when resizing the Wine Regedit Window when using the Wayland driver makes it flicker a lot. I don't know if other apps are affected by this issue, I've tried resizing notepad and it doesn't flicker. -- 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 58200] New: winehq-repo for Fedora 42 is empty.
by WineHQ Bugzilla 21 Oct '25

21 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58200 Bug ID: 58200 Summary: winehq-repo for Fedora 42 is empty. Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: roidal(a)googlemail.com CC: dimesio(a)earthlink.net Distribution: --- I enabled the winehq-repo for Fedora 42 but it seems to be empty. winehq.repo contains following baseurl: baseurl=https://dl.winehq.org/wine-builds/fedora/42 -- 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 58711] New: DNF refuses to install or update winehq-staging, checksum sha256sum mismatch
by WineHQ Bugzilla 21 Oct '25

21 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58711 Bug ID: 58711 Summary: DNF refuses to install or update winehq-staging, checksum sha256sum mismatch Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: charlesthethobe(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- Since wine version 10.15 release I'm unable to perform a system update due to mismatching checksums between what the repo suggests and the actual rpm package. https://dl.winehq.org/wine-builds/fedora/42/x86_64/winehq-staging-10.15-1.1… This file's checksum is currently: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0 While it's expected to be: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfcbfea6 I tried running `# dnf clean metadata` to no avail. -- 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 58703] New: Fedora 42: Suddenly getting checksum errors
by WineHQ Bugzilla 21 Oct '25

21 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58703 Bug ID: 58703 Summary: Fedora 42: Suddenly getting checksum errors Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: johnny.jy.ooi(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- Recently, while trying to do the standard "dnf upgrade", my system sees updates for wine-staging and winehq-staging, but upon triggering the upgrade, I get checksum errors Total size of inbound packages is 226 MiB. Need to download 226 MiB. After this operation, 6 MiB extra will be used (install 1 GiB, remove 1 GiB). [1/2] winehq-staging-1:10.15-1.1.x86_64 100% | 144.6 KiB/s | 75.0 KiB | 00m01s >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc >>> Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfc [2/2] wine-staging-1:10.15-1.1.x86_64 0% | 3.3 MiB/s | 1.7 MiB | 00m01s >>> Not finished - interrupted by error: Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bd ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [2/2] Total 100% | 3.4 MiB/s | 1.8 MiB | 00m01s Failed to download packages Librepo error: Downloading successful, but checksum doesn't match. Calculated: 7d0e878400f211d295092216c6e2b30048336037ecc3de0211ac2530cadfd0b0(sha256) Expected: b1238f8bf020af8c31b6bdb817e50fffb27bee61129abbeb6c619066bfcbfea6(sha256) I've tried removing the winehq.repo, reimporting the repo key (https://dl.winehq.org/wine-builds/winehq.key), readding the repo according to the instructions, and doing "dnf clean" and it keep failing the checksum checks. I know there's been some issues with the repo in the past, do we have another similar 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

[Bug 57815] New: Splinter Cell (2002): crashes when changing game resolution when used with DXVK
by WineHQ Bugzilla 21 Oct '25

21 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=57815 Bug ID: 57815 Summary: Splinter Cell (2002): crashes when changing game resolution when used with DXVK Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: daniel.penalized(a)proton.me Distribution: ArchLinux Created attachment 78025 --> https://bugs.winehq.org/attachment.cgi?id=78025 output log When I change the game resolution via the settings menu, the game crashes. You can also crash when you start the game (right after the introductory video). Just change the game resolution via the SplinterCellUser.ini configuration file: Resolution=1920x1080 This behavior only happens when used with DXVK. It doesn't happen with WineD3D OpenGL (it's impossible to test with WineD3D Vulkan, as it completely breaks the look of the game). And of course, it doesn't happen with winex11.drv either. - The game was installed via CD-ROM and is up to date with the latest update (v1.3). - I use labwc/wlroots as WM. - Although I'm on Arch Linux, I compile wine manually with these options: ./configure --prefix=/usr --enable-archs=i386,x86_64 --enable-win64. So I'm using the new WoW64 mode, but this behavior also happens in normal 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 6

[Bug 58738] New: debian packages and wow64
by WineHQ Bugzilla 21 Oct '25

21 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58738 Bug ID: 58738 Summary: debian packages and wow64 Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: info(a)fernandolucas.info CC: dimesio(a)earthlink.net Distribution: --- So far it seems that the Debian packages are built without the wow64 support? Is this right? If so, in view of the wine 11 release, allowing the wow64 mode in the packages would be a great step forward. There is the step of the hardcoded dependency into the i386 packages. I have workaround this with a local dummy package, printf "Package: wine-devel-i386-dummy Version: %s Architecture: all Provides: wine-devel-i386 (= %s) Conflicts: wine-devel-i386 Replaces: wine-devel-i386 Maintainer: Dummy Maintainer <noreply(a)example.com> Description: Dummy package to satisfy wine-devel-i386 dependency This is a placeholder package that pretends to be wine-devel-i386. " "$VERSION" "$VERSION" > wine-devel-i386-dummy_${VERSION}/DEBIAN/control I install this package first, and then I can install wine-devel and winehq-devel without complaining about dependencies. It would be ideal if the repositories also provide something such as wine-devel-i386-dummy in the release process and document that by installing it, the win32 dependency is avoided. -- 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 6

[Bug 56184] New: - Elite Dangerous Data Interface)
by WineHQ Bugzilla 21 Oct '25

21 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=56184 Bug ID: 56184 Summary: - Elite Dangerous Data Interface) Product: Wine Version: 9.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de Distribution: --- Program does not start. https://github.com/EDCD/EDDI/issues/1976 It's a companion app for this game: https://appdb.winehq.org/objectManager.php?sClass=version&iId=37490 Console output without "winetricks dotnet472": [ERROR] FATAL UNHANDLED EXCEPTION: System.EntryPointNotFoundException: CreateInstalledObjectsInfo assembly:<unknown assembly> type:<unknown type> member:(null) at (wrapper managed-to-native) MS.Internal.PtsHost.UnsafeNativeMethods.PTS.CreateInstalledObjectsInfo(MS.Internal.PtsHost.UnsafeNativeMethods.PTS/FSIMETHODS&,MS.Internal.PtsHost.UnsafeNativeMethods.PTS/FSIMETHODS&,intptr&,int&) at MS.Internal.PtsHost.PtsCache.InitInstalledObjectsInfo (MS.Internal.PtsHost.PtsHost ptsHost, MS.Internal.PtsHost.UnsafeNativeMethods.PTS+FSIMETHODS& subtrackParaInfo, MS.Internal.PtsHost.UnsafeNativeMethods.PTS+FSIMETHODS& subpageParaInfo, System.IntPtr& installedObjects, System.Int32& installedObjectsCount) [0x0024c] in <d31f3a57049e4054ad4371f364def5bc>:0 at MS.Internal.PtsHost.PtsCache.CreatePTSContext (System.Int32 index, System.Windows.Media.TextFormattingMode textFormattingMode) [0x0003c] in <d31f3a57049e4054ad4371f364def5bc>:0 at MS.Internal.PtsHost.PtsCache.AcquireContextCore (MS.Internal.PtsHost.PtsContext ptsContext, System.Windows.Media.TextFormattingMode textFormattingMode) [0x000b0] in <d31f3a57049e4054ad4371f364def5bc>:0 at MS.Internal.PtsHost.PtsCache.AcquireContext (MS.Internal.PtsHost.PtsContext ptsContext, System.Windows.Media.TextFormattingMode textFormattingMode) [0x00035] in <d31f3a57049e4054ad4371f364def5bc>:0 at MS.Internal.PtsHost.PtsContext..ctor (System.Boolean isOptimalParagraphEnabled, System.Windows.Media.TextFormattingMode textFormattingMode) [0x0003c] in <d31f3a57049e4054ad4371f364def5bc>:0 at MS.Internal.PtsHost.StructuralCache.EnsurePtsContext () [0x0001b] in <d31f3a57049e4054ad4371f364def5bc>:0 at MS.Internal.PtsHost.StructuralCache.get_Section () [0x00001] in <d31f3a57049e4054ad4371f364def5bc>:0 at MS.Internal.PtsHost.FlowDocumentPage..ctor (MS.Internal.PtsHost.StructuralCache structuralCache) [0x00010] in <d31f3a57049e4054ad4371f364def5bc>:0 [...] When installing "dotnet472" there's a DirectX problem. This can be workarounded by using "winetricks dxvk". Console output without DXVK: 0150:fixme:d3d:wined3d_check_device_format_conversion output 00FD2060, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! 0150:fixme:d3d:wined3d_device_apply_stateblock Last Pixel Drawing Disabled, not handled yet. 0150:fixme:d3d:wined3d_check_device_format_conversion output 00FD20C4, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! 01bc:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. 0120:fixme:dwrite:dwritetextanalyzer_AnalyzeNumberSubstitution (0F753F80 0 100 01081FF0): stub 0150:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0150:err:d3dcompiler:D3DCompile2 Shader log: 0150:err:d3dcompiler:D3DCompile2 <anonymous>:144:1: E5000: syntax error, unexpected KW_PASS, expecting '}' 0150:err:d3dcompiler:D3DCompile2 0150:fixme:seh:WerRegisterMemoryBlock (FF9B2E60 6144) stub 0150:fixme:seh:WerRegisterMemoryBlock (FF9B2E10 4) stub 01bc:err:d3d:wined3d_context_gl_update_window Failed to get a device context for window 0F67ACA8. 01c0:err:d3d:wined3d_context_gl_update_window Failed to get a device context for window 0F717F48. -- 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 58819] New: Games crashing with WINE ntsync implementation but do not crash with Proton ntsync implementaion
by WineHQ Bugzilla 20 Oct '25

20 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58819 Bug ID: 58819 Summary: Games crashing with WINE ntsync implementation but do not crash with Proton ntsync implementaion Product: Wine-staging Version: 10.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chasbigham(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 79478 --> http://bugs.winehq.org/attachment.cgi?id=79478 console output of running wine-staging with retail world of warcraft launching world of warcraft(retail and MoP Classic) crashes when loading into the game from the character selection screen. This does not happen when using steam Proton to launch the game. This has happened since the release of wine/wine-staging 10.16 with the implementaion of the fleshed out ntsync. -- 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 58826] New: Winhq 10.17 seems to loose window focus??
by WineHQ Bugzilla 20 Oct '25

20 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58826 Bug ID: 58826 Summary: Winhq 10.17 seems to loose window focus?? Product: Wine Version: 10.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikes(a)guam.net Distribution: --- Just upgraded to 10.17 and notices a change in process. Seems to loose focus on the wine window? Click on something, and the try entering a character, and nothing happens. Have to click on top of wine window to get focus back, and then pressing key works. I've noticed the with Pegasus email 4.91, but not sure if it is only with that app, or with many apps. Another user posted an issue with an earlier wine issue with Pegasus. But think this is new with 10.17. I've also noticed, that it seems to also have the XFCE bottom panel pop up at same time. Generally, it hides when not in use, but should only pop back up when mouse is moved in that lower area, but in this case the mouse pointer is no where near that area?? Thanks. -- 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 39352] New: Soulbringer launcher doesn't paint buttons initially
by wine-bugs＠winehq.org 20 Oct '25

20 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=39352 Bug ID: 39352 Summary: Soulbringer launcher doesn't paint buttons initially Product: Wine-staging Version: unspecified Hardware: x86 URL: http://www.gog.com/game/soulbringer OS: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 52445 --> https://bugs.winehq.org/attachment.cgi?id=52445 screenshot (comparison) Originally reported in https://bugs.wine-staging.com/show_bug.cgi?id=96 When I start the game launcher, the 4 buttons in it (play,video,advanced,quit) are not drawn either in fullscreen or in virtual desktop mode. If I grab the launcher window and move it towards the edge of the screen, the buttons appear when that part of the window which holds the buttons moves beyond the screen. The launcher needs mfc42.dll. There is no demo version available. In the terminal: fixme:win:EnumDisplayDevicesW ((null),0,0x33d9f8,0x00000000), stub! fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. fixme:win:EnumDisplayDevicesW ((null),0,0x33d9f8,0x00000000), stub! fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled fixme:win:EnumDisplayDevicesW ((null),0,0x33ddd8,0x00000000), stub! The patch from staging to blame: https://github.com/wine-compholio/wine-staging/blob/master/patches/user32-D… The patch fixes bug #35652. wine-1.7.51-225-g3966aff Fedora 22 XFCE 4.12 XOrg 1.17.2 -- 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 11

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