wine-bugs July 2024

wine-bugs@winehq.org

1 participants
1483 discussions

[Bug 56958] New: ChessBase 17 crashes after splash screen
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56958 Bug ID: 56958 Summary: ChessBase 17 crashes after splash screen Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)brobston.com CC: rbernon(a)codeweavers.com Regression SHA1: 27f63ff1cd7daeb47b0c396b5c842e73a3a34584 Distribution: Ubuntu Created attachment 76774 --> https://bugs.winehq.org/attachment.cgi?id=76774 Log from launching ChessBase 17 at the first bad commit This is a recent regression in which ChessBase 17 crashes after its splash screen. I ran a regression test. Log (with WINEDEBUG=warn+all) from the first bad revision is attached. -- 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 56957] New: CEF application (BSG Launcher) freezes on mouse hover action
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56957 Bug ID: 56957 Summary: CEF application (BSG Launcher) freezes on mouse hover action Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madbyte(a)tuta.io Distribution: --- Created attachment 76773 --> https://bugs.winehq.org/attachment.cgi?id=76773 error log, used WINEDEBUG=+seh+debugstr Starting with Wine 9.11, the BSG Launcher (CEF application) freezes as soon as the mouse enters the window of the application & the process has to be killed forcefully to close the window. On Wine 9.10 the launcher works as expected. Only observable difference in the log output between 9.10 and 9.11 is this err: 0114:err:virtual:virtual_setup_exception nested exception on signal stack addr 0x7d1bec533173 stack 0x7ffcee80 -- 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 56910] New: Sysinternals的ZoomIt程序的部分功能无法使用。
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56910 Bug ID: 56910 Summary: Sysinternals的ZoomIt程序的部分功能无法使用。 Product: Wine Version: unspecified Hardware: x86-64 OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: luzixuan2022(a)126.com Created attachment 76731 --> https://bugs.winehq.org/attachment.cgi?id=76731 ZoomIt.exe为程序的可执行文件 ZoomIt程序的Draw和Zoom功能无法使用——使用时屏幕会黑屏，所以无法按预期使用。程序见附件。 -- 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 57006] New: Unhandled exception: page fault trying to run Midtown Madness 2
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=57006 Bug ID: 57006 Summary: Unhandled exception: page fault trying to run Midtown Madness 2 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: hillpeter723(a)gmail.com Distribution: --- Created attachment 76843 --> https://bugs.winehq.org/attachment.cgi?id=76843 Error report: Unhandled exception: page fault trying to run Midtown2 I encountered the Program Error dialog while trying to run Midtown Madness 2. BTW, the installation process completed. Unhandled exception: page fault on read access to 0x00004738 in wow64 32-bit code (0x0040e41a). -- 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 57000] New: Inspera Exam Portal SSO login (iceworm.exe) window crashes
by WineHQ Bugzilla 26 Jul '24

26 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=57000 Bug ID: 57000 Summary: Inspera Exam Portal SSO login (iceworm.exe) window crashes Product: Wine Version: 9.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tuxifan(a)posteo.de Distribution: --- Created attachment 76839 --> https://bugs.winehq.org/attachment.cgi?id=76839 iceworm.exe crash report While Wine is surprisingly able to pass **all** system checks, the SSO login fails. Follow these instructions to reproduce: https://www.ltu.se/en/student-web/your-studies/examination/digital-exam-ins… To be clear, I wouldn't use Wine to take an exam, EVER. Just gave this a try as a joke and thought it might be worth fixing. -- 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 32515] New: Warhammer 40,000: Space Marine (Steam) fails to start
by wine-bugs＠winehq.org 26 Jul '24

26 Jul '24

http://bugs.winehq.org/show_bug.cgi?id=32515 Bug #: 32515 Summary: Warhammer 40,000: Space Marine (Steam) fails to start Product: Wine Version: 1.5.20 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 42894 --> http://bugs.winehq.org/attachment.cgi?id=42894 plain terminal output On startup the game shows a black screen for a few seconds and audio from the intro video can be heard for 0.5-1 second, then the game's own bug reporting tool (Bugsplat) is popping up: "A problem has been encountered and the program needs to close". No backtrace from Wine is generated. A demo version is available on Steam, but I couldn't test it as I have the full version. http://store.steampowered.com/app/55150/ Steam installs MSVC++ 2005 runtime libraries and various DirectX components the first time you start the game. Disabling gameoverlayrenderer in winecfg doesn't help. I tested this bug with Wine 1.2.3, 1.4.1, 1.5.20. Fedora 17 x86 Nvidia 250 / driver 304.64 X.Org X Server 1.12.4 Alsa 1.0.26 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 111

