Locking the screen once leaves screen contents visible but not interactive. Locking the screen a second time works.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Invalid
|
High
|
Andrea Azzarone | ||
Bionic |
Invalid
|
High
|
Andrea Azzarone | ||
Cosmic |
Invalid
|
High
|
Andrea Azzarone | ||
Disco |
Invalid
|
High
|
Andrea Azzarone | ||
gnome-shell-extension-ubuntu-dock (Ubuntu) |
Fix Released
|
High
|
Andrea Azzarone | ||
Bionic |
Fix Released
|
High
|
Andrea Azzarone | ||
Cosmic |
Fix Released
|
High
|
Andrea Azzarone | ||
Disco |
Fix Released
|
High
|
Andrea Azzarone |
Bug Description
1) Ubuntu 18.10 (new install)
2) gdm3 3.30.1-1ubuntu5
Preconditions
The session's user has auto-login enabled (i.e. the system starts and the user is not prompted for a password but directly presented with the desktop)
3) What should happen:
Unlocked desktop is showing. Lock screen is invoked (via WIN+L or via top right corner menu) and the lock screen is engaged (that is, lock screen clock shade drops down and screen fades to dark). Pressing ENTER brings back the lock screen and the password is prompted.
4) What happens:
First Win + L lets the system in a half locked state in which the contents of the desktop are seen although no interaction is possible. A second Win + L correctly invokes the lock screen.
affects: | ubuntu → gnome-session (Ubuntu) |
affects: | gnome-session (Ubuntu) → gnome-shell (Ubuntu) |
Changed in gnome-shell (Ubuntu): | |
status: | Confirmed → In Progress |
status: | In Progress → Triaged |
status: | Triaged → Confirmed |
tags: | added: rls-cc-incoming rls-dd-incoming |
Changed in gnome-shell (Ubuntu Cosmic): | |
assignee: | nobody → Andrea Azzarone (azzar1) |
tags: |
added: rls-cc-tracking removed: rls-cc-incoming |
Changed in gnome-shell (Ubuntu Bionic): | |
assignee: | nobody → Andrea Azzarone (azzar1) |
Changed in gnome-shell (Ubuntu Disco): | |
assignee: | nobody → Andrea Azzarone (azzar1) |
Changed in gnome-shell-extension-dashtodock (Ubuntu Bionic): | |
assignee: | nobody → Andrea Azzarone (azzar1) |
Changed in gnome-shell-extension-dashtodock (Ubuntu Cosmic): | |
assignee: | nobody → Andrea Azzarone (azzar1) |
Changed in gnome-shell-extension-dashtodock (Ubuntu Disco): | |
assignee: | nobody → Andrea Azzarone (azzar1) |
tags: | removed: rls-dd-incoming |
summary: |
- gnome session: Must ask twice to lock the screen + Locking the screen once leaves screen contents visible but not + interactive. Locking the screen a second time works. |
Changed in gnome-shell (Ubuntu Bionic): | |
importance: | Undecided → High |
Changed in gnome-shell (Ubuntu Cosmic): | |
importance: | Undecided → High |
Changed in gnome-shell-extension-ubuntu-dock (Ubuntu Cosmic): | |
status: | In Progress → Fix Released |
Changed in gnome-shell-extension-ubuntu-dock (Ubuntu Bionic): | |
status: | In Progress → Fix Released |
no longer affects: | gnome-shell-extension-dashtodock (Ubuntu) |
no longer affects: | gnome-shell-extension-dashtodock (Ubuntu Bionic) |
no longer affects: | gnome-shell-extension-dashtodock (Ubuntu Cosmic) |
no longer affects: | gnome-shell-extension-dashtodock (Ubuntu Disco) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1799293/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]