# Lockscreen not working after update to 21.10

**URL:** <https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394>\
**Category:** Budgie Desktop\
**Created:** [October 15, 2021, 4:45pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394 "2021-10-15T16:45:53Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![MLampner](https://avatars.discourse-cdn.com/v4/letter/m/9fc29f/32.png) [@MLampner](https://discourse.ubuntubudgie.org/u/MLampner)\
**Post date:** [October 27, 2021, 3:21pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/21 "2021-10-27T15:21:18Z")

</div>

Will give this a try. I’m new to the Linux structure but should be capable of pasting this into terminal. again thanks! Will let you know if it also works on 20.04.

---

<div class="post-metadata">

**Author:** ![RupertEverton](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@RupertEverton](https://discourse.ubuntubudgie.org/u/RupertEverton)\
**Post date:** [October 27, 2021, 3:38pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/22 "2021-10-27T15:38:56Z")

</div>

Open `gedit`, copy the following and paste it into gedit, save it as `screensaver-autorun.sh` in a place where you’re not gonna move it. Then in the menu search for ‘Startup Applications’, click add, give it a name and in ‘Command’ click ‘Browse’ and select screensaver-autorun.sh.

That should do it

> [@Lockscreen not working after update to 21.10](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/17):
>
> So this is what I came up with: #!/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 Adding it to startup applications seems to be sufficient to get everything running the way it should. Cheers for the help

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [November 22, 2021, 6:37pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/24 "2021-11-22T18:37:15Z")

</div>

Note to all … if you don’t use gnome-shell then this solution is easier and quicker to do

> [@Lock screen not working in 21.10](https://discourse.ubuntubudgie.org/t/lock-screen-not-working-in-21-10/5466/11):
>
> So to remove GDM3 sudo apt purge gdm3 To remove gnome-shell-common sudo apt purge gnome-shell-common Remember you can in Ubuntu install multiple desktop environments - you choose which desktop environment you want to launch via the login screen - so click on the “budgie” icon next to the password field to see which desktop environments you want to switch to. When I say “break GNOME Shell installation” - its just that it means you will no longer have the ability to login to GNOME Shell via t…

---

<div class="post-metadata">

**Author:** ![vdibart](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/vdibart/32/3649_2.png) [@vdibart](https://discourse.ubuntubudgie.org/u/vdibart)\
**Post date:** [November 23, 2021, 7:47pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/25 "2021-11-23T19:47:47Z")

</div>

[UPDATED] I have been struggling with the same issue stemming from the same update. These instructions worked perfectly for me. Thank you all for this.

Cheers!

(the original post mentioned an issue with the ‘x’ key on my laptop which has since been determined to be unrelated)

---

<div class="post-metadata">

**Author:** ![rbreaves](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/rbreaves/32/3871_2.png) [@rbreaves](https://discourse.ubuntubudgie.org/u/rbreaves)\
**Post date:** [November 30, 2021, 8:28pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/26 "2021-11-30T20:28:00Z")

</div>

Lockscreen broke for me too - but that script didn’t work for me so I modified it to work.

```auto
#!/bin/bash
if ! pgrep -f gnome-screensaver &> /dev/null 2>&1; 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

```

Also when adding it to autostart I needed to delay it from running for like 5 seconds so or it’d fail.

```auto
/bin/bash -c "/usr/bin/sleep 5;/home/rreaves/lockfix.sh&"

```

---

<div class="post-metadata">

**Author:** ![Misso](https://avatars.discourse-cdn.com/v4/letter/m/97f17d/32.png) [@Misso](https://discourse.ubuntubudgie.org/u/Misso)\
**Post date:** [January 7, 2022, 4:58pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/27 "2022-01-07T16:58:31Z")

</div>

I use this script to solve the same problem but it doesn’t work, any suggestions!

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 7, 2022, 5:17pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/28 "2022-01-07T17:17:18Z")

</div>

Make sure you are using slick-greeter not gdm3.

If you don’t want to use gnome-shell then removing this package will make the lock screen work

```
sudo apt purge gnome-shell-common
```

---

<div class="post-metadata">

**Author:** ![Misso](https://avatars.discourse-cdn.com/v4/letter/m/97f17d/32.png) [@Misso](https://discourse.ubuntubudgie.org/u/Misso)\
**Post date:** [January 7, 2022, 6:34pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/29 "2022-01-07T18:34:50Z")

</div>

Many thanks! problem solved.

---

<div class="post-metadata">

**Author:** ![brdloush](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/brdloush/32/1089_2.png) [@brdloush](https://discourse.ubuntubudgie.org/u/brdloush)\
**Post date:** [January 13, 2022, 10:50pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/30 "2022-01-13T22:50:10Z")

</div>

@fossfreedom Amazing hint for that `apt purge gnome-shell-common` trick, finally my lock shortcut (& lock command in general) is working again. Why does removing that package help with this specific problem?

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 13, 2022, 11:05pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/31 "2022-01-13T23:05:52Z")

</div>

gnome-shell installs an autostart file that also runs when you login. It is that autostart file that prevents gnome-screensaver working correctly. By uninstalling gnome-shell-common, that autostart file and the accompanying application (called gjs) is removed. Thus gnome-screensaver works correctly.

---

<div class="post-metadata">

**Author:** ![Coeur-Noir](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/coeur-noir/32/4515_2.png) [@Coeur-Noir](https://discourse.ubuntubudgie.org/u/Coeur-Noir)\
**Post date:** [January 26, 2022, 6:44pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/32 "2022-01-26T18:44:55Z")

</div>

But first what triggered here the installation of _gnome-shell-common_ ?

×buntu are not made to use many DE on a same installation, furthermore if different DE get used by only one and same user.

Most DE being « forks » from Gnome components and using Gtk, they use _same_ files for storing their _different_ parameters, ending up in - no other word - mess.

That’s the purpose of each variant, each integrates one DE.

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 26, 2022, 6:50pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/33 "2022-01-26T18:50:35Z")

</div>

> [@Coeur-Noir](#):
>
> But first what triggered here the installation of _gnome-shell-common_ ?

By install GDM3 this installs gnome-shell-common as well as gnome-shell.

Likewise, as you mentioned, people who started of on “Ubuntu” with gnome-shell and then installed budgie.

---

<div class="post-metadata">

**Author:** ![KnoedelFan](https://avatars.discourse-cdn.com/v4/letter/k/22d042/32.png) [@KnoedelFan](https://discourse.ubuntubudgie.org/u/KnoedelFan)\
**Post date:** [March 16, 2022, 6:46pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/34 "2022-03-16T18:46:32Z")

</div>

Then is a new installation of Ubuntu 22. 04 the right way?

Can you please explain the order of the commands that lead to a working Budgie interface after reinstalling and perfect update?

Because I want to continue participating in the test program and share my experiences

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [March 16, 2022, 6:54pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/35 "2022-03-16T18:54:22Z")

</div>

@samlane is looking at some last minute raspi issues - we’ll be then releasing a beta 22.04 raspi image to test with.

---

<div class="post-metadata">

**Author:** ![KnoedelFan](https://avatars.discourse-cdn.com/v4/letter/k/22d042/32.png) [@KnoedelFan](https://discourse.ubuntubudgie.org/u/KnoedelFan)\
**Post date:** [March 16, 2022, 7:10pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/36 "2022-03-16T19:10:22Z")

</div>

Fine, fine, then I wait with the further test, and then with pleasure  
22. 04 Budgie for Raspi to be able to test.

Thank you for this message.

---

<div class="post-metadata">

**Author:** ![Zajdalen](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/zajdalen/32/3902_2.png) [@Zajdalen](https://discourse.ubuntubudgie.org/u/Zajdalen)\
**Post date:** [May 3, 2022, 7:06am UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/37 "2022-05-03T07:06:18Z")

</div>

updated to 22.04 but the problem persists. The solution with bash script seems to work but it always break “show time” applet in raven. I use multiple screen and this applet always disappear after lock - unlock. I though that new LTS version will repair this but it doesnt ☹ so any idea how to make lockscreen work and does not break applet?

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [May 3, 2022, 7:24am UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/38 "2022-05-03T07:24:53Z")

</div>

> [@Lockscreen not working after update to 21.10](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/31):
>
> gnome-shell installs an autostart file that also runs when you login. It is that autostart file that prevents gnome-screensaver working correctly. By uninstalling gnome-shell-common, that autostart file and the accompanying application (called gjs) is removed. Thus gnome-screensaver works correctly.

You cannot use gdm3 as your login screen and you must uninstall the package described in the link above

---

<div class="post-metadata">

**Author:** ![CalmDownMonkey](https://avatars.discourse-cdn.com/v4/letter/c/87869e/32.png) [@CalmDownMonkey](https://discourse.ubuntubudgie.org/u/CalmDownMonkey)\
**Post date:** [May 28, 2022, 5:23pm UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/39 "2022-05-28T17:23:53Z")

</div>

I’m having this problem since upgrading to 22.04 and these solutions don’t work for me (can’t get my lock screen to appear).

I tried the scripts (killing and restarting gnome-screensaver) but that doesn’t seem to matter. I also checked gnome-screensaver is running.

I ran `sudo apt purge gnome-shell-common` too, and restarted, which removed some options from the login screen, but the problem persists (not sure how those others got there, I’ve only ever used Ubuntu Budgie).

I confirmed I’m using lightdm, and `/etc/lightdm/lightdm.conf` says `greeter-session=slick-greeter`.

`journalctl` doesn’t seem to show anything at all when I click the lock button or press WIN+L.

Any other ideas?

---

<div class="post-metadata">

**Author:** ![CalmDownMonkey](https://avatars.discourse-cdn.com/v4/letter/c/87869e/32.png) [@CalmDownMonkey](https://discourse.ubuntubudgie.org/u/CalmDownMonkey)\
**Post date:** [May 30, 2022, 9:47am UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/40 "2022-05-30T09:47:39Z")

</div>

I fixed my problem, so I’ll share the solution just in case it helps anyone.

I enabled gnome-screensaver debugging by doing this:

```auto
pkill gnome-screensaver
gnome-screensaver --no-deamon --debug 2>&1 | tee ~/g-ss.log

```

Then in the log file, I noticed it was saying `Locking disabled by the administrator` whenever I tried to lock.

I found these two settings:

```auto
gsettings get org.gnome.desktop.screensaver lock-enabled
gsettings get org.gnome.desktop.lockdown disable-lock-screen

```

Both of these were `true`, but I reckon the second one should be `false`, so I changed it with `set` instead of `get`.  
Now everything works fine - none of the other fixes mattered in my situation.

I have no idea why the upgrade would’ve changed that variable to disable the lock screen, but hey-ho, fixed now!

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [May 30, 2022, 9:53am UTC](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394/41 "2022-05-30T09:53:35Z")

</div>

congrats!

I had a look at the disable-lock-screen key in dconf-editor. It states that the default value for that key is “false” - so something else must have manually set that key value to true.

Did you happen to be in the displays section of budgie-control-center ? you have the option there to play with the disable lock screen option. Note - if you are using fractional scaling it will automatically disable the lock screen since fractional scaling & the lock screen doesn’t work.

[Previous page](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394.md?page=1)

[Next page](https://discourse.ubuntubudgie.org/t/lockscreen-not-working-after-update-to-21-10/5394.md?page=3)