Lock screen still shows desktop windows

[Andras Veto]

https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

---

Super+l needs to be pressed twice to lock the screen. Pressing the shortcut only once results in strange behavior. Locking the screen in general is buggy (e.g. dock is visible when screen is locked, once screen is unlocked the dock disappears even after pressing activities). These issues were not present in 18.04. I am on a fresh install of 18.10 with gnome.

See also:
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

1)
Description: Ubuntu 18.10
Release: 18.10
2)
gdm3:
  Installed: 3.30.1-1ubuntu5
  Candidate: 3.30.1-1ubuntu5
  Version table:
 *** 3.30.1-1ubuntu5 500
        500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status
gnome-shell:
  Installed: 3.30.1-2ubuntu1
  Candidate: 3.30.1-2ubuntu1
  Version table:
 *** 3.30.1-2ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status
3)
The lock screen should maintain the functionality present in 18.04. Pressing the shortcut once should lock the screen, no ui elements should remain on the locked screen, locking and unlocking the screen should not result in the dock disappearing.
4)
The lock screen no longer works. It is possible to view and interact with ui elements after pressing the lock shortcut. It is possible to view the dock when the screen is locked.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gdm3 3.30.1-1ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 17 00:41:33 2018
ExecutablePath: /usr/lib/gdm3/gdm-x-session
InstallationDate: Installed on 2018-11-16 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 SHELL=/usr/bin/zsh
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=<set>
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Please explain in more detail what you see after locking once vs twice.

Also note existing bug reports:
"dock is visible when screen is locked" -> bug 1769383
"once screen is unlocked the dock disappears even after pressing activities" -> bug 1796265, bug 1801494

Finally, please try disabling all gnome-shell extensions and see if that fixes things.

[Andras Veto (andrasvetoprivate)]

Thanks for your response. Sorry for not seeing the existing bug reports.

When I lock once, the ui freezes completely and is still visible.

However, on the top bar (sorry, not sure what the specific terms are), the "Activities" button, any open application indicators (the things with the icons and the application name in the top bar), and the date/time disappear, but the keyboard language indicator and other indicators on the top right remain visible. It is still possible to click on the keyboard indicator or top right menu to bring them up, but at that point they can no longer be interacted with. The top right menu does show a pause button instead of the settings/lock/power button.

Pressing lock a second time locks the screen as normal.

This morning, I tried locking the screen by pressing the button itself instead of using the keyboard shortcut, and that worked the first time, but displayed the behavior described above the second time.

I only have gnome-tweaks installed that I know of (for disabling mouse acceleration). In the extensions tab, both items (kstatusnotifieritem and ubuntu dock) were disabled.

Please let me know if I can provide any more information to help resolve this, or if this was unclear. I would attach pictures, but PrtSc doesn't do anything after pressing lock the first time.

[Daniel van Vugt (vanvugt)]

Thanks. Can you please take a photo of the lock screen after locking only once?

[Andras Veto (andrasvetoprivate)]

This is after locking the screen once.

I opened the top right menu after locking the screen, and then opened the keyboard menu to the left of it. Both stay up, and can no longer be interacted with. The blurriness on the menus is not just because of the picture, that's what it looks like.

[Daniel van Vugt (vanvugt)]

Thanks. I don't know what would cause this so suggest next you report the bug to the gnome-shell developers here:

  https://gitlab.gnome.org/GNOME/gnome-shell/issues

and then tell us the new bug ID.

[Andras Veto (andrasvetoprivate)]

Ok, thanks. I created an issue and its ID is 794.

https://gitlab.gnome.org/GNOME/gnome-shell/issues/794

Let me know if there's anything else I could provide to help.

[Andras Veto (andrasvetoprivate)]

I just tested something, and it turns out that the issue was I had the Extensions turned on (even though each extension itself was off, as in the picture). Once I toggled that off, the issue resolved itself and now locking appears to work perfectly. Not sure why having extensions on would cause this behavior, though.

[Daniel van Vugt (vanvugt)]

Interesting. It might be a bug in one of those (standard Ubuntu extensions). It might also be an old extensions hiding in:

  ~/.local/share/gnome-shell/extensions/

(please look)

[Andras Veto (andrasvetoprivate)]

Sorry, I don't appear to have that folder. This is my ~/.local/share/gnome-shell/
[2018-11-19 9:13:32] ➜ gnome-shell ls -laR
.:
total 12
drwx------ 2 andras andras 4096 Nov 19 09:11 .
drwx------ 22 andras andras 4096 Nov 19 09:07 ..
-rw-rw-r-- 1 andras andras 3848 Nov 19 09:11 application_state
-rw-rw-r-- 1 andras andras 0 Nov 15 22:31 gnome-overrides-migrated

I've been playing around trying to break things again, and it seems as though the issue was having Extensions enabled (which I believe is the default Ubuntu behavior). Since disabling them, locking and unlocking works as it should (locking once immediately locks the screen, dock is not visible on the lock screen, and dock is still present after logging back in following the locking action).

[Andras Veto (andrasvetoprivate)]

Update: when I tried locking the screen while mirroring my laptop and external monitor, it failed (needed to be locked twice, dock disappeared, etc.). When extending the displays, locking works correctly.

[Jeffrey Davenport (jeffreydvp)]

@andrasvetoprivate I found out that this is caused by the Ubuntu Dock extension. However, this extension builds default settings into another existing extension called "Dash to Dock" I recommend installing Dash to Dock instead and customizing the settings to match that of Ubuntu Dock. That has resolved my screen locking issues with Ubuntu Dock.

To install:
1. Go to your Software center
2. Click on the search bar and type in "dash to dock"
3. Click install
4. Click Extension Settings and play around with them.

[Sebastien Bacher (seb128)]

@Jeffrey, could you give specifics on why you think it's an ubuntu-dock issue? Did you have dash-to-dock already installed, in which case it could be because those conflicts which is being fixed, see https://github.com/micheleg/dash-to-dock/pull/843

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Adam Niedling (krychek)]

Example video of the Launcher being visible on top of the Lock screen:

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1805014/+attachment/5216139/+files/Launcher%20visible%20on%20Lock%20screen.ogv

[Daniel van Vugt (vanvugt)]

Adam,

That's not this bug. That is bug 1769383.

[Daniel van Vugt (vanvugt)]

Changed the bug title to avoid ongoing confusion with bug 1769383.

[Daniel van Vugt (vanvugt)]

Assigned to extensions packages only, per comment #8.

[Adam Niedling (krychek)]

Sorry, someone else set my bug to be duplicate of this. Changed it.

[Andrea Azzarone (azzar1)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1769383, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.