Privacy : Deactivating screen lock doesn't work

Bug #1724105 reported by NoOne on 2017-10-16
12
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Low
Unassigned
gnome-shell (Ubuntu)
Low
Unassigned

Bug Description

What steps do I need to follow to reproduce this bug : Install gnome-session. In that session, open System Settings/Privacy Uncheck Lock Screen.

What did I expect to happen : When opening the lid of my laptop, I was expecting to see no login screen and be back right away in my session, without having to enter my password.

What actually happens: After opening the lid, the screen flashes, then goes black. After hitting the space bar, I get the "clock screen", swipe up, then get login screen. Sometimes, the screen just freeze. Have to hard reboot.

Side effect : Lock Screen activated, only way that the laptop will come back from sleep normally.

Dell XPS 13 (9360)
---
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 17.10
InstallationDate: Installed on 2017-10-16 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
Package: gnome-shell 3.26.1-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Tags: artful
Uname: Linux 4.13.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
_MarkForUpload: True

Daniel van Vugt (vanvugt) wrote :

Curious you describe a setting that doesn't seem to exist: "Confidentiality, Deactivating lock screen"

Do you mean this? Privacy > Screen lock = OFF

Regardless, please upload your system information using this command:

apport-collect 1724105

Changed in gnome-shell (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected artful
description: updated

apport information

apport information

apport information

apport information

I mean this setting. See screenshot. English is not installed on my computer... So, I can make mistake about the right names. Sorry.

Daniel van Vugt (vanvugt) wrote :

Yes, that's it. Thanks.

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
NoOne (1noname) wrote :

I modified the title. Hope it's better. :-)

summary: - Confidentiality : Deactivating lock screen doesn't work
+ Privacy : Deactivating screen lock doesn't work
NoOne (1noname) on 2017-10-31
description: updated
NoOne (1noname) wrote :

More infos...

I first installed a gnome-session in Ubuntu 17.10, to get a more Vanilla Gnome. Now that I've modified the GDM Lock Screen to Vanilla Gnome*, so far it works. The laptop correctly comes back from sleep after opening the lid, and I'm presented with the "normal" clock screen. Then, I swipe up to get the Login screen.

But... If I deactivate the Lock Screen, in the Privacy Settings, it won't work. It behaves erratically, screen flashes, goes black, and come back to the login screen.

* Link https://didrocks.fr/2017/09/11/ubuntu-gnome-shell-in-artful-day-11/

NoOne (1noname) on 2017-10-31
description: updated
description: updated
NoOne (1noname) on 2017-10-31
description: updated
NoOne (1noname) wrote :

I updated the bug description, hoping it is clearer to understand.

tags: added: unlock
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

NoOne (1noname) wrote :

I don't think it's an upstream bug at all, as I didn't have that problem on Fedora 27 and Manjaro, both on Gnome 3.26.

And I had the same problem with Ubuntu Gnome 17.04

Please don't put the blame on upstream before investigating.

Jeremy Bicha (jbicha) wrote :

I confirm that I cannot duplicate the issue on Fedora 27 or on Debian Buster.

Changed in gnome-shell (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in gdm3 (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Daniel van Vugt (vanvugt) wrote :

If you still experience screen freezes and have to reboot, please try this:

1. Apply the workaround from bug 994921.

2. After the problem happens next time, reboot and look for files in /var/crash.

3. If you find any crash files then run:
   ubuntu-bug /var/crash/YOURFILE.crash

4. Tell us here the ID(s) of new bugs created.

Changed in gdm3 (Ubuntu):
status: Triaged → Incomplete
Changed in gnome-shell (Ubuntu):
status: Triaged → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]

Changed in gdm3 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers