Description of problem: This morning I was following the F13 Test Day for palimpsest. After closing palimpsest, I'm seeing quite a high CPU load from the process gvfs-gdu-volume monitor: 2986 rawhide 20 0 1010M 214M 32132 S 12.0 2.7 2:56.37 /usr/lib64/firefox-3.6/firefox 2471 rawhide 20 0 371M 4896 3032 S 7.0 0.1 2:06.70 /usr/libexec/gvfs-gdu-volume-monitor 10536 root 20 0 17684 1556 1032 R 5.0 0.0 0:14.17 htop Version-Release number of selected component (if applicable): gvfs-1.5.5-1.fc13.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hi, I notice the same problem. It happens when USB storage devices are connected to the PC. Actually, it seems the CPU load increases with the number of devices, like the daemon is continuously checking the devices. It also happens with "gdu-notification-daemon", i.e. both daemons seem to use all the available CPU. Killing the daemons solves the CPU problem, but leaves the notification and related functionality (desktop icon, for example) not working. Hope this helps, bye, pg
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Hi, to the reporter or assignee, please update to F14, since the issue is still present there. bye, pg
Would be interesting to get output of `udevadm monitor`. Or maybe even `udisks --monitor-detail`. Please make sure to test this on Fedora 15, a lot has been changed since Fedora 14.
Hi, about F15, same story. So no change, in this respect. About "udevadm monitor" and "udisks --monitor-detail", how exactly should those be used? I tried, but I did not get any meaningful output. I mean, nothing at all after the hot-plug, some device discovery during hot-plug. Any hints? Thanks, bye, pg
Maybe the "needinfo" needs to be cleared? pg
2247 20 0 306m 8776 2968 R 98.5 0.2 4:16.38 gvfs-gdu-volume ^^^^ This is in rawhide as of 20110725 and so I suspect it will be in 16 branched. Anyone: what is going on, please?
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping