Project

General

Profile

Bug #16763

Screen locker does not work in Buster

Added by spriver 9 months ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

100%

Feature Branch:
bugfix/16763-screen-locker-not-working-in-buster
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

The screen locker in Buster based Tails versions does not work.

When an administration password is set, neither pressing Super+L or clicking the button in the system menu will lock the screen.

When no administration password is set and pressing Super+L or clicking the screen locking button in the system menu will show the prompt for setting a password for the screen locker. When "Lock Screen" is clicked after a password was specified nothing will happen.


Related issues

Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

Associated revisions

Revision 1eba4009 (diff)
Added by segfault 9 months ago

Fix screen locker not working in Buster (refs: #16763)

We used the disable-lock-screen dconf setting in order to hide the
default lock screen button in the system menu. But in Buster, this also
disables locking the screen via the org.gnome.ScreenSaver D-Bus service,
so we can't use this setting anymore.

This commit disables the disable-lock-screen dconf setting and hides the
default lock screen button via out gnome-shell extension instead.

Revision 835f745c
Added by intrigeri 9 months ago

Merge remote-tracking branch 'origin/bugfix/16763-screen-locker-not-working-in-buster' into feature/buster

Closes: #16763

History

#1 Updated by mercedes508 9 months ago

  • Status changed from New to Confirmed

#2 Updated by intrigeri 9 months ago

@segfault, wanna take this one?

#3 Updated by intrigeri 9 months ago

#4 Updated by intrigeri 9 months ago

  • Assignee set to segfault

#5 Updated by segfault 9 months ago

intrigeri wrote:

@segfault, wanna take this one?

Sure

#6 Updated by segfault 9 months ago

  • Status changed from Confirmed to In Progress

#7 Updated by segfault 9 months ago

I think I found a fix. I pushed a commit to the feature branch. It's working when applied in a running Tails, I'm currently building a new image to test whether it also works there.

#8 Updated by segfault 9 months ago

  • Feature Branch set to bugfix/16763-screen-locker-not-working-in-buster

#9 Updated by segfault 9 months ago

  • Assignee deleted (segfault)
  • % Done changed from 0 to 30
  • QA Check set to Ready for QA

segfault wrote:

I'm currently building a new image to test whether it also works there.

Seems to work

#10 Updated by intrigeri 9 months ago

  • Assignee set to intrigeri

#11 Updated by intrigeri 9 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 30 to 100

#12 Updated by intrigeri 9 months ago

  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass

#13 Updated by intrigeri 9 months ago

In passing, this is an important feature and it seems that adding automated tests for it would be rather cheap; given we've seen one regression already, maybe it's worth it.

Also available in: Atom PDF