← Back to team overview

kernel-packages team mailing list archive

[Bug 1580553] Re: Inactive screen on laptop turns back on immediately after blanking


ubuntu-bug and its documentation makes it very hard to post a bug that
is actually related to power management. I told it that it was an apport
bug in order to get into the system at all.

** Package changed: apport (Ubuntu) => linux-meta (Ubuntu)

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.

  Inactive screen on laptop turns back on immediately after blanking

Status in linux package in Ubuntu:

Bug description:
  Inactive laptop screen fades to blank, then immediately brightens
  again showing the login screen, and stays lit.

  This happens whether the laptop if charging or running on battery.

  The problem occurs with both the gnome screensaver package installed
  and with xscreensaver.

  Indicators in the status bar in addition to the default ones include 
  Classic Menu indicator
  Dropbox indicator
  System Load indicator
  (I have been running the same set of indicators on a different, 14.04, laptop without them interfering with screen blanking behavior)

  Charging with the screen lit seems very slow and discharge seems fast,
  but this is a new laptop that came with 16.04 installed, so I don't
  really have a basis for comparison.

  I have not installed TLP on this laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashReports: 664:108:116:11903:2016-05-07 00:23:37.423810907 -0500:2016-05-07 00:23:37.423810907 -0500:/var/crash/_sbin_upstart.108.crash
  CurrentDesktop: Unity
  Date: Wed May 11 06:03:10 2016
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2016-04-28T21:07:24.472000

To manage notifications about this bug go to: