Hi Ludger, thanks for the apport-collect information. xsession-errors definitely shows nautilus freaking out. It would be great if we could get a "backtrace" of the point of error.
Here are the steps to do so: 1) Install nautilus-dbg and gdb: sudo apt-get install nautilus-dbg gdb. 2) Kill the current nautilus: killall nautilus 3) Run the debugger with: G_DEBUG=fatal_criticals gdb nautilus 4) Finish the steps under "Generation": <https://wiki.ubuntu.com/Backtrace#Generation>. (We left off partly through #3.) If you could also report the directory listing of /usr/share/rhythmbox from the command line, that would be excellent. Just run "ls -l /usr/share/rhythmbox >directory.txt" and attach directory.txt here. This will pinpoint the problem. Thank you! ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- Nautilus hangs and uses 100% cpu on /usr/share/rhythmbox https://bugs.launchpad.net/bugs/529406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
