Here's the change that was made: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/zesty/commit/?id=a87ae50beda8c46c543b39e19070549cf355eb65
It's just the default of the consoleblank= kernel parameter. You can override it by specifying that parameter to the kernel at boot time (eg. via /etc/default/grub) If someone could test and document exact steps to do this override in this bug please, that'd be useful to users and I'd appreciate it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp