GNOME Bugzilla – Bug 354541
Crash when opening a folder from places
Last modified: 2006-09-09 22:54:19 UTC
Steps to reproduce: When i opened a bookmark from the places menu nautilus crashed. Nautilus also opened a lot of unresponding windows of my home folder. I'm using spatial nautilus with home=desktop set. I cannot reproduce this, but I hope the backtrace is of valid information. Stack trace: (gdb) bt
+ Trace 71688
Thread 1 (Thread -1226291536 (LWP 19802))
Other information: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.92 2006-08-22 (Ubuntu) BugBuddy Version: 2.15.92 Memory status: size: 74305536 vsize: 0 resident: 74305536 share: 0 rss: 16879616 rss_rlim: 0 CPU usage: start_time: 1157500381 rtime: 0 utime: 138 stime: 0 cutime:126 cstime: 0 timeout: 12 it_real_value: 0 frequency: 0
unique trace 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.
Ok I just got another crash and a similar backtrace. However when I used the simple dupe finder with my new stacktrace with debugging symbols it pointed me to http://bugzilla.gnome.org/show_bug.cgi?id=353629 I assume this is a duplicate then? Anyways here is my stacktrace. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 73146368 vsize: 0 resident: 73146368 share: 0 rss: 16945152 rss_rlim: 0 CPU usage: start_time: 1157839665 rtime: 0 utime: 155 stime: 0 cutime:130 cstime: 0 timeout: 25 it_real_value: 0 frequency: 0 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 -1226955088 (LWP 5547)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72006
Thread 1 (Thread -1226955088 (LWP 5547))
thank you for responding, indeed this is a duplicate of bug 353629 what version of Gnome are you running? In case it is newer than 2.15.92 please set your version in the other report. thanks. *** This bug has been marked as a duplicate of 353629 ***