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
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`.
--
Yo
So how can we further diagnose the issue? I see it too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to baobab in Ubuntu.
https://bugs.launchpad.net/bugs/1291427
Title:
Baobab won't start: Failed to register: Timeout was reached
Statu
As a workaround, for me it works with the root account (but not with my
normal user account).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to baobab in Ubuntu.
https://bugs.launchpad.net/bugs/1291427
Title:
Baobab won't start: Failed t
For me it starts, but it takes some 7-10 seconds to come up. Lubuntu
14.04 ox x86.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to baobab in Ubuntu.
https://bugs.launchpad.net/bugs/1291427
Title:
Baobab won't start: Failed to register:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: baobab (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to baobab in Ubuntu.
https://bugs.launchpad.net/bugs/129142
6 matches
Mail list logo
