After an evaluation, the migration from Bugzilla to GitLab is ongoing. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore. Some older issues are still tracked here (until migrated to Gitlab).
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 708218 - “Enter a Command” dialog stays visible when the screen locker starts
“Enter a Command” dialog stays visible when the screen locker starts
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: lock-screen
3.9.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
:
: 703679 708313 722967 (view as bug list)
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2013-09-17 10:10 UTC by Mike FABIAN
Modified: 2017-04-24 19:23 UTC (History)
7 users (show)

See Also:
GNOME target: 3.10
GNOME version: ---

Attachments
enter-command-dialog-stays-visible-on-screen-locker.png (117.70 KB, image/png)
2013-09-17 10:10 UTC, Mike FABIAN 		  Details
main: Close runDialog as necessary on session mode changes (1.14 KB, patch)
2013-09-18 17:53 UTC, Florian Müllner 		committed Details | Review
View All Add an attachment (proposed patch, testcase, etc.)

Description Mike FABIAN 2013-09-17 10:10:30 UTC 
Created attachment 255081 [details]
enter-command-dialog-stays-visible-on-screen-locker.png

gnome-shell-3.9.91-1.fc20.x86_64

On Fedora  20 Alpha RC2:

When I open the “Enter a Command” dialog with Alt+F2 but then just
wait until the screen lock starts, the “Enter a Command” dialog is
still visible on top of the screen lock. I can enter a command,then
unlock the screen and see that the command has been executed.
Comment 1 Matthias Clasen 2013-09-17 23:31:22 UTC 
hmm, ugly
Comment 2 Florian Müllner 2013-09-18 16:12:20 UTC 
*** Bug 708313 has been marked as a duplicate of this bug. ***
Comment 3 Florian Müllner 2013-09-18 17:53:08 UTC 
Created attachment 255237 [details] [review]
main: Close runDialog as necessary on session mode changes

We already do this for looking glass, but it makes even less sense
for the normal run dialog - if a mode sets runDialog to false, the
intention is to not allow executing aribitrary commands.
Comment 4 Jasper St. Pierre (not reading bugmail) 2013-09-18 18:00:04 UTC 
Review of attachment 255237 [details] [review]:

OK.
Comment 5 Florian Müllner 2013-09-19 05:54:44 UTC 
Attachment 255237 [details] pushed as efdf1ff - main: Close runDialog as necessary on session mode changes
Comment 6 Florian Müllner 2014-01-25 13:49:09 UTC 
*** Bug 722967 has been marked as a duplicate of this bug. ***
Comment 7 Florian Müllner 2017-04-24 19:23:17 UTC 
*** Bug 703679 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.