Thank you for taking the time to write this up and helping to make Ubuntu better.
As far as I understand, some of you consider this to be a matter of the default configuration shipped by Ubuntu, rather than kernel DPMS functionality itself not working when configured to do so. Others seem to be reporting that kernel DPMS functionality does not work at all. I'm unclear which is which, but the original reporter described this problem as solved in comment 24 and that was based on the default configuration, not on non-functional blanking as required when configured. On that basis, I'm marking this particular bug, as reported and suggested by the original reporter, as Invalid. If you have a problem getting some specific blanking functionality to work *when configured to do so*, please file a new, separate bug for that, making it clear what you think isn't working (blanking or DPMS) and describing exactly how you have configured your system such that you believe it should work. If you object to Ubuntu's *default configuration* as changed in the resolution to bug 869017, then please start a discussion on that on the mailing list (https://lists.ubuntu.com/mailman/listinfo/ubuntu-server) or on the community forum (https://community.ubuntu.com/c/server) and, following discussion, the Ubuntu Server Team will make a final decision on what the default should be (I'm claiming this decision for the Ubuntu Server Team since this is clearly a server question since it's outside the scope of Ubuntu Desktop). You can file a bug to have the default changed if you like, but since we already made the decision to change the default in bug 869017, we're only going to mark it Won't Fix pending further discussion as a decision was already previously made. Otherwise we'll just end up flip-flopping between defaults every release, which is clearly bad for everyone. The better approach would be to seek consensus considering both sides which would be better done in a general discussion and not a bug that presumes a conclusion by only considering one side of the discussion. -- 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/1767568 Title: Console DPMS is not enabled by default in Ubuntu Server 18.04 Status in linux package in Ubuntu: Confirmed Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description: Ubuntu 18.04 LTS Release: 18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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
