GNOME Bugzilla – Bug 436141
crash in CD/DVD Creator: Nautilus のツリー表示から「オーディオ」...
Last modified: 2007-05-07 20:30:15 UTC
What were you doing when the application crashed? Nautilus のツリー表示から「オーディオ」を参照しようとしたところ落ちました。 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.2948.fc6 #1 SMP Fri Apr 27 19:48:40 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 107233280 vsize: 0 resident: 107233280 share: 0 rss: 27066368 rss_rlim: 0 CPU usage: start_time: 1178373177 rtime: 0 utime: 4564 stime: 0 cutime:4229 cstime: 0 timeout: 335 it_real_value: 0 frequency: 0 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 -1208858928 (LWP 3161)] (no debugging symbols found) 0x00a2e402 in __kernel_vsyscall ()
+ Trace 132571
Thread 1 (Thread -1208858928 (LWP 3161))
----------- .xsession-errors (17 sec old) --------------------- warning: .dynamic section for "/usr/lib/libstdc++.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libattr.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libacl.so.1" 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 320020 ***