[Budgie] Screen does not lock when suspended

[Nicolò Bianchetto]

Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but there is no password required anymore when the laptop awakes out of suspend. I did not change any settings and I still see "lock screen on suspend" = YES in the settings.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-09-29 (69 days ago)
InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Package: gnome-shell 40.5-1ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
Tags: impish
Uname: Linux 5.13.0-22-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-12-06 (1 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

[Ubuntu Foundations Team Bug Bot (crichton)]

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/FindRightPackage. 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/1953547/+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.]

[Chris Guiver (guiverc)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709

Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1953547

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Please try:

  gsettings set org.gnome.desktop.lockdown disable-lock-screen false
  gsettings set org.gnome.desktop.screensaver lock-enabled true

and then log in again.

If the problem still happens then please open the 'Extensions' app and ensure you don't have any custom extensions installed.

If the problem still happens after that then please run this command to gather more information:

  apport-collect 1953547

[Nicolò Bianchetto (nickwho)]

apport information

[Nicolò Bianchetto (nickwho)]

apport information

[Nicolò Bianchetto (nickwho)]

apport information

[Nicolò Bianchetto (nickwho)]

apport information

[Nicolò Bianchetto (nickwho)]

apport information

[Daniel van Vugt (vanvugt)]

I just noticed you're using Budgie. I wonder how that changes things compared to GNOME.

[Nicolò Bianchetto (nickwho)]

Ok. I found the solution here.

https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/16

By adding this to the startup application it seems to work:

#!/bin/bash
if ps ax | grep -v grep | grep gnome-screensaver > /dev/null
 then
  echo "gnome-screensaver is not running"
  echo "starting gnome-screensaver ..."
  pkill -9 -f '/usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver'
  sleep 3
  gnome-screensaver
 else
  echo "gnome-screensaver already running"
  exit
fi

Thank you very much for your time and sorry for the trouble.

[Launchpad Janitor (janitor)]

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

[fossfreedom (fossfreedom)]

@nickwho

Ah good that you have found our discourse forum.

Yes, gnome has from 21.10 changed gdm3 to run a process called gjs that sets up a dbus entry that gnome-screensaver also tries to create.

Basically two processes are competing for the same thing ... this is called a race .. that gnome-screensaver often loses.

In essence, you should not use either gdm3 if you want to run budgie, or don't install gnome-shell. Uninstalling gnome-shell-common will uninstall gnome-shell, remove gdm3 and install lightdm.

Budgie recommends you use slick-greeter.

If you have to use gdm3 then you have to use odd workarounds as described on discourse to try and kill the rogue gjs process. Note .... it does not always work and as such screen lock will break.

[Nicolò Bianchetto (nickwho)]

@fossfreedom

Thank you. I did as you said and it worked just fine.

I'm now using LightDM (with slick-greeter) and everything is fine.