[Bug 48525] New: 0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
by WineHQ Bugzilla 26 Jul '24

26 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=48525 Bug ID: 48525 Summary: 0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: cagnulein(a)gmail.com Distribution: --- On a commercial application written on .NET 2.0 i have a crash that occurs randomly every few days. I put the +seh debug here. I have 2 questions: 1) my +seh log file is full of 0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0048:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223 ip=7b43e223 tid=0048 0048:trace:seh:raise_exception info[0]=00000041 0048:trace:seh:raise_exception info[1]=0d061dd8 0048:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0733ef20 edx=0733efd0 esi=00000041 edi=40010006 0048:trace:seh:raise_exception ebp=0733ef78 esp=0733eef4 cs=300023 ds=002b es=f7d7002b fs=006b gs=73c0063 flags=00000212 0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef0c edx=0733efd8 esi=0733efd8 edi=7b48ace0 0048:trace:seh:__regs_RtlUnwind ebp=0733eac8 esp=0733eaa8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 it's a problem of my application? Of wine gdiplus implementation? 2) In the meanwhile i'm trying with "winetricks gdiplus": what you think about this +seh trace? 0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef0c edx=0733efd8 esi=0733efd8 edi=7b48ace0 0048:trace:seh:__regs_RtlUnwind ebp=0733eac8 esp=0733eaa8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0048:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223 ip=7b43e223 tid=0048 0048:trace:seh:raise_exception info[0]=00000041 0048:trace:seh:raise_exception info[1]=0d061dd8 0048:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0733ef20 edx=0733efd0 esi=00000041 edi=40010006 0048:trace:seh:raise_exception ebp=0733ef78 esp=0733eef4 cs=300023 ds=002b es=f7d7002b fs=006b gs=73c0063 flags=00000212 0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef0c edx=0733efd8 esi=0733efd8 edi=7b48ace0 0048:trace:seh:__regs_RtlUnwind ebp=0733eac8 esp=0733eaa8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0048:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223 ip=7b43e223 tid=0048 0048:trace:seh:raise_exception info[0]=0000003e 0048:trace:seh:raise_exception info[1]=0d0719e8 0048:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0733ef50 edx=0733f000 esi=0000003e edi=40010006 0048:trace:seh:raise_exception ebp=0733efa8 esp=0733ef24 cs=0023 ds=34002b es=733002b fs=7dd9006b gs=7330063 flags=00000216 0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef3c edx=0733f008 esi=0733f008 edi=7b48ace0 0048:trace:seh:__regs_RtlUnwind ebp=0733eaf8 esp=0733ead8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0009:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223 ip=7b43e223 tid=0009 0009:trace:seh:raise_exception info[0]=00000046 0009:trace:seh:raise_exception info[1]=0d068440 0009:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0032e720 edx=0032e7d0 esi=00000046 edi=40010006 0009:trace:seh:raise_exception ebp=0032e778 esp=0032e6f4 cs=0023 ds=34002b es=002b fs=006b gs=0063 flags=00000212 0009:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0009:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0009:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0032e70c edx=0032e7d8 esi=0032e7d8 edi=7b48ace0 0009:trace:seh:__regs_RtlUnwind ebp=0032e2c8 esp=0032e2a8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0009:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 0009:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash Fatal,Program[1:MainThread]: System.Runtime.InteropServices.SEHException: External component has thrown an exception. at System.Drawing.SafeNativeMethods.SelectObject(HandleRef hdc, HandleRef obj) at System.Drawing.BufferedGraphicsContext.DisposeDC() at System.Drawing.BufferedGraphicsContext.ReleaseBuffer(BufferedGraphics buffer) at System.Drawing.BufferedGraphics.Dispose(Boolean disposing) at System.Drawing.BufferedGraphics.Dispose() at System.Windows.Forms.Control.WmPaint(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Label.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) I can't share the application because it's not free, but if you need more information i will try to get them. 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 6

[Bug 57001] New: Compute shader change causes Affinity Photo 2 to crash on start up
by WineHQ Bugzilla 26 Jul '24

26 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=57001 Bug ID: 57001 Summary: Compute shader change causes Affinity Photo 2 to crash on start up Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: topgamer7(a)gmail.com CC: gmascellani(a)codeweavers.com Regression SHA1: c319b874669450cc17ebe9a7f459a17b86cdcddb Distribution: ArchLinux Created attachment 76840 --> https://bugs.winehq.org/attachment.cgi?id=76840 The two patches cat'd together commit c319b874669450cc17ebe9a7f459a17b86cdcddb (HEAD) Author: Giovanni Mascellani <...> Date: Tue Mar 19 12:25:28 2024 +0100 wined3d: Compile the clear compute shaders at runtime. Affinity Photo 2 can no longer start after the above commit was made. I narrowed this down by bisecting and rebuilding wine. The application no longer starts. It has a splash screen, and was not even getting to that point. System details: OS: Manjaro Linux x86_64 CPU: AMD Ryzen 9 6900HS with Radeon Graphics (16) @ 4.935GHz GPU: AMD ATI Radeon 680M GPU: AMD ATI Radeon RX 6650 XT / 6700S / 6800S Window manager: Sway, however the application is run using xwayland. Extra configure flags: ../configure \ --prefix='/usr' \ --libdir='/usr/lib' \ --with-x \ --enable-win64 \ --with-wayland \ -C Running affinity photo requires 1. winetricks dotnet48 corefonts 2. You do not need a license to reproduce. 3. some off mainline commits: commit a3c1e73023aa98c6665383096df34dfd86f33108 Author: James McDonnell <> Date: Sun Feb 26 12:56:24 2023 -0800 shell32/iconcache: Call LoadIconW commit 07dd01d8346cba084528ddf6e375641337f876f0 Author: James McDonnell <> Date: Mon Nov 21 21:26:19 2022 -0800 wintypes: Hack in some calls to RoResolveNamespace -- 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 56911] New: System.Windows.Forms: ContextMenuStrip -> SourceControl property is null
by WineHQ Bugzilla 26 Jul '24

26 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56911 Bug ID: 56911 Summary: System.Windows.Forms: ContextMenuStrip -> SourceControl property is null Product: Mono Version: main Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: System.Windows.Forms Assignee: wine-bugs(a)winehq.org Reporter: maxmueller485(a)web.de CC: madewokherd(a)gmail.com Distribution: --- Created attachment 76732 --> https://bugs.winehq.org/attachment.cgi?id=76732 A small sample project containing nothing else but a cs source file, a csproj file and the sln file for this project Hello, I've stumbled over an issue in your current System.Windows.Forms implementation which did not affect the official version of Mono from the Mono Project. The problem affects the ContextMenuStrip class which usually has a SourceControl property. In WinForms there is a PictureBox widget which can have a context menu (ContextMenuStrip) with its elements (ToolStripMenuItem). The property SourceControl would normally provide you with information about the element that actually owns this context menu (useful if you have multiple PictureBoxes) - it actually did until upstream version 6.12.0.200 (the final release I could get from Mono's official repository for Ubuntu). Now when I take the mono implementation from your repository and compile it locally to run my project, the SourceControl will always be null which is really annoying. To better understand my problem, I've attached a zip compressed archive of a sample project I created to demonstrate the issue. The program consists of a small WinForms window with a single PictureBox in it. Right-click on the picture box will open up a ContextMenuStrip with a single ToolStripMenuItem in it ("Get underlying control"). When you click on this item, the method ToolStripMenuItem_Click will be executed and runs GetUnderlyingControl to determine the type of the control. On Windows .NET Framework and the old Mono implementations, the behavior is consistent (MessageBox shows "Underlying Control: pictureBox"). In your current Mono build, the MessageBox will show "No underlying control found" -- 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 12

[Bug 55818] New: 32-bit game Dark Age of Camelot slow memory leak leads to crash since WINE 7.4
by WineHQ Bugzilla 25 Jul '24

25 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=55818 Bug ID: 55818 Summary: 32-bit game Dark Age of Camelot slow memory leak leads to crash since WINE 7.4 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: tmwine(a)pertho.net Distribution: --- I've bisected a bug relating to a possible memory leak in wined3d. I've been playing an old game (Dark Age of Camelot) for years now on free servers, but I noticed there is a slow memory leak as it runs. I ran 'top' and watched the RES memory creep up to 1.0 GB and then hit about 1.2-1.3 GB before the game crashes. On WINE 8 this issue seems to persist as well. So I went back and bisected the bug and it occurs between WINE 7.3 and 7.4. In 7.3, I don't get the memory leak and the game plays for hours, but in 7.4 I get the memory leak. I've narrowed it down to this commit: https://gitlab.winehq.org/wine/wine/-/commit/ee12556960e30fc22f276d2de2833e… It might have to do with the code change in the function wined3d_context_gl_destroy_bo that introduced this. Happy to try any patches to test with against latest WINE 8.x tree. Thanks, Tom -- 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 43

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 July 2024