http://bugzilla.opensuse.org/show_bug.cgi?id=1094452 http://bugzilla.opensuse.org/show_bug.cgi?id=1094452#c2 David Rankin <drankinatty@suddenlinkmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |drankinatty@suddenlinkmail. | |com --- Comment #2 from David Rankin <drankinatty@suddenlinkmail.com> --- This is not the intended behavior because it breaks console blanking for every server operating without X. All monitors on my server are stuck ON 24/7 because default console blanking is broken. The intended behavior is to have consoleblank default to 600, so that console blanking works correctly. This has worked properly for nearly 20 years. There is no reason to break the default behavior by zeroing consoleblank. The underlying issue is apparently a problem with the vt blanking effecting the new X. So instead of fixing X properly to work with default consoleblank, all default console blanking was broken by setting the value to 0 as a workaround to an X problem. Let's fix the problem so that default console blanking works correctly, as it always has, instead of just giving up and disabling console DPMS altogether. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1094452 http://bugzilla.opensuse.org/show_bug.cgi?id=1094452#c4 --- Comment #4 from David Rankin <drankinatty@suddenlinkmail.com> --- The console should blank and powerdown, with defaults of 10 min (600s) and 12 min, respectively. Servers are NOT headless as used to justify the change in the "intended behavior" link - that is a boneheaded assumption to justify crippling /sys/module/kernel/parameters/consoleblank to mask other problems that should have been fixed instead of swept-under-the-rug by disabling default console blanking and powerdown -- that has worked flawlessly for the past 15 years. What kind of defect in reasoning makes it OK to break default behavior? None. If there is a problem with X due to some change in X or vt reordering that now makes blanking /dev/tty0 a problem for X users -- then fix X, don't break default vt blanking and powerdown. The type of backwards reasoning in https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017?comments=all that suggests breaking defaults instead of fixing the actual problem is what leads to a proliferation of unnecessary kernel parameters passed at boot or forces the creation of unnecessary startup services just to restore basic default terminal blanking and powerdown. That strikes me as completely unacceptable and a complete abdication to insure simple default features -- just work. I don't mean to beat a dead horse, but fix the problem, don't break default behavior. This type of fundamental behavior by the console should just work as it always has, not be something users now have jump through hoops adding startup files or passing kernel parameters just to restore simple, basic, default power-saving features. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1094452 http://bugzilla.opensuse.org/show_bug.cgi?id=1094452#c6 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@suse.com Assignee|kernel-maintainers@forge.pr |jslaby@suse.com |ovo.novell.com | --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- In anyway, I leave this to Jiri, who was on Cc in the affecting commit. -- You are receiving this mail because: You are on the CC list for the bug.