Brave guy at http://www.linuxquestions.org/questions/linux-newbie-8
/what-is-gvfsd-metadata-4175458624/ proposes more permanent workaround:
chmod -x /usr/lib/gvfs/gvfsd-metadata. If you think about it for a
bit, that solution has its merit: if you already have your metadata in
your file system,
For what it's worth, I'm seeing this issue (100% CPU usage, Gnome
desktop hangs completely on start) with Jaunty installed from http
://old-releases.ubuntu.com/ubuntu/ , running in a chroot under Android
on a Tegra2 tablet %).
--
You received this bug notification because you are a member of
Installing http://old-releases.ubuntu.com/ubuntu/pool/main/g/gnome-
keyring/gnome-keyring_2.28.1-0ubuntu1_armel.deb (using dpkg -i --force-
all) makes desktop not hang on start (like with 2.26.1-0ubuntu1), but
gnome-keyring-daemon still eats 100% CPU.
So, rm
