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 733051 - Interrupted shutdown cannot be retried
Interrupted shutdown cannot be retried
Status: RESOLVED DUPLICATE of bug 750508
Product: gnome-shell
Classification: Core
Component: general
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-07-11 10:54 UTC by Reuben Thomas
Modified: 2015-12-27 23:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Reuben Thomas 2014-07-11 10:54:34 UTC 
If I choose to shutdown from the GNOME Shell menu, and then an application complains, interrupting the process, selecting shutdown from the menu again has no effect.
Comment 1 André Klapper 2014-07-11 11:08:22 UTC 
What is "complains, interrupting the process" exactly? 
Strings from dialogs welcome.
Comment 2 Reuben Thomas 2014-07-11 11:57:55 UTC 
Sorry for my lack of precision. It seems that in fact my problem only occurs with certain apps, in particular VirtualBox (but the problem still manifests as an oddity in GNOME Shell, hence my filing a bug against gnome-shell, not Virtualbox!).

Here's what I do:

1. Start up Virtualbox, and start a VM running.

2. Click the power button in the main GNOME Shell menu. Notice that Virtualbox has popped up a dialog for saving the VM state underneath, so click "Cancel" in the GNOME Shell restart dialog.

3. Click Save in the Virtualbox dialog. Virtualbox saves the VM state and exits.

4. Click the power button in the main GNOME Shell menu. Nothing happens…and then a minute later the machine shuts down. No dialog was shown.
Comment 3 Reuben Thomas 2014-07-11 12:00:48 UTC 
By the way, when I said "then a minute later the machine shuts down", that sometimes does happen, and sometimes doesn't.

If instead I perform the experiment with unsaved data in GEdit, for example, then GNOME Shell prompts me with the information that I appear to have unsaved data, and if I click Cancel and then close GEdit, and then click the power button again in the GNOME Shell menu, the dialog is shown again as I would expect. Hence, something about Virtualbox seems to be confusing GNOME Shell. I'm using Virtualbox 4.3.10 as shipped in Ubuntu 14.04, but I've been noticing this problem for over a year.
Comment 4 Christian Stadelmann 2015-05-30 18:07:25 UTC 
This looks like a duplicate of #699795 to me.
Comment 5 Reuben Thomas 2015-05-30 18:12:38 UTC 
The symptoms described at #699795 are exactly those I had, only with gedit instead of Virtualbox. However, as I reported in comment #3, with GEdit it works fine for me, whereas in #699795 the reporter says GEdit has the same problem I had with Virtualbox.
Comment 6 Michael Catanzaro 2015-12-27 23:53:26 UTC 
I'm going to dup this against #750508... I think there may be multiple underlying issues here, but I don't see value in keeping open multiple "log out doesn't work" bugs without understanding fully the differences between the cases.

*** This bug has been marked as a duplicate of bug 750508 ***