GNOME Bugzilla – Bug 531141
crash in Home Folder:
Last modified: 2008-05-02 23:19:36 UTC
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 Fri Apr 18 23:08:22 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola Memory status: size: 438099968 vsize: 438099968 resident: 30556160 share: 18116608 rss: 30556160 rss_rlim: 18446744073709551615 CPU usage: start_time: 1209766688 rtime: 483 utime: 448 stime: 35 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2b0d4dfd1b80 (LWP 3929)] 0x00002b0d47af6edf in waitpid () from /lib/libpthread.so.0
+ Trace 196719
Thread 1 (Thread 0x2b0d4dfd1b80 (LWP 3929))
----------- .xsession-errors (446 sec old) --------------------- (npviewer.bin:4020): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (npviewer.bin:4020): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (npviewer.bin:4020): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (npviewer.bin:4020): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (npviewer.bin:4020): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (npviewer.bin:4020): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (npviewer.bin:4020): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/immodules/im-cedilla.so: wrong ELF class: ELFCLASS64 (npviewer.bin:4020): Gtk-WARNING **: Loading IM context type 'cedilla' failed --------------------------------------------------
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 ***