GNOME Bugzilla – Bug 345300
Nautilus crash (while downloading tarball?)
Last modified: 2007-06-24 22:03:37 UTC
Steps to reproduce: Description of the crash: While downloading a tarball in firefox to the desktop and looking at mc in a gnome-terminal nautilus suddenly popped up an error dialog. Steps to reproduce the crash: 1. Download http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.16.15.tar.gz to your desktop? Stack trace: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226188576 (LWP 4517)] [New Thread -1227867216 (LWP 4531)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 68922
Thread 1 (Thread -1226188576 (LWP 4517))
Other information: Expected Results: No crash. How often does this happen? Haven't tried to reproduce it yet. Additional Information: Linux Distro: Ubuntu Dapper
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Yeah I know about the lack of symbols... Perhaps if buggy buddy had an option saying "reload core after grabbing symbols" or "save core for later?" we could reduce the number of these cases. There's no point my installing the symbols if I can't reproduce the bug because I don't have a core file to load up reread. Close this INCOMPLETE and I'll reopen it if I find a way to reproduce it.
Yeah, I think fer has some improvements along those lines planned for bug-buddy, but yes it does suck that we don't have them yet. Sorry about that. Anyway, I'll close as incomplete as you say and you can reopen when you have additional info. :)
*** Bug 353461 has been marked as a duplicate of this bug. ***
*** Bug 348200 has been marked as a duplicate of this bug. ***
duplicates, reopening
Please see http://live.gnome.org/GettingTraces and install the gnome-vfs debugging package
*** Bug 355288 has been marked as a duplicate of this bug. ***
*** Bug 360739 has been marked as a duplicate of this bug. ***
*** Bug 362926 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
*** Bug 444244 has been marked as a duplicate of this bug. ***