After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 726672 - Baobab consumes 100% processor, no GUI
Baobab consumes 100% processor, no GUI
Status: RESOLVED DUPLICATE of bug 709330
Product: baobab
Classification: Core
Component: general
3.10.x
Other Linux
: Normal blocker
: ---
Assigned To: Baobab Maintainers
Baobab Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-03-19 02:34 UTC by John Webb
Modified: 2014-03-19 09:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John Webb 2014-03-19 02:34:06 UTC 
Distribution:  Fedora 20 3.13.6-200.fc20.x86_64
CPU:  AMD A10-5800K 3.8 G Quad Core
Motherboard:  Gigabyte GA-F2A85XM-D3H
Memory: 8 GB

When starting "Disk Usage Analyzer" within F20, the application appear briefly in the top bar of Gnome 3, but soon after disappears without ever being accessible.  baobab continues to run, consuming 100% of one processor's resources (as reported by conky).  This continues indefinitely, even if allowed to run overnight and throughout the next day.  
I have tried re-installing baobab, both from yum and the new 'software' application in F20, I have also re-installed dependent packages atk, glibc, cairo-gobject, cairo, gtk3, gdk-pixbuf2, glib2 & pango without changing this behaviour.  Rolling back the core to the 'rescue' configuration available during grub startup (F19) does not resolve the issue.  Nothing is apparent in /var/log/messages to indicate a problem, nor can I find any other log files with any information.
Comment 1 Stefano Facchini 2014-03-19 09:13:04 UTC 
probabily a dup of bug 709330, can you try what is suggested there at comment 3?

*** This bug has been marked as a duplicate of bug 709330 ***