GNOME Bugzilla – Bug 449151
crash in Computer:
Last modified: 2007-11-20 19:42:50 UTC
Version: 2.18.1 What were you doing when the application crashed? 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: 103112704 vsize: 103112704 resident: 32935936 share: 16248832 rss: 32935936 rss_rlim: 4294967295 CPU usage: start_time: 1182258420 rtime: 3109 utime: 2572 stime: 537 cutime:493 cstime: 43 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 -1208457504 (LWP 2954)] (no debugging symbols found) 0x001c9402 in __kernel_vsyscall ()
+ Trace 142170
Thread 1 (Thread -1208457504 (LWP 2954))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libgstaudio-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libXtst.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libXxf86vm.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libhal.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
*** Bug 467524 has been marked as a duplicate of this bug. ***
*** Bug 473986 has been marked as a duplicate of this bug. ***
*** Bug 454926 has been marked as a duplicate of this bug. ***
*** Bug 457531 has been marked as a duplicate of this bug. ***
*** Bug 468761 has been marked as a duplicate of this bug. ***
*** Bug 469352 has been marked as a duplicate of this bug. ***
*** Bug 469801 has been marked as a duplicate of this bug. ***
*** Bug 469990 has been marked as a duplicate of this bug. ***
*** Bug 469924 has been marked as a duplicate of this bug. ***
*** Bug 470049 has been marked as a duplicate of this bug. ***
*** Bug 470122 has been marked as a duplicate of this bug. ***
*** Bug 470758 has been marked as a duplicate of this bug. ***
*** Bug 471219 has been marked as a duplicate of this bug. ***
*** Bug 472867 has been marked as a duplicate of this bug. ***
*** Bug 472344 has been marked as a duplicate of this bug. ***
*** Bug 479590 has been marked as a duplicate of this bug. ***
*** Bug 477372 has been marked as a duplicate of this bug. ***
*** Bug 481472 has been marked as a duplicate of this bug. ***
*** Bug 482088 has been marked as a duplicate of this bug. ***
*** Bug 483769 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 491801 has been marked as a duplicate of this bug. ***
*** Bug 492452 has been marked as a duplicate of this bug. ***
*** Bug 492659 has been marked as a duplicate of this bug. ***
*** Bug 493915 has been marked as a duplicate of this bug. ***
*** Bug 494258 has been marked as a duplicate of this bug. ***
*** Bug 494478 has been marked as a duplicate of this bug. ***
this is the same issue as bug 417530 according to some .xsession-error output *** This bug has been marked as a duplicate of 417530 *** *** This bug has been marked as a duplicate of 417530 ***
*** Bug 498309 has been marked as a duplicate of this bug. ***