GNOME Bugzilla – Bug 469207
crash in Computer: open smb connect to Wind...
Last modified: 2007-08-22 13:39:50 UTC
Version: 2.18.3 What were you doing when the application crashed? open smb connect to Windows network 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 120737792 vsize: 120737792 resident: 42713088 share: 24215552 rss: 42713088 rss_rlim: 4294967295 CPU usage: start_time: 1187760716 rtime: 6045 utime: 4876 stime: 1169 cutime:9 cstime: 3 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 -1208772896 (LWP 2935)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 157106
Thread 1 (Thread -1208772896 (LWP 2935))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libesd.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgnomeui-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/libbonoboui-2.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libasound.so.2" 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 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 349551 ***