Summary: | Nautilus consumes 100% cpu when disabled from managing desktop | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | rafnov <rafnov> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
rafnov
2010-04-02 18:28:40 UTC
I suppose that you probably use nautilus-2.26.x, mostly because If I remember correctly this bug was fixed upstream in 2.28 dev cycle. @herd wasn't it ? Well, please attach at least the output of your emerge --info Created attachment 226309 [details]
emerge --info
eix -I nautilus
[I] gnome-base/nautilus
Available versions: 2.24.2-r3 2.26.4 2.26.4-r1 (~)2.28.1 (~)2.28.2 (~)2.28.4 (~)2.28.4-r1 {beagle debug doc gnome test tracker xmp}
Installed versions: 2.28.4-r1(15:09:00 30.03.2010)(-beagle -doc -gnome -test -xmp)
This is actually a known behavior since 2.26, I suggest you use the search feature of bugzilla or re-read the gnome 2.26 migration guide which probably gives a description of the problem and a solution. That solution is just a workaround but if there is no real solution workarounds seem necessary. I've got another one: copy /usr/share/applications/nautilus.desktop to ~/.config/autostart and set X-GNOME-AutoRestart=false. This is much cleaner and simpler for me, but main advantage is that it doesn't get overwritten every nautilus emerge. reopening to mark proper status *** This bug has been marked as a duplicate of bug 266398 *** |