deja-dup-monitor process survives after logout

Bug #1051811 reported by Michael Terry on 2012-09-17
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Déjà Dup
deja-dup (Ubuntu)

Bug Description

This seems to be a new symptom since quantal. Maybe gnome-session changed some behavior?

When gnome-session exits in quantal, it doesn't explicitly kill the processes it spawned. Instead it relies on the processes noticing that the dbus session is gone and exit.

deja-dup-monitor does not notice this. So you will accumulate one new process every time you log out and back in. This can actually be presented to the user as an error if the old processes try to kick off a backup, and the deja-dup process will not be able to claim a bus name, so it thinks (erroneously, but that's a separate bug) that an existing backup is happening, and throws up a dialog like "Another backup process is already running".

To reproduce, simply log in, wait a few minutes, run:
ps aux | grep deja-dup-monitor
To make sure it started, then log out and back in. After another few minutes, if you run the ps command again, you should see two.

A good fix would be to watch when the dbus session exits and exit with it.

Related branches

Michael Terry (mterry) on 2012-09-18
Changed in deja-dup:
milestone: none → 23.92
status: New → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package deja-dup - 23.92-0ubuntu1

deja-dup (23.92-0ubuntu1) quantal; urgency=low

  * New upstream release
    - Only allow one deja-dup-monitor process at a time (LP: #891797,
      LP: #1051811)
 -- Michael Terry <email address hidden> Tue, 18 Sep 2012 13:15:04 -0400

Changed in deja-dup (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers