GNOME Bugzilla – Bug 422731
crash in Computer: clicking on a hyperlink ...
Last modified: 2007-03-31 00:45:59 UTC
Version: 2.16.2 What were you doing when the application crashed? clicking on a hyperlink firefox Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:00:19 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 573489152 vsize: 573489152 resident: 38494208 share: 16216064 rss: 38494208 rss_rlim: 0 CPU usage: start_time: 1174725817 rtime: 5672 utime: 4763 stime: 909 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912499439776 (LWP 3937)] 0x000000345640d96f in __libc_waitpid (pid=12995, stat_loc=0x7fff4ed376fc, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 122142
Thread 1 (Thread 46912499439776 (LWP 3937))
0x000000345640d96f 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); ----------- .xsession-errors --------------------- warning: .dynamic section for "/lib64/libgcc_s.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib64/libuuid.so.1" is not at the expected address warning: .dynamic section for "/usr/lib64/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/lib64/libmetacity-private.so.0" is not at the expected address warning: .dynamic section for "/lib64/libattr.so.1" is not at the expected address warning: .dynamic section for "/lib64/libacl.so.1" is not at the expected address --------------------------------------------------
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 ***