http://bugs.winehq.org/show_bug.cgi?id=18439
Summary: Crash dialog appears underneath fullscreen (D3D9?) apps Product: Wine Version: 1.1.21 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: roothorick@new.rr.com
Any game, be it Oblivion, be it some random free MMO, be it whatever, if it's fullscreen, and it crashes, the "encountered a problem and needs to close" dialog appears UNDERNEATH the game, unclickable, so you have to go to another window / X server and manually kill it to get back to normal. Obviously this kinda kills the debugger too. Using a virtual desktop doesn't help, because the dialog appears INSIDE the virtual desktop, UNDERNEATH the game.
I know this is happening with D3D9 games, haven't really tested outside of that.
http://bugs.winehq.org/show_bug.cgi?id=18439
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |minor
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-12 01:32:38 --- That's a problem with WMs which insist to put fullscreen windows on top. Since this behaviour is visible only if a fullscreen app crashes the severity is minor.
http://bugs.winehq.org/show_bug.cgi?id=18439
--- Comment #2 from Ben Anderson roothorick@new.rr.com 2009-05-12 02:39:20 --- This has nothing to do with WMs. It happens if the WM is forbidden from controlling the windows, it happens on an X server where no WM is running, and as you would already know if you had bothered to read my description, it even happens when the application is running inside a virtual desktop. (For the record, I've tested all three with the same result -- frozen fullscreen app on top of unclickable window.)
http://bugs.winehq.org/show_bug.cgi?id=18439
--- Comment #3 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-12 02:49:13 --- Both virtual desktop and no WM cases are not interesting, window management in Wine has known windows Z order problems in that cases. It's not clear to me from your comments have you tried with a WM then.
http://bugs.winehq.org/show_bug.cgi?id=18439
--- Comment #4 from Ben Anderson roothorick@new.rr.com 2009-05-12 08:31:09 --- I have tested it with fluxbox. Are there any others you want me to test?
http://bugs.winehq.org/show_bug.cgi?id=18439
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-12 09:29:23 --- (In reply to comment #4)
I have tested it with fluxbox. Are there any others you want me to test?
Gnome and KDE are more widely used/tested, so it's worth to test with (one of) them as well.
http://bugs.winehq.org/show_bug.cgi?id=18439
--- Comment #6 from H. Verbeet hverbeet@gmail.com 2009-05-12 09:37:29 --- (In reply to comment #5)
Gnome and KDE are more widely used/tested, so it's worth to test with (one of) them as well.
This does happen with at least KDE 3.5.9 as well.
http://bugs.winehq.org/show_bug.cgi?id=18439
--- Comment #7 from Austin English austinenglish@gmail.com 2009-05-12 10:57:11 --- What happens if a game crashes on windows? IIRC, it took careful ATL+TAB'ing to get to the dialog.
http://bugs.winehq.org/show_bug.cgi?id=18439
--- Comment #8 from Ben Anderson roothorick@new.rr.com 2009-06-19 22:41:49 --- (In reply to comment #7)
What happens if a game crashes on windows? IIRC, it took careful ATL+TAB'ing to get to the dialog.
If you want to belabor the point...
Even on Windows, the crash parachute doesn't actually come out until the dialog is confirmed; until then, you have a fullscreen, crashed app blocking you from doing much of anything at all. Therefore, the dialog must ALWAYS appear onscreen somewhere, and the mouse made free to click on it (or at a minimum, give it keyboard focus). At least, in theory. Practice? I really don't know. So, write up a quick program that engages a fullscreen D3D9 context and promptly crashes, and have people test it on various Windows / hardware combinations to get a more solid idea of *actual* Windows behavior.
http://bugs.winehq.org/show_bug.cgi?id=18439
pierre geier bloodywing@neocomy.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bloodywing@neocomy.net
--- Comment #9 from pierre geier bloodywing@neocomy.net 2009-07-26 04:33:56 --- I tested it with fluxbox, it happens there too. But you can give the crash dialog a "always on top"-setting. Alt+Tab works too.
http://bugs.winehq.org/show_bug.cgi?id=18439
Andrew Clapperton andrew_clapperton@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #10 from Andrew Clapperton andrew_clapperton@hotmail.com 2010-03-17 16:26:57 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=18439
Xavier Vachon xvachon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon@gmail.com
--- Comment #11 from Xavier Vachon xvachon@gmail.com 2010-07-24 22:28:30 --- What is the expected behaviour to determine if this is fixed? Most of the DX9 games I play in full screen whom crash in Windows 7 have their crash dialog underneath the app as well, I need to CTRL+ALT+DELETE and activate the task manager to kill the application.
http://bugs.winehq.org/show_bug.cgi?id=18439
Javier Kohen jkohen@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jkohen@users.sourceforge.ne | |t
--- Comment #12 from Javier Kohen jkohen@users.sourceforge.net 2010-11-01 07:51:53 CDT --- One more data point. I'm using Metacity (composite manager mode disabled) and I also see this issue. It's not just a matter of z-order, because moving the crash dialog to a different virtual workspace still doesn't allow me interact with it and the dialog's contents don't repaint properly. The dialog remains in that condition until I kill the game, in the case of Oblivion by issuing "pkill Oblivion" from the command-line. Once the game is gone the dialog works as expected.
http://bugs.winehq.org/show_bug.cgi?id=18439
Michal Suchanek hramrach@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hramrach@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=18439
--- Comment #13 from butraxz@gmail.com 2013-09-15 07:50:45 CDT --- This ticket has not been updated for over 900 days. Development recommends to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed. If you are no longer able to put effort to this ticket, you can abandon it.
Is this still an issue with 1.7.2 or higher ?
https://bugs.winehq.org/show_bug.cgi?id=18439
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |ABANDONED
--- Comment #14 from Austin English austinenglish@gmail.com --- (In reply to butraxz from comment #13)
This ticket has not been updated for over 900 days. Development recommends to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed. If you are no longer able to put effort to this ticket, you can abandon it.
Is this still an issue with 1.7.2 or higher ?
Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=18439
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org