[Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)

Robie Basak 869017 at bugs.launchpad.net
Sun Jul 21 23:14:27 UTC 2019


On Sun, Jul 21, 2019 at 09:59:40PM -0000, atterdag wrote:
> I have to concur that it must this change is really a detriment to
> people that still use Ubuntu on physical servers - i.e. running
> OpenStack hosts. Fixing one problem by creating another problem is
> really poor problem management.

I don't see how we created another problem. We changed the default,
that's all. We thought the new default would be more suitable for more
users. Clearly not everyone will agree with the default - that's the
nature of defaults, and why the behaviour is configurable.

If you think that a different default would be better for Ubuntu, by all
means let's discuss that, as I described by suggesting a venue for that
discussion in the previous comment. But it doesn't follow that a default
not suitable in your particular situation is a problem in general.

If on the other hand the problem you're describing is not a matter of
the default configuration, then please file your own bug with specific
details.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to kbd 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



More information about the foundations-bugs mailing list