wine-bugs July 2024

wine-bugs@winehq.org

1 participants
1151 discussions

[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 57002] New: touch screen does not click the right location for surface pro
by WineHQ Bugzilla 26 Jul '24

26 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=57002 Bug ID: 57002 Summary: touch screen does not click the right location for surface pro Product: Wine Version: unspecified 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: --- i try to touch but it can only select the item, while I cannot click 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 1

[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

[Bug 56269] New: Systray icons do not scale based on Cinnamon settings
by WineHQ Bugzilla 25 Jul '24

25 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56269 Bug ID: 56269 Summary: Systray icons do not scale based on Cinnamon settings Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bq74stlxvkpb(a)opayq.com Distribution: --- Created attachment 75987 --> https://bugs.winehq.org/attachment.cgi?id=75987 Systray icons do not scale based on Cinnamon settings As the summary says. Open the attachment and guess which two systray icons do not scale with the taskbar height. By the way, the scaling size for all elements is set at 100% (so this isn't about DPI scaling and such). I do realize that .ico files are used, and those have several predefined sizes inside, but a nearest neighbour scaling to the size of other icons would help a lot and it would look a lot less silly. NAME="Linux Mint" VERSION="21.3 (Virginia)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Linux Mint 21.3" VERSION_ID="21.3" HOME_URL="https://www.linuxmint.com/" SUPPORT_URL="https://forums.linuxmint.com/" BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/" PRIVACY_POLICY_URL="https://www.linuxmint.com/" VERSION_CODENAME=virginia UBUNTU_CODENAME=jammy -- 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 56998] New: AMD frame latency meter doesn't work (dxgi_output_DuplicateOutput is a stub)
by WineHQ Bugzilla 25 Jul '24

25 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56998 Bug ID: 56998 Summary: AMD frame latency meter doesn't work (dxgi_output_DuplicateOutput is a stub) Product: Wine Version: 9.13 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- The terminal output is very short, so I'm going to break the rule and just paste it: 0134:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0134:fixme:dxgi:dxgi_output_DuplicateOutput iface 00007FFFFF19D650, device 00007FFFFF1A1BB0, output_duplication 00007FFFFF155580 stub! 0134:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet Frame latency meter v1.0.0 Error [3]: m_capture->InitCapture failed Error [3]: Unexpected error[80004001]: Failed to get duplicate output in DUPLICATIONMANAGER press any key to continue $ sha256sum flm_v1.0.zip 8492aabdf0b9f3b735670b2a004ee947e1f60290708b56033e91d3408e2300cc -- 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 56988] New: wineserver: server/sock.c:1342: sock_poll_event: Assertion `sock->obj.ops == &sock_ops' failed.
by WineHQ Bugzilla 24 Jul '24

24 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56988 Bug ID: 56988 Summary: wineserver: server/sock.c:1342: sock_poll_event: Assertion `sock->obj.ops == &sock_ops' failed. Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: benoit.arciuolo(a)ubiwan.net Distribution: --- hello, my wine crash with this error wineserver: server/sock.c:1342: sock_poll_event: Assertion `sock->obj.ops == &sock_ops' failed. do you have a idea? 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 7

[Bug 44962] New: Smart Guard no run
by wine-bugs＠winehq.org 23 Jul '24

23 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=44962 Bug ID: 44962 Summary: Smart Guard no run Product: Wine-staging Version: 3.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: terapy-session(a)bk.ru CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 61074 --> https://bugs.winehq.org/attachment.cgi?id=61074 averia petch, l2.exe log Smart Guard does not work and cannot work around it. Checked on different servers, but I give a log from the server Averia.ws -- 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 18

[Bug 56941] New: EA app fails to launch game if total size of environment variables exceeds ~32000 characters
by WineHQ Bugzilla 23 Jul '24

23 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56941 Bug ID: 56941 Summary: EA app fails to launch game if total size of environment variables exceeds ~32000 characters Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)gmail.com Distribution: --- ### Steps to reproduce Preparation: - Have the EA app installed: https://origin-a.akamaihd.net/EA-Desktop-Client-Download/installer-releases… - I installed it through Bottles, which installs the following Winetricks dependencies: https://github.com/bottlesdevs/programs/blob/main/Games/eaclient.yml Reproducing: - Set a very long environment variable, before launching the EA app - From the EA app, launch any game - Alternatively, execute the game directly, it will automatically launch the EA app to launch the game - If you don't have any game, "The Sims 4" is free - The game won't launch, an error popup from the EA app will appear (see notes) ### Notes It doesn't matter whether these ~32000 characters are from a single environment variable, or from the combination of many of them. I didn't test on Windows. It may be impossible to test there, since the environment block there has a limit of 32760 characters (which may probably be the reason for this issue in the first place). I say "~32000", because the issue starts occurring a little before 32760 characters. However, my counting method was imprecise (I simply typed `set` in `wine cmd`, then counted the characters), and there's also the fact that the EA app also sets its own environment variables. The issue also occurs with games bought from Steam (thus launched with Proton) that also have to go through the EA app (thanks EA). This issue existed before, and the weird thing is that the error popup from the EA app is different from some time ago (I imagine due to the app being updated). Before it was: "Failed to launch game. An error on our end caused the launch to fail. Try again a little later." Now it's: "The game hasn't released yet" (which is obviously untrue). Is it a stack overflow issue? Logs obtained with `WINEDEBUG=EADesktop.exe:+relay` are too big to attach, even compressed. Let me know what `WINEDEBUG` parameters I should use instead. I can see that the app calls `GetEnvironmentStringsW`, shortly followed by a `WideCharToMultiByte` for each variable (key and value separately). This is done three times. -- 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

Jump to page:

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