GNOME Bugzilla – Bug 474388
crash in Computer: Reading
Last modified: 2008-02-21 10:52:39 UTC
Version: 2.18.3 What were you doing when the application crashed? Reading 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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: MurrinaGilouche Icon Theme: Echo Memory status: size: 701726720 vsize: 701726720 resident: 129064960 share: 42201088 rss: 129064960 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189069321 rtime: 6307 utime: 5839 stime: 468 cutime:6 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496380976 (LWP 3220)] (no debugging symbols found) 0x0000003827c0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 161005
Thread 1 (Thread 46912496380976 (LWP 3220))
----------- .xsession-errors (3102 sec old) --------------------- compiz (cubecaps) - Warn: Failed to load image: compizcap.png fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL default:0 ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL default:0 fixme:win:EnumDisplayDevicesW ((null),0,0x34f604,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x34d894,0x00000000), stub! ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL default:0 ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL default:0 fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet ...Too much output, ignoring rest... --------------------------------------------------
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 the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 507120 has been marked as a duplicate of this bug. ***
*** Bug 517839 has been marked as a duplicate of this bug. ***