Feature #5799
Deactivate screensaver until time is set
0%
Description
If the system clock is off (being late), when the time is set properly from the network, the screen is blanked. As it happens during the boot process, this is a little bit sudden and frightening. Moving the mouse gets the display back, but sill, it would be best to be avoided.
As Tais does not ship gnome-screensaver
it is probably X.org that does the blanking. One should experiment with the -dpms
and +dpms
options of xset(1)
.
Subtasks
Related issues
Related to Tails - |
Resolved | 2013-11-13 | |
Related to Tails - |
Rejected | 2016-12-29 | |
Related to Tails - |
Resolved | 2014-12-03 |
History
#1 Updated by BitingBird 2014-06-09 10:11:52
- Subject changed from deactivate screensaver until time is set to Deactivate screensaver until time is set
- Description updated
- Starter set to No
#2 Updated by BitingBird 2014-06-21 14:16:20
It would be great, but I don’t think that it deserves a priority elevated.
#3 Updated by BitingBird 2015-01-02 20:59:32
- Priority changed from Elevated to Normal
#4 Updated by intrigeri 2017-01-07 13:36:42
- related to
Bug #12098: Spurious screensaver activation while synchronizing the system clock added
#5 Updated by intrigeri 2017-01-07 13:36:59
- related to
Feature #5684: Screen locker added
#6 Updated by Anonymous 2018-08-19 09:34:02
- related to Feature #12213: Wayland in Tails 5.0 (Bullseye) added
#7 Updated by intrigeri 2018-08-19 09:56:11
- Status changed from Confirmed to Rejected
I think the screensaver we now use (implemented by GNOME Shell) uses a monotonic clock, is not affected by this problem, and overrides whatever DPMS thing X.Org may want to do: I’ve tried setting the clock to now + 1h with date
and the screen did not go blank.
#8 Updated by intrigeri 2018-08-19 09:56:24
- related to deleted (
Feature #12213: Wayland in Tails 5.0 (Bullseye))