dbus puts system to sleep every 30 seconds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbus (Ubuntu) |
Confirmed
|
Critical
|
Unassigned |
Bug Description
After upgrading from 14.10 to 15.04, I found that the system was going to sleep every 30 seconds. This behavior does not manifest once I log into the graphical desktop (Lubuntu), but if I switch over to a virtual console, it manifests again.
A temporary fix has been to make /sys/power/state non-writable.
At first, I believed the problem was with systemd, but the problem continues after switching to upstart.
I believe the problem is in the dbus package, because I see this every 30 seconds in /var/log/syslog, coinciding with the laptop going to sleep:
Apr 29 07:46:58 socrates dbus[701]: [system] Activating service name='org.
Apr 29 07:46:58 socrates dbus[701]: [system] Successfully activated service 'org.freedeskto
Apr 29 07:46:58 socrates kernel: [ 529.289164] init: anacron main process (17760) killed by TERM signal
Apr 29 07:47:01 socrates anacron[18796]: Anacron 2.3 started on 2015-04-29
Apr 29 07:47:01 socrates anacron[18796]: Will run job `cron.daily' in 5 min.
Apr 29 07:47:01 socrates anacron[18796]: Will run job `cron.weekly' in 10 min.
Apr 29 07:47:01 socrates anacron[18796]: Jobs will be executed sequentially
Apr 29 07:47:30 socrates acpid: client connected from 19009[0:0]
Apr 29 07:47:30 socrates acpid: 1 client rule loaded
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: dbus 1.8.12-1ubuntu5
ProcVersionSign
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
CurrentDesktop: LXDE
Date: Wed Apr 29 07:53:42 2015
InstallationDate: Installed on 2010-04-30 (1824 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dbus
UpgradeStatus: Upgraded to vivid on 2015-04-27 (1 days ago)
Changed in dbus (Ubuntu): | |
importance: | Undecided → Critical |
Status changed to 'Confirmed' because the bug affects multiple users.