On 05/24/2018 01:34 AM, Per Jessen wrote:
FYI, I have opened a ticket - https://bugzilla.opensuse.org/show_bug.cgi?id=1094452
Good deal, in the mean time, I've found a way to set consoleblank from a remote session, e.g. # TERM=linux setterm -blank 10 -powerdown 12 >/dev/tty0 </dev/tty0 That will restore /sys/module/kernel/parameters/consoleblank 600 The TERM=linux is required so that setterm will communicate with the correct terminal. When accessing remotely via xterm, the environment variable TERM=xterm which doesn't have an interface. The apparent kernel default changed from 600 to 0 at some point which I believe is what broke this. (I suspect it was a cludge to fix a problem with vt blanking effecting X, but instead of fixing the new X to work correctly with consoleblank, somebody got the bright idea to just set consoleblank to 0) God I hope we haven't slipped to that level of "fixing" things. The biggest PITA is /sys/module/kernel/parameters/consoleblank is read-only (0444), so the only way to set it is either by passing the kernel parameter "consoleblank=600" (which doesn't set the powerdown), or with setterm. Thank you for filing the bug, I added to it... (what utter BS -- "this is intended behavior" -- intended behavior my a55... I guess it was just broken for the past 20 years (while it actually worked) and then got fixed when it stopped working???? What planet are we living on? Planet Stupidity? -- where things NOT working are the "intended behavior", and we are all supposed to be just dumb enough to take "this is intended behavior" as a valid reason for it not working?? Good lord...) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org