GNOME Bugzilla – Bug 463563
crash in Computer: clicked on config.sh fil...
Last modified: 2007-08-21 20:43:23 UTC
Version: 2.16.2 What were you doing when the application crashed? clicked on config.sh file to edit it in gedit 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.2962.fc6 #1 SMP Tue Jun 19 18:50:05 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 607985664 vsize: 607985664 resident: 77422592 share: 51191808 rss: 77422592 rss_rlim: 0 CPU usage: start_time: 1185604083 rtime: 7026 utime: 5769 stime: 1257 cutime:0 cstime: 19 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 46912496437184 (LWP 4697)] 0x000000395ba0d9ff in __libc_waitpid (pid=4864, stat_loc=0x7fff4d338b5c, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 152883
Thread 1 (Thread 46912496437184 (LWP 4697))
0x000000395ba0d9ff 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); ----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib64/libaudiofile.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libgnome-desktop-2.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/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/lib64/libSM.so.6" is not at the expected address ...Too much output, ignoring rest... --------------------------------------------------
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 ***