GNOME Bugzilla – Bug 495493
crash in Open Folder: infinity.xml -> wallpape...
Last modified: 2007-11-13 22:20:51 UTC
Version: 2.18.3 What were you doing when the application crashed? infinity.xml -> wallpapers box 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.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 423952384 vsize: 423952384 resident: 41181184 share: 34189312 rss: 41181184 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194670585 rtime: 22 utime: 14 stime: 8 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496467488 (LWP 8535)] (no debugging symbols found) 0x00000031d200d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 176720
Thread 1 (Thread 46912496467488 (LWP 8535))
----------- .xsession-errors --------------------- Initializing nautilus-open-terminal extension warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff5e5fd000 Initializing nautilus-image-converter extension Initializing gnome-mount extension seahorse nautilus module initialized Initializing nautilus-open-terminal extension warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff933fd000 Initializing nautilus-image-converter extension Initializing gnome-mount extension seahorse nautilus module initialized Initializing nautilus-open-terminal extension warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff9bffd000 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 436873 ***