Screen seems to think it is still locked after I've unlocked it

Bug #1800492 reported by Jonathan Kamens
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

Sometimes in 18.10 when I unlock my screen (well, not actually "unlock", since I don't have the screensaver configured to lock, so more accurately, when I disable the screensaver), I end up on a screen which looks like the computer still sort of thinks the screensaver is activated. My regular background isn't there, my system tray app indicators are missing, and the system tray menu looks like the one that shows when the screensaver is activated, but at the same time, there's a launch tray at the left side of the screen, and the rest of the ornamentation that usually displays when the screensaver is activated is missing. See the attached screenshot.

Nothing I do at this point seems to have any effect, e.g. I can't launch app windows from the tray.

This particular time this happened that has prompted me to report it was when I was accessing my desktop remotely (that's how I got a screenshot), but I _think_ I've also seen it when walking up to my desk and turning off the screensaver locally by hitting the Enter key. I.e., I don't _think_ this bug is related to using a remote desktop, but I can't be 100% certain. If I do notice it again when I'm local I'll update this bug to confirm.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 29 11:26:05 2018
DisplayManager: gdm3
InstallationDate: Installed on 2016-01-16 (1017 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (8 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T07:35:17.955033

Revision history for this message
Jonathan Kamens (jik) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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 1800475, 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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.