The Ubuntu Power Consumption Project

accounts-daemon is progressively causing more wakeups over time

Bug #1234289 reported by Colin Ian King
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Ubuntu Power Consumption Project
Fix Released
Low
Unassigned
accountsservice (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Over the past few months accounts-daemon has been increasing the number of wakeup events it generates, see:

http://reports.qa.ubuntu.com/power/eventstat/image/2736/machine/1/task/accounts-daemon/details/

In April 2013 it was averaging about 13.5 wakeups per minute, now it has increased to 17.5. This isn't much overall, but it does seem like the trend is upwards and every wakeup takes the CPU out of deep sleep and hence consumes a little more power.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, it seems there was an increase in wakeups on 2013-08-13

Looking to https://launchpad.net/ubuntu/+source/accountsservice/+changelog we didn't have changes in the package around then, it's likely that the issue is rather a client app making more calls to the service...

Changed in accountsservice (Ubuntu):
importance: Undecided → Low
Revision history for this message
Colin Ian King (colin-king) wrote :

Sebastien, is their a way to track the offending client app down? I'd like to get to the root of this issue.

Revision history for this message
Sebastien Bacher (seb128) wrote :

you can probably use dbus-monitor and try to see what is talking to org.freedesktop.Accounts

Colin Ian King (colin-king)
affects: accountsservice (Ubuntu) → ubuntu-power-consumption
Changed in accountsservice (Ubuntu):
importance: Undecided → Low
Revision history for this message
Colin Ian King (colin-king) wrote :

running strace on one of the treads shows the culprit:

poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}], 2, 3998) = 0 (Timeout)
inotify_add_watch(8, "/etc/gdm", IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR) = -1 ENOENT (No such file or directory)
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}], 2, 3996) = 0 (Timeout)
inotify_add_watch(8, "/etc/gdm", IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR) = -1 ENOENT (No such file or directory)
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}], 2, 3996) = 0 (Timeout)
inotify_add_watch(8, "/etc/gdm", IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR) = -1 ENOENT (No such file or directory)

for some reason it is polling every 4 seconds and adding a watch on a non-existent /etc/gdm directory

Sebastien Bacher (seb128)
Changed in accountsservice (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package accountsservice - 0.6.35-0ubuntu7

---------------
accountsservice (0.6.35-0ubuntu7) trusty; urgency=medium

  * debian/patches/0007-add-lightdm-support.patch:
    - updated to not keep polling on an inexistant gdm (or lightdm)
      configurations, fixed the code checking if gdm is running as well
      (thanks Lars for hints on how to do that one correctly) (lp: #1234289)
 -- Sebastien Bacher <email address hidden> Fri, 17 Jan 2014 18:09:20 +0100

Changed in accountsservice (Ubuntu):
status: Fix Committed → Fix Released
Colin Ian King (colin-king)
Changed in ubuntu-power-consumption:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.