wine-bugs July 2023

wine-bugs@winehq.org

1 participants
2803 discussions

[Bug 28678] New: DirectDraw primary buffer is obscured by transparent window
by wine-bugs＠winehq.org 01 Jul '23

01 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=28678 Bug #: 28678 Summary: DirectDraw primary buffer is obscured by transparent window Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: octavian.voicu(a)gmail.com Classification: Unclassified Created attachment 36852 --> http://bugs.winehq.org/attachment.cgi?id=36852 Screenshot showing the obscured dialog. When trying to exit from the game The Longest Journey (either via menu option or pressing Alt+F4), a dialog box is shown with Yes/No options. The application uses DirectDraw for rendering. The dialog box and mouse cursor are rendered on an offscreen surface (dialog has an image as the background and buttons use a custom implementation afaics), which is then blitted to the primary buffer (happens like this when you force single buffer mode; with double buffering it could be slightly different, but the overall effect is the same). The dialog is a parent of the main application window, uses the standard dialog window class (atom #32270 or 8000 in hex) and has the WS_POPUP and WS_EX_TRANSPARENT window styles. Window receives a WM_ERASEBKGND message, which is handled by the default dialog proc by painting the background in the standard window background color (gray in this case). When primary buffer is blitted to the d3d surface (ddraw_surface_update_frontbuffer which uses OpenGL), the rendering of the dialog is masked by the window boundaries and the gray rectangle remains. Dialog is interactable and you can click the buttons (if you can do that without seeing where the mouse is). The question is: how can we make the primary buffer draw over WS_EX_TRANSPARENT child windows, as it works on native? Removing the WS_EX_TRANSPARENT style from the dialog window (on runtime, using WinSpy++ 1.7) makes native's behavior identical to current wine behavior (only a gray rectangle is visible). -- 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 30

[Bug 54638] New: amazon music does not let wineserver quit (on shutdown)
by WineHQ Bugzilla 01 Jul '23

01 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=54638 Bug ID: 54638 Summary: amazon music does not let wineserver quit (on shutdown) Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: wine(a)stegm.de Distribution: --- amazon music does not let wineserver quit (on shutdown). That results in waiting for systemd to kill wineserver after 2 minutes. Or wineserver -k must be run as user before shutdown. -- 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 43054] New: FlightUnlimited II crashes during map load, Unhandled page fault on read access to 0x00000039 at address 0x41f87f ( thread 0009)
by wine-bugs＠winehq.org 01 Jul '23

01 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=43054 Bug ID: 43054 Summary: FlightUnlimited II crashes during map load, Unhandled page fault on read access to 0x00000039 at address 0x41f87f (thread 0009) Product: Wine Version: 2.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: haakobja(a)gmail.com Distribution: --- Created attachment 58220 --> https://bugs.winehq.org/attachment.cgi?id=58220 Log from FlightUnlimitedII I recently installed Flight Unlimited II through Wine. After successfully loading the menus (the game needs quartz.dll override, if not it crashes during intro), I tried to play. Only to experience an error stating "Unhandled page fault on read access to 0x00000039 at address 0x41f87f (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x00000039 in 32-bit code (0x0041f87f)" being thrown in my face. -- 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 9

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 2023