After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 656813 - The gnome-shell crash screen prevents users from cleanly terminating applications
The gnome-shell crash screen prevents users from cleanly terminating applicat...
Status: RESOLVED OBSOLETE
Product: gnome-session
Classification: Core
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
: 656706 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-08-18 10:50 UTC by Tassilo Horn
Modified: 2021-06-14 18:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tassilo Horn 2011-08-18 10:50:14 UTC
Whenever the gnome-shell crashes, you get that "Oops"/"Oh no!" screen, where the only thing the user is able to do is [Logout].  (It seems, in 3.2 he might also be able to deactivate extensions there: http://i.imgur.com/ETvfg.png)

The problem with that screen is that although the shell crashed, X11 and the user's apps are still running fine and probably contain unsaved data.  But that fullscreen crash dialog prevents users from shutting down their apps cleanly before logging out, causing data loss for all applications that don't auto-save.  (And for the auto-saving apps, you'd better wait some minutes before logging out now...)

It would be much better if that dialog was just a small dialog positioned somewhere where it doesn't overlay the user's apps (bottom-right corner or so).
Comment 1 Tassilo Horn 2011-08-25 07:01:49 UTC
Maybe a good UI would be to stick to the full-screen dialog but add some kind of minimize button.  When pressed, you get back to the desktop (or what's left over) and some logout button is shown at some corner.

Then the user can shutdown his apps cleanly (at least on the current desktop) and logout thereafter.
Comment 2 Jasper St. Pierre (not reading bugmail) 2011-08-25 09:59:40 UTC
(In reply to comment #1)
> Maybe a good UI would be to stick to the full-screen dialog but add some kind
> of minimize button.  When pressed, you get back to the desktop (or what's left
> over) and some logout button is shown at some corner.
> 
> Then the user can shutdown his apps cleanly (at least on the current desktop)
> and logout thereafter.

When the crash dialog appears, it's only supposed to appear after the Shell has crashed multiple times. So we can't really let the user "shutdown their apps" without a WM running. Maybe we could launch metacity in that case.
Comment 3 Tassilo Horn 2011-08-25 10:38:30 UTC
> When the crash dialog appears, it's only supposed to appear after the Shell has
> crashed multiple times. So we can't really let the user "shutdown their apps"
> without a WM running. Maybe we could launch metacity in that case.

Most apps have a File menu containing Save/Quit entries and a toolbar with a Save button.  That way, a user could at least save his work and terminate his applications on the *current* workspace.  Clearly, that's not ideal but better than loosing all his unsaved work.
Comment 4 Jean-François Fortin Tam 2012-10-25 20:39:40 UTC
*** Bug 656706 has been marked as a duplicate of this bug. ***
Comment 5 Francois Gouget 2013-02-06 16:08:47 UTC
(In reply to comment #2)
[...]
> When the crash dialog appears, it's only supposed to appear after the Shell has
> crashed multiple times. So we can't really let the user "shutdown their apps"
> without a WM running. Maybe we could launch metacity in that case.

I'm using metacity as my window manager and I get this error quite regularly because Wine's test suite causes metacity to crash (see bug 693264).

Fortunately I discovered that there is actually a way to dismiss the "Oops"/"Oh no!" screen: hold the left 'Windows' key and right-click on the background. This brings up a dialog which overs to minimize the windows. Do that and then, out of sight, out of mind. This leaves me with a fully usable desktop that I routinely still use for days. Of course it still has a window manager (metacity).

That suggests that it could make sense to add a 'dismiss without logging me out' button to deal with this sort of situation; or that the code that fires up this "Oops"/"Oh no!" screen should be fixed so it does not needlessly cause users to lose all their data.
Comment 6 André Klapper 2021-06-14 18:23:08 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of gnome-session, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-session/-/issues/

Thank you for your understanding and your help.