Description of problem: When i start "nautilus" from the menu, I got 30 to 60 sec. high cpu usage from gnome-shell. The mouse cursor displays "backgroud activity" meanwhile and system slows down for this amount of time. starting "nautilus" from a terminal works fine and without any noticeable cpu usage and mouse cursor does not change. Version-Release number of selected component (if applicable): gnome-shell-extension-user-theme-3.4.0-1.fc17.noarch gnome-shell-extension-weather-0-0.2.git5c61d80.fc17.noarch gnome-shell-extension-noripple-2.0-1.fc17.noarch gnome-shell-3.4.1-5.fc17.x86_64 gnome-shell-extension-remove-accessibility-icon-20111008-3.fc17.noarch gnome-shell-extension-common-3.4.0-1.fc17.noarch nautilus-image-converter-0.3.1-0.3.git430afce31.fc17.x86_64 nautilus-sendto-3.0.2-2.fc17.x86_64 nautilus-3.4.2-5.fc17.x86_64 tracker-nautilus-plugin-0.14.1-1.fc17.x86_64 nautilus-pastebin-0.5.0-6.fc17.x86_64 nautilus-extensions-3.4.2-5.fc17.x86_64 nautilus-sound-converter-3.0.2-1.fc17.x86_64 file-roller-nautilus-3.4.2-1.fc17.x86_64 seahorse-nautilus-3.4.0-2.fc17.x86_64 gtkhash-nautilus-0.6.0-1.fc17.x86_64 nautilus-python-1.1-2.fc17.x86_64 nautilus-open-terminal-0.19-4.fc17.x86_64 totem-nautilus-3.4.2-1.fc17.x86_64 nautilus-dropbox-1.4.0-1.fc10.x86_64 tnef-nautilus-1.4.8-5.2.fc17.x86_64 gnome-mplayer-nautilus-1.0.6-2.fc17.x86_64 brasero-nautilus-3.4.1-1.fc17.x86_64 evince-nautilus-3.4.0-2.fc17.x86_64 How reproducible: Always Steps to Reproduce: 1. launch nautilus from dash or menu 2. watch cpu usage of the process gnome-shell Actual results: Long background activity, high cpu usage over 30 to 60 sec. Expected results: no high cpu usage, no large background activity Additional info: launching nautilus from terminal works fine and as expected and without high cpu usage of gnome-shell.
Seen this too. Easily reproducible. Fresh default F17 install. Just run nautilus and watch the CPU activity.
Just reproduced it on i386 too. Fresh install + all updates
Any advice how to track this down? It is REALLY annoying. Since the mouse cursor is changing to "background activity", which makes it very difficult to navigate, because the pointer becomes a circle shape. It happens too, when I open a file via right click "open with gedit" for instance. As soon as I leave the gedit window, the pointer change, signaling activity. Any advice is welcome. Thanks.
This seems to have something to do with having odd filesystems mounted. gnome-shell is giving me log messages like this when I start it with '-r': JS LOG: Unable to guess content types on added mount private: Gio.IOErrorEnum: mount doesn't implement content type guessing JS LOG: Unable to guess content types on added mount TOURO: Gio.IOErrorEnum: mount doesn't implement content type guessing It's also giving me this, which I'm guessing might be a problem, but is also not likely related to the nautilus issue: JS LOG: Could not set property status on remote object /org/gnome/SessionManager/Presence: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I'm getting this on Fedora 19 x86_64
I'm also experiencing very high cpu usage (one core at 100% - 50% overall) from nautilus on F19 x86_64. When I kill the process, everything is back to normal. I haven't been able to reproduce it intentionally, it just occurs from time to time with as long as few days passing between the occurences. I'll provide more info when I manage to reproduce it.
Could be a duplicate of Bug 975592
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.