GNOME Bugzilla – Bug 699795
Can't get back to 'log out' screen after dealing with unsaved documents
Last modified: 2015-12-28 00:56:56 UTC
Say you have gedit open, with an unsaved document. You hit 'Power Off' from the user menu. It warns you that gedit has unsaved documents. You click on this message, which shows you gedit. You save or close the unsaved documents. The system works! Now what? Well, er, you can't find the dialog again. It seems to have disappeared. So you click on "Power Off" from the user menu again, and...nothing at all happens. Your options are to wait a while - some kind of timeout seems to eventually expire, and you can get back to the dialog - or run 'poweroff' from a console (which doesn't close GNOME down cleanly), and...that's about it. Kinda sucks. I'm using current Fedora 19, but this has been the case basically ever since the Shell-y shutdown dialog first appeared.
The dialog is supposed to reappear when you're closing gedit, I believe. And I'm sure this has worked at some point with the shell dialogs
(In reply to comment #0) > I'm using current Fedora 19, but this has been the case basically ever since > the Shell-y shutdown dialog first appeared. No, it definitively worked when the dialogs first appeared - in fact, I fail to reproduce the issue here (current master on top of F19). Is there anything interesting in ~/.cache/gdm/session.log?
mclasen: ah - that's the thing, I didn't think to close gedit. I just close the unsaved documents, and run Power Off again, or try to. Perhaps the design didn't cover the way I tried to use it? florian: hard to tell, as that file isn't timestamped and has all kinds of stuff in it. No idea when it all comes from.
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. In my case, log out works properly only if no application has an inhibitor. So if I open gedit and type a couple characters, log out will not work immediately (it will actually work eventually, but not until a minute or so later). Without gedit open, log out works fine. But logging in again almost never works, regardless. It seems related to Red Hat #1222157. *** This bug has been marked as a duplicate of bug 750508 ***
Well, I went to test this on current Rawhide, and after typing some random characters into gedit and hitting the power button in the user menu (or whatever we're calling that menu now) I didn't get a warning of unsaved data at all - it just shut the system down and lost my changes - so it's a bit hard to tell if it's still happening as I originally described. 750508 sounds similar but without the wrinkle of having any unsaved data, so it *may* be the same thing, but it's difficult to tell for sure.