Project

General

Profile

Bug #5617

screen turns black after 10 minutes regarless of screensaver settings

Added by Tails over 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/13/2013
Due date:
% Done:

100%

Feature Branch:
bugfix/disable-dpms
Type of work:
Code
Blueprint:
Starter:
No
Affected tool:

Description

The default screensaver waiting time in Tails is set to 30 minutes, nonetheless the screen turns black after 10 minutes at most.

Running xset -dpms s off fixes this behavior. We should fix that in the ISO somewhere...


Subtasks

Feature #6421: Test GNOME power management overriding of X.Org DPMS defaultsResolved


Related issues

Related to Tails - Feature #5799: Deactivate screensaver until time is set Rejected

History

#1 Updated by ioerror over 6 years ago

This bug didn't seem to affect my machine - though as of 0.20 - my coreboot machine no longer functions after gnome-screensaver blanking without the above xset command.

#2 Updated by ioerror over 6 years ago

For those wondering about how the X server does screen blanking, I've found this website handy for a primer: http://www.shallowsky.com/linux/x-screen-blanking.html

#3 Updated by intrigeri over 6 years ago

  • Tracker changed from Feature to Bug
  • Starter set to No

#4 Updated by intrigeri over 6 years ago

  • QA Check set to Info Needed

Tails doesn't ship any screensaver, so I must say I am a bit lost wrt. "default screensaver waiting time" and "after gnome-screensaver blanking".

What is the actual behaviour on a standard Tails system, and why is this a problem?

#5 Updated by intrigeri over 6 years ago

  • Assignee set to ioerror

#6 Updated by ioerror over 6 years ago

I've tried this on Tails systems with extra packages as well as on tails systems with nothing, not even persistence enabled. This bug appears to impact many thinkpad users. I'm not clear if it impacts all users of Tails if the other developers aren't experiencing this issue.

I can confirm that users without any screen saver installed also experience this screen blanking issue. Essentially, to fix it, each user must type the following command at boot:

xset -dpms s off

If that command is typed, it ensures that the screen back light will not turn off after ~10 minutes and if the lid is closed, the LCD back light will turn off but when opened, the screen LCD will turn on again.

We should run that command at boot. What is the best place to hook such a change for the next release?

#7 Updated by akuckartz over 6 years ago

xorg.conf ? Some documentation I found so far:

Display Power Management Signaling
https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling

#8 Updated by intrigeri over 6 years ago

Before we start tweaking settings that apparently work well for the rest of us, please test with a build from feature/wheezy, as requested on tails-dev (August 15), and report back. Thanks in advance!

#9 Updated by sajolida over 6 years ago

To answer intrigeri's question: yes, there is no screensaver installed so we were using the wrong terminology. But if you do System → Preferences → Power Management Preferences. The setting for "Put display to sleep when inactive for" is set to "30 minutes". That's what we are talking about.

If I remember correctly, this setting does put the screen to sleep, turns it black. But this behavior is taken over by the DPMS stuff that turns the screen black after only 10 minutes, and not 30. So, for example, if you want to disable this feature and set that preference to "Never", the screen will still turn black after 10 minutes.

If I understand correctly, ioerror is reporting that this DPMS sleep is breaking badly on some computers. So that initial problem, DPMS taking over the configured sleeping delay, is actually more problematic now that it used to be. Even thought the problem has been known for a while.

Is that any clearer?

#10 Updated by intrigeri over 6 years ago

sajolida wrote:

Is that any clearer?

Yes, thanks!

So apparently we have two bugs here:

  1. Users can't tweak screen blanking settings using GNOME tools only.
  2. DPMS sleep makes at least one system (a coreboot machine) unusable.

The first bug is a minor one, that indeed has been known for a while (I forgot). Patches are welcome, no emergency, especially if it can't be reproduced on Tails/Wheezy.

Things might be different for the second bug, and we need to assert how broadly it impacts hardware, to start with:

  • What hardware can it be reproduced on with Tails 0.20?
  • What hardware can it be reproduced on with Tails/Wheezy snapshots?

(It's unclear to me which one "This bug" relates to in "This bug appears to impact many thinkpad users". ioerror?)

Anyone interested in working on this, perhaps it's time to split this ticket in two, then.

#11 Updated by sajolida about 6 years ago

I did some more testing with Tails 0.20.1 on various laptops. The screen turns black after 10 minutes with DPMS, but pressing any key brings them back as usual:

  • Thinkpad X61 running on power adapter
  • Thinkpad X61 running on battery
  • Thinkpad X60s running on power adapter
  • Thinkpad X60s running on battery

#12 Updated by intrigeri about 6 years ago

ThinkPad X32, Tails 0.20.1 with main power connected: screen goes to sleep after about 10 minutes, wakes up after pressing any key.

#13 Updated by sajolida about 6 years ago

lspci reports the same graphical hardware for both Thinkpad X60 (affected for ioerror) and Thinkpad X60s (unaffected for me):

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)

#14 Updated by intrigeri about 6 years ago

The "screen goes black after 10 minutes, regardless of GNOME power management settings" issue was reproduced on Tails/Wheezy at commit 7ee3fa8.

Next step: reproduce on current Debian unstable, or Fedora Rawhide, or whatever is close to the latest upstream stuff.

Worst case, we'll workaround this with a xorg.conf.d snippet or a xsession init script that runs xset, but first we should ensure that this bug is reported to GNOME upstream.

#15 Updated by intrigeri about 6 years ago

  • Assignee deleted (ioerror)
  • QA Check deleted (Info Needed)

#16 Updated by intrigeri about 6 years ago

  • Assignee set to intrigeri
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/disable-dpms

Tentative fix pushed, will be part of the next experimental nightly build. I'll test and request review'n'merge.

#17 Updated by intrigeri about 6 years ago

  • Assignee deleted (intrigeri)

On bugfix/disable-dpms, Thinkpad X32, connected to AC power: screen goes black after 30 minutes.

#18 Updated by intrigeri about 6 years ago

  • Assignee set to bertagaz

Asked review'n'merge, assigning to someone who volunteered to do some review'n'merges during this cycle.

#19 Updated by alant about 6 years ago

  • Status changed from Confirmed to 11
  • Assignee changed from bertagaz to intrigeri
  • QA Check changed from Ready for QA to Pass

Merged, thanks!

#20 Updated by intrigeri about 6 years ago

  • Assignee deleted (intrigeri)

#21 Updated by intrigeri almost 6 years ago

  • Status changed from 11 to Resolved

Fixed in 0.22.

Also available in: Atom PDF