[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#787279: installation-reports: still present in rootskel-gtk 11.0.2



Followup-For: Bug #787279
Control: reassign -1 rootskel-gtk

Having just tested this again, I see that setting `dpms=true` on the kernel
command line has no effect, as reported in this bug.

In the mean time, I note that we no longer have screen-blanking going on in the
text-mode (console) install.  This seems to be because the kernel is now defaulting
to setting consoleblank=0 as one can see by running:

  cat /sys/module/kernel/parameters/consoleblank

which returns `0`  (BTW This is just as it should be IMO)

Given that we seem to have decided that there's no danger of burn-in on consoles
these days, perhaps we can also agree that there's no danger for X either.

The '-s 0' option to Xorg does actually stop X from blanking, as one can
demonstrate by specifying this kludge on the kernel command-line:

  preseed/early_command="echo DPMS=-s\ 0 > /lib/debian-installer.d/S61Xnoblank"

which sets $DPMS to "-s 0" which is then used within
`debian-installer.d/S62Xorg` to set an option for Xorg.

That being the case, I think we should apply the '-s 0' setting by default, and
only remove it if someone sets "dpms=true".

=-=-

This can all be seen here (while the links remain active):

Normal Debian-Edu install (which takes long enough to blank the screen) being
marked as a soft-fail at the blank screen:

  https://openqa.debian.net/tests/76944

now with a setting of:  GRUB: dpms=false
which sets that on the kernel command line, thus:

  https://openqa.debian.net/tests/77055#step/_boot_to_debianinstaller/2

but still blanks:

  https://openqa.debian.net/tests/77055#step/grub/36

on the other hand, no screen-blanking is seen in text mode:

  https://openqa.debian.net/tests/77056

and if one applies the '-s 0' kludge:

  https://openqa.debian.net/tests/77059#step/_boot_to_debianinstaller/2

which also doesn't blank:

  https://openqa.debian.net/tests/77059


Cheers, Phil.


Reply to: