Bug#919914: Systematic test of settings & tweaks

[Tassia Camoes Araujo]

On 2019-04-28 16:18, Simon McVittie wrote:
> 
> Please could you describe precisely what these tests mean, and
> particularly the cases you describe as failing? 
>
Sure. Please check below more info on each case described as a failure
in my previous message.

Failure #1

- To reproduce: Gnome-Tweaks configuration "Suspend when laptop lid is
closed" turned OFF. Gnome-settings Privacy option "Automatic lock" is
turned ON, and "After screen turns off". Close the lid.
- Expected: when the lid is closed, the laptop should not suspend, but
when the lid is re-opened the screen should be locked, asking for
authentication.
- What happens: No suspend, and no authentication required. ***this was
the situation described when the bug was opened***

Failure #2

- To reproduce: Gnome-Tweaks configuration "Suspend when laptop lid is
closed" turned OFF. Gnome-settings Privacy option "Automatic lock" is
turned ON, and "After blank for X minutes". Close the lid and wait for X
minutes.
- Expected: when the lid is closed, the laptop should not suspend, but
after X minutes have passed, the lid is re-opened and the screen should
be locked, asking for authentication.
- What happens: No suspend, and no authentication required, even after X
minutes have passed.

Failure #3

- To reproduce: Gnome-Tweaks configuration "Suspend when laptop lid is
closed" turned ON. Gnome-settings Privacy option "Automatic lock" is
turned ON, and "After blank for X minutes". Close the lid and re-open
before the X minutes have passed.
- Expected: when the lid is closed, the laptop should suspend, but only
after X minutes have passed that the screen should be locked. If the lid
is open before X minutes, I would expect it to not be locked.
- What happens: suspend is OK, but screen is locked right away, even
before the X minutes.

Failure #4

- To reproduce: Gnome-settings power saving is configured "Blank screen
after X minutes". Gnome-settings Privacy option "Automatic lock" is
turned ON, and "After blank for Y minutes". Close the lid and re-open
before the X+Y minutes have passed.
- Expected: when the laptop is inactive for X minutes, the screen should
blank, but only after extra Y minutes that the screen should be locked.
If the lid is open before X+Y minutes, I would expect it to not be
locked.
- What happens: but screen is locked right after blank, even before the
X+Y minutes.

Let me know if anything is still not clear.
Cheers,

Tassia.

Bug#919914: Systematic test of settings & tweaks

[Tassia Camoes Araujo]

user debian-rele...@lists.debian.org
usertags 919914 + bsp-2019-04-ca-toronto
thanks

We did some systematic tests and believe it is a bug in the integration
between gnome-tweaks and gnome-settings-daemon (Privacy -> Screen Lock
option). We still considered the status of the Power saving settings,
blank screen, check below.

I) Behavior on closing the lid

a) Tweaks: "Suspend when laptop lid is closed" OFF

"Automatic screen lock OFF" --> OK
"Automatic lock: After screen turns off" --> FAIL *** this was the bug
reported ***
"Automatic lock: After blank for X minutes: check passed X" --> FAIL
"Automatic lock: After blank for X minutes: check before X" --> OK (no
block)

b) Tweaks: "Suspend when laptop lid is closed" ON

"Automatic screen lock OFF" --> OK
"Automatic lock: After screen turns off" -.> OK
"Automatic lock: After blank for X minutes: check passed X" --> OK
"Automatic lock: After blank for X minutes: check before X" --> FAIL
(already blocked before X)

II) Behavior on inactivity

c) Power saving: "Blank screen after X minute"
   Laptop lid position: OPEN
   Privacy:

"Automatic screen lock OFF" --> OK
"Automatic lock: After screen turns off" -.> OK
"Automatic lock: After blank for X minutes: check passed X" --> OK
"Automatic lock: After blank for X minutes: check before X" --> OK (no
block)

d) Power saving: "Blank screen after X minute:
   Laptop lid position: CLOSED
   Privacy:

"Automatic screen lock OFF" --> OK
"Automatic lock: After screen turns off" --> OK
"Automatic lock: After blank for X minutes: check passed X" --> OK
"Automatic lock: After blank for X minutes: check before X" --> FAIL
(already blocked before X)


we hope this helps!

Tassia & Valessio.

Bug#913978: Maybe at least document those keystrokes?

[Tassia Camoes Araujo]

found 913978 1:3.30.3-1
tags 913978 +confirmed
thanks

--

>From what I could understand, it is unlikely this will be fixed before
Buster release. So how should we proceed about his bug?
Even if a backport can possibly be provided later, would it be possible
to just document the keystrokes "workaround" mentioned by Jeremy Bicha
in the package shipped with Buster?
It might be a big difference for users in need of this accessibility
feature.

Thanks,

Tassia.

Bug#913978: (no subject)

[Tassia Camoes Araujo]

user debian-rele...@lists.debian.org
   
usertags 913978 + bsp-2019-04-ca-toronto   
   
thank you