GNOME Bugzilla – Bug 722329
Baobab times out and never starts
Last modified: 2014-05-25 16:26:25 UTC
Arch Linux: (Also with baobab-3.10, .x and git) With package baobab-3.10.1-1-x86_64.pkg.tar.xz installed I get the following when launching baobab (baobab:20700): GLib-GIO-CRITICAL **: Timeout was reached I get the same error if launching the git version EDIT: bizarrely, 3.10 works now What I did 1) Wait several months for this issue to resolve itself (after it suddenly appeared, for now obvious reason for myself, as far as i can tell) 2) Clone baobab git repo, compiled that, same issue. 3) Downgraded to baobab-3.8.2-1-x86_64.pkg.tar.xz - WORKS! 4) Decided to create this issue 5) Bizarrely: went back to 3.10 in order to retest for this issue. 3.10 works. No more timeout. I'll reboot and verify that it still works with 3.10 External factors: not sure about gnome shell 3.6 but definite upgrade from 3.8 -> 3.10 Install d-feet today Compiled baobab from source Also, what does baobab:20700 mean, line 20700 in baobab bin? Could you point me to the relevant vala exception handling/error message docs? Couldn't find anything relevant.
Created attachment 266462 [details] List of files in package 3.8.2
Created attachment 266463 [details] List of files in package 3.10.1
Rebooted, still works with the 'normal' 3.10 package. Which is weird, downgrading the package didn't replace or conflict any other packages as far as I can tell...
Created attachment 277151 [details] backtrace of baobab-3.10.1-1.fc20 eating 100% cpu at startup I can confirm this behavior. Baobab eats 100% CPU and never starts for me. I am using baobab-3.10.1-1.fc20 from Fedora 20 (+updates-testing). This is with no baobab folders in ~/.config/ and ~/.local/share/ and all dconf/GSettings preferences reset to defaults. See attached backtrace for details.
can you try what suggested at https://bugzilla.gnome.org/show_bug.cgi?id=709330#c3 ? Closing as duplicate for now. *** This bug has been marked as a duplicate of bug 709330 ***