Baobab won't start: Failed to register: Timeout was reached

[Alan Pope 🍺🐧🐱 🦄]

Baobab just won't start on 14.04 for me.

alan@wopr:~$ baobab
Failed to register: Timeout was reached
alan@wopr:~$

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: baobab 3.8.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 12 14:58:03 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-01-02 (799 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120102)
SourcePackage: baobab
UpgradeStatus: Upgraded to trusty on 2013-12-09 (93 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[goldencut (goldencut)]

For me it starts, but it takes some 7-10 seconds to come up. Lubuntu 14.04 ox x86.

[MakGreg (makgreg)]

As a workaround, for me it works with the root account (but not with my normal user account).

[NoBugs! (luke32j)]

So how can we further diagnose the issue? I see it too.

[Anton Sergeev (anton-sergeev77)]

I had the same problem.
I found out that meld already worked in some terminal, and then it was suspended. So I found terminal with suspended meld in background and resume it. After that meld began to work as always.
I think hard killing of "meld" processes may help too: `killall -9 meld`.

[Mark Jeronimus (mark-jeronimus)]

It happens to me when one of the file systems is busy (USB) or the network mount unreachable.
For reference, it also happens when specifying a known non-busy directory on the command-line, like /home/mark.
xdiskusage fails the same way with unavailable filesystems but works fine when specifying the directory.