GNOME Bugzilla – Bug 444242
crash in Home Folder: opened smb share
Last modified: 2007-06-22 18:16:04 UTC
What were you doing when the application crashed? opened smb share Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 179875840 vsize: 179875840 resident: 43077632 share: 23236608 rss: 43077632 rss_rlim: 4294967295 CPU usage: start_time: 1181000732 rtime: 3420 utime: 3198 stime: 222 cutime:298 cstime: 19 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 -1209108768 (LWP 2630)] [New Thread -1260926064 (LWP 30909)] (no debugging symbols found) 0x007b1402 in __kernel_vsyscall ()
+ Trace 138369
Thread 1 (Thread -1209108768 (LWP 2630))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libpoppler.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgnome-window-settings.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpanel-applet-2.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libmetacity-private.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 433983 ***