GNOME Bugzilla – Bug 490515
crash in Open Folder:
Last modified: 2007-10-26 16:47:47 UTC
Version: 2.18.3 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 58843136 vsize: 58843136 resident: 24883200 share: 19595264 rss: 24883200 rss_rlim: 4294967295 CPU usage: start_time: 1193389624 rtime: 66 utime: 60 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208305952 (LWP 6273)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173029
Thread 1 (Thread -1208305952 (LWP 6273))
----------- .xsession-errors (10 sec old) --------------------- end from FAM server connection end from FAM server connection end from FAM server connection end from FAM server connection Fönsterhanterarvarning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a050f2 (GIMP) Fönsterhanterarvarning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Initializing nautilus-open-terminal extension Initializing nautilus-open-terminal extension Initializing nautilus-open-terminal extension Cannot access memory at address 0xbfe88c58 /usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file: Couldn't get registers: No such process. Quitting: ptrace: No such process. Initializing nautilus-open-terminal extension Initializing nautilus-open-terminal extension --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 439977 ***