Bug #16763

Screen locker does not work in Buster

Added by spriver 2019-05-26 19:49:35 . Updated 2019-06-02 09:43:33 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_4.0
Start date:
Due date:
% Done:

100%

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

Starter:
Affected tool:
Deliverable for:

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.

Subtasks

Related issues

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

History

#1 Updated by mercedes508 2019-05-27 11:12:07

  • Status changed from New to Confirmed

#2 Updated by intrigeri 2019-06-01 07:21:04

@segfault, wanna take this one?

#3 Updated by intrigeri 2019-06-01 07:21:14

#4 Updated by intrigeri 2019-06-01 07:21:25

  • Assignee set to segfault

#5 Updated by segfault 2019-06-01 13:04:47

intrigeri wrote:
> @segfault, wanna take this one?

Sure

#6 Updated by segfault 2019-06-01 21:30:23

  • Status changed from Confirmed to In Progress

Applied in changeset commit:tails|1eba40091824ff4adf519314acd5535f35456df6.

#7 Updated by segfault 2019-06-01 21:32:41

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 2019-06-01 21:32:57

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

#9 Updated by segfault 2019-06-01 23:00:41

  • 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 2019-06-02 06:56:42

  • Assignee set to intrigeri

#11 Updated by intrigeri 2019-06-02 09:41:42

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

Applied in changeset commit:tails|835f745c59a5083564aa413d168742a0b3e663a5.

#12 Updated by intrigeri 2019-06-02 09:42:37

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

#13 Updated by intrigeri 2019-06-02 09:43:33

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.