GNOME Bugzilla – Bug 709330
When 'active-chart' set to 'treemap', baobab doesn't open and CPU usage is at 100%
Last modified: 2014-05-25 16:26:25 UTC
Fedora 20, jhbuilt from master (but it also happens with the version in the repos). I run baobab, either from gnome-shell or terminal and the window doesn't appear, nothing prints to the terminal, and my cpu usage on one core goes up to 100%. bleh
I experience the same problem on Arch Linux running baobab 3.10.1 For me, the program will run if I give it admin rights (gksu, gksudo, sudo, etc.), but otherwise it fails VERY silently. Someone said an strace might be useful so I did that and the last thing it prints before stopping is stat("/usr/bin/nautilus-connect-server", {st_mode=S_IFREG|0755, st_size=44704, ...}) = 0
OpenSuse 13.1 - the same problem noticed. After starting baobab 3.10.1 it doesn't display GUI and CPU utilization climbs to 100%. There is no problem when running as root. Last lines from strace when run as user 20:39:51 access("/usr/bin/X11/nautilus-connect-server", X_OK) = -1 ENOENT (No such file or directory) 20:39:51 access("/usr/X11R6/bin/nautilus-connect-server", X_OK) = -1 ENOENT (No such file or directory) 20:39:51 access("/usr/games/nautilus-connect-server", X_OK) = -1 ENOENT (No such file or directory) When run as root these lines are followed by 20:41:57 access("/usr/X11R6/bin/nautilus-connect-server", X_OK) = -1 ENOENT (No such file or directory) 20:41:57 access("/usr/games/nautilus-connect-server", X_OK) = -1 ENOENT (No such file or directory) 20:41:57 brk(0x1367000) = 0x1367000 20:41:57 poll([{fd=6, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=6, revents=POLLOUT}]) 20:41:57 writev(6, [{"<\0\2\0\35\0\340\2\213\4\5\0\36\0\340\2\34\0\340\2&\0\0\0\0\0\0\0006\2\2\0"..., 2644}, {"MIT-SHM", 7}, {"\0", 1}], 3) = 2652 20:41:57 poll([{fd=6, events=POLLIN}], 1, 4294967295) = 1 ([{fd=6, revents=POLLIN}])
Could you give the output of: $ gsettings get org.gnome.baobab.ui active-chart and try the following $ gsettings set org.gnome.baobab.ui active-chart rings
Perfect advice :) The setting was 'treemap'. When I changed to 'rings' baobab started without problem. To confirm I changed in GUI chart type to treemap and close baobab. It didn't start again. So it seems there is a bug related to chart type selected. When you know the solution it is not very serious. Thanx for help.
(In reply to comment #3) > Could you give the output of: > $ gsettings get org.gnome.baobab.ui active-chart > > and try the following > $ gsettings set org.gnome.baobab.ui active-chart rings I also performed the commands and the setting was already rings (possibly from an update?) and baobab now starts perfectly fine.
*** Bug 726672 has been marked as a duplicate of this bug. ***
Stefano, Sorry about the duplicate, I had checked in redhat.bugzilla and neglected to check here as well. Yes, it certainly is a duplicate and I can confirm that the active chart was set to 'treemap' and with it set to 'rings' baobab works as usual. I concur with the severity of 'normal' for this bug. Thank you for your time and producing such a useful tool! BR, John
*** Bug 727378 has been marked as a duplicate of this bug. ***
Fixed in commit 4501b534691552847d38db96e7d44cf665999939
*** Bug 722329 has been marked as a duplicate of this bug. ***