GNOME Bugzilla – Bug 532505
crash in Home Folder: accessing files using sm...
Last modified: 2008-05-10 18:16:57 UTC
What were you doing when the application crashed? accessing files using smb://computer/dir Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Frozen Plastic Icon Theme: gTangish-2.0 Memory status: size: 94044160 vsize: 94044160 resident: 39079936 share: 17510400 rss: 39079936 rss_rlim: 4294967295 CPU usage: start_time: 1210428315 rtime: 916 utime: 826 stime: 90 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6fa7720 (LWP 3272)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197389
Thread 1 (Thread 0xb6fa7720 (LWP 3272))
----------- .xsession-errors --------------------- (bug-buddy:5180): Gtk-WARNING **: Theme directory 32x32/emotes of theme gTangish-2.0 has no size field (bug-buddy:5180): Gtk-WARNING **: Theme directory 32x32/mimetypes of theme gTangish-2.0 has no size field (bug-buddy:5180): Gtk-WARNING **: Theme directory 32x32/places of theme gTangish-2.0 has no size field (bug-buddy:5180): Gtk-WARNING **: Theme directory 32x32/status of theme gTangish-2.0 has no size field warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***