← Back to team overview

desktop-packages team mailing list archive

[Bug 1393855] Re: System suspends after closing the screen lid


Thank you for your bug report, do you still have the issue? could you
provide your ~/.cache/upstart/unity-settings-daemon.log?

** Package changed: dbus (Ubuntu) => unity-settings-daemon (Ubuntu)

** Changed in: unity-settings-daemon (Ubuntu)
   Importance: Undecided => Low

** Changed in: unity-settings-daemon (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.

  System suspends after closing the screen lid

Status in unity-settings-daemon package in Ubuntu:

Bug description:

  I adjusted the behaviour of my system (in system setting -> power
  management) as the folloing: After I close the screen lid nothing
  shall happen, regardless of the connection to the power adapter.

  However, after closing the lid the system hibernates after a time lag
  of about 4-5 seconds. Even if I opened up the lid again before.

  I can use this to suspend the system even when the screen is locked
  (which comes in handy because I am occasionally experiencing the lack
  of a passwort prompt).

  Please note that this is only one bug of a series of bugs, most of
  them concerning the screen lock. They are probably all related. I will
  provide the links to the bug reports later, until then you can find
  them in my personal profile.


  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dbus 1.6.18-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:29:14 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
   PATH=(custom, no user)
  SourcePackage: dbus
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to: