nautilus hangs when browsing home folder with mbox file in it

[Ori Hoch]

If a file called mbox is present in the home folder nautilus hangs.
Using ubuntu 8.04 - Linux adesktop 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux
I tried to provide a trace but I couldn't do it because nautilus hangs and doesn't crash

Steps to reproduce:

1. cd ~
2. touch mbox
3. using nautilus - browse the home folder
4. nautilus hangs
5. click the X icon - after a few seconds, click the 'force quit' button.
6. nautilus re-opens again on the home folder, and again is not responsive
7. cd ~
8. rm mbox
9. click the X icon then 'force quit'
10. nautilus re-opens and is working properly
11. repeat from step 1...

[Ori Hoch (ori-uumpa)]

might be similiar to bug #120070

[Pedro Villavicencio (pedro)]

thanks for the report, however the trace doesn't have symbols and no indication of a crash, may you please follow the instructions located at http://wiki.ubuntu.com/DebuggingProgramCrash , install the dbgsym packages and get a backtrace of the hang? further instructions about that can be found here: https://wiki.ubuntu.com/Backtrace#Already%20running%20programs ; thanks in advance.

[Ori Hoch (ori-uumpa)]

thanks, like I said the problem is that the program doesn't crash - it hangs, and I have to do a 'force quit' on it - so I don't know how to get a trace of the hang. I followed the guide for backtracing already running programs - that's the trace that is attached, but when nautilus hangs, gdb is not responsive - and when I do a 'force quit' on nautilus then gdb is responsive but then there is no info (when I do `backtrace full` I get nothing). If you can tell me how to get a trace of a hanging program I will be happy to do it, thanks.

[Sebastien Bacher (seb128)]

you just need to do ctrl-c in gdb to get the stacktrace while it's hanging

[Ori Hoch (ori-uumpa)]

thanks, unfortunately now it doesn't happen anymore... I guess you can close the bug if the information is not sufficient.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.