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 788972 - logout and restart/shutdown dialog doesn't work sometimes
logout and restart/shutdown dialog doesn't work sometimes
Status: RESOLVED DUPLICATE of bug 788542
Product: gnome-shell
Classification: Core
Component: general
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-10-14 02:44 UTC by dylnmc
Modified: 2017-10-14 02:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description dylnmc 2017-10-14 02:44:40 UTC
Sometimes after I log in, if these system dialog windows that pop up after I run `gnome-session-quit --logout`, for instance, don't allow keyboard interaction. That is to say, Escape does not Cancel the action and close the window and tab does not cycle through the options (and, of course, Return does not select any of the options).

So, if I (or someone else) did not have a mouse, then the only option would be to go to another tty and run `pkill gnome`  because there is no way to either return to gnome-shell without the dialog or logout or do whatever it is you were trying to do (logout/restart/shutdown), and that is fairly bizarre and annoying.

I am using `OSX-Arc-Shadow` Applications theme and `Gnome-OSX-Dark-Shell` Shell theme, and I also have `redshift-gtk` running. Also, I'm on arch (fresh install). I don't think these would have any effect on this, but the more info the better. Also, I log in with startx not gdm.

Another issue that has been following me (even on different installs) is that sometimes when I login, my keyboard shortcuts do not work. I feel like it is related somehow.

Finally, someone on freenode found this: https://git.gnome.org/browse/gnome-shell/commit/?id=0b02f757f862d0d292e57f68179440f2a0bd572c

Since it works sometimes, I don't think that git commit is relavent, but *meh*

Thanks,
dylnmc

ps, if I have submitted this in the wrong place (first bug report), then hopefully you all can figure out where it should go and handle it internally, but let me know if I need to do anything or can help. Thanks again.
Comment 1 Florian Müllner 2017-10-14 02:50:25 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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