GNOME Bugzilla – Bug 339605
Nautilus random crash
Last modified: 2006-12-05 23:33:12 UTC
Steps to reproduce: 1. open nautilus 2. use nautilus 3. crash Stack trace: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/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) (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 46912497485280 (LWP 2663)] [New Thread 1074006352 (LWP 2677)] (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) 0x0000003c9990cb7f in waitpid () from /lib64/libpthread.so.0
+ Trace 67819
Thread 1 (Thread 46912497485280 (LWP 2663))
Other information: I use FC5 on x86_64 architecture and gnome 2.14.1.
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.
*** Bug 340476 has been marked as a duplicate of this bug. ***
Sorry but I can'nt repoduce this ...
Thanks, closing. Feel free to reopen it if you can reproduce it again.
*** Bug 348882 has been marked as a duplicate of this bug. ***
*** Bug 342778 has been marked as a duplicate of this bug. ***
Duplicates, reopening.
*** Bug 349316 has been marked as a duplicate of this bug. ***
*** Bug 349533 has been marked as a duplicate of this bug. ***
*** Bug 349905 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > 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. > i have ubuntu dapper and this address doesnt help. Bug-Buddy always writes "(no debugging symbols found)" although i installed these -dbg packages.
with libglib2.0-0-dbg libgnomevfs2-0-dbg libgtk2.0-0-dbg nautilus-dbg you should have most of the debug symbols needed on the backtrace
(In reply to comment #12) > with libglib2.0-0-dbg libgnomevfs2-0-dbg libgtk2.0-0-dbg nautilus-dbg you > should have most of the debug symbols needed on the backtrace > bonjour sebastien ;) i get these errors in synaptic: libgnomevfs2-0-dbg: Hängt ab: »libgnomevfs2-0 (=2.14.1-0ubuntu8)«, aber es wird »2.14.2-0ubuntu1« installiert. nautilus-dbg: Hängt ab: »nautilus (=2.14.1-0ubuntu9)«, aber es wird »2.14.3-0ubuntu1« installiert. in other words: libgnomevfs2-0-dbg needs »libgnomevfs2-0 (=2.14.1-0ubuntu8)« but »2.14.2-0ubuntu1« will be installed. nautilus-dbg needs »nautilus (=2.14.1-0ubuntu9)« but »2.14.3-0ubuntu1« will be installed. this doesnt give me any information really.
looks like dapper-updates is not activated for universe
oh yea. i can reproduce the bug as often as you want. with other words im using konqueror now :P here you go: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225464128 (LWP 5124)] [New Thread -1227318352 (LWP 5131)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 70086
Thread 1 (Thread -1225464128 (LWP 5124))
On my ubuntu 6.06 nautilus, this (?) crash occurs when opening a folder containg the following files in pictogram mode (ctrl+1) nathalie_notule.doc offerte_wouter_molenbroek.doc 2GSM+uit_eli.svg nathalie_offerte.doc verbodentelefoons_jamie.png After the 1st crash, als the opening of a new nautilus window of /home/barry keeps on crashing. since nautilus just is not going to show a pictogram of the 2GSM+uit_eli.svg other than a watch, i suppose it is while creating a preview icon for this file, that we crash. Confirm, nautilus crashes when only that file is in a specific directory. a name change does not really imporvo usage, after i renamed it to file.svg, the nautilus window lags.
Created attachment 70790 [details] nautilus crashes creating a preview pictogram of this file the svg file is from inkscape, a xml format of course
Hi, I got another backtrace for you guys: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225435456 (LWP 5335)] [New Thread -1227306064 (LWP 5363)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 70549
Thread 1 (Thread -1225435456 (LWP 5335))
best regards coresniper
no way, barry. i tried every single file in the directory and it was two SWF (flash) files that made nautilus crash.
erm so we have 3 different traces now for 3 different problems. We focus on one problem per report in order not to get confused (which is about to happen here). the secons trace from comment #15 (timo) is a crash in the libswfdec shockwave library that is *not* part of Gnome. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome. The trace from comment #18 (florian Lütkebohmert) is the trace from bug 34348 and totally unrelated to this problem. the trace in the other report is just as good as this one, so there is no need to copy it there. I cannot reproduce the crash on the xml document with Gnome 2.14 nor with Gnome 2.16 however we still need a better trace. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
stacktraces similar to bug 350975 and to bug 343488.
This is definately bug 343488. *** This bug has been marked as a duplicate of 343488 ***
*** Bug 382492 has been marked as a duplicate of this bug. ***