GNOME Bugzilla – Bug 538408
crash in Open Folder:
Last modified: 2008-06-15 10:08:24 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Gion Memory status: size: 451543040 vsize: 451543040 resident: 32210944 share: 17485824 rss: 32210944 rss_rlim: 18446744073709551615 CPU usage: start_time: 1213484809 rtime: 489 utime: 412 stime: 77 cutime:5 cstime: 6 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 0x2b130dde8ba0 (LWP 6587)] (no debugging symbols found) 0x00002b130780cedf in waitpid () from /lib/libpthread.so.0
+ Trace 200470
Thread 1 (Thread 0x2b130dde8ba0 (LWP 6587))
----------- .xsession-errors (1335 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) LoadPlugin: failed to initialize shared library /home/sonat/.mozilla/plugins/libflashplayer.so [/home/sonat/.mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32] ** (gnome-system-monitor:8681): WARNING **: SELinux was found but is not enabled. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 522534 ***