Nautilus hangs and uses 100% cpu on /usr/share/rhythmbox

[Ludger Solbach]

Binary package hint: nautilus

I have to kill and restart nautilus. On restart by clicking on a folder shortcut in the panel, the icons on the desktop are missing.
Nautilus on Ubuntu 9.10 with all updates.

[Bruno Girin (brunogirin)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

I tried to reproduce this bug by opening a Nautilus window and navigating to /usr/share/rhythmbox but I cannot reproduce. I also made sure I had the latest updates before doing so. It would help us a lot if you could attach the details of your system by running the following in a terminal:

apport-collect 529406

[Ludger Solbach (lsolbach)]

Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.1-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
Uname: Linux 2.6.31-19-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[David Tombs (dgtombs)]

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!

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.