GNOME Bugzilla – Bug 394765
crash in Sessions: Distribution: Fedora Cor...
Last modified: 2007-04-25 09:56:32 UTC
Version: 2.17.2 What were you doing when the application crashed? Distribution: Fedora Core release 6 (Rawhide) Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc) BugBuddy Version: 2.17.3 System: Linux 2.6.19-1.2906.fc7 #0 SMP Sun Jan 7 21:02:25 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Enabled Memory status: size: 293478400 vsize: 293478400 resident: 18710528 share: 11411456 rss: 18710528 rss_rlim: -1 CPU usage: start_time: 1168371807 rtime: 85 utime: 72 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-session-properties' (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 46912496346736 (LWP 3501)] (no debugging symbols found) 0x000000369aa0d7c5 in waitpid () from /lib64/libpthread.so.0
+ Trace 100791
Thread 1 (Thread 46912496346736 (LWP 3501))
----------- .xsession-errors --------------------- ** (gnome-session-properties:3501): WARNING **: Could not save /usr/share/gnome/autostart/gnome-volume-manager.desktop file ** (gnome-session-properties:3501): WARNING **: Could not save /etc/xdg/autostart/beagle.desktop file ** (gnome-session-properties:3501): WARNING **: Could not save /etc/xdg/autostart/puplet.desktop file ** (gnome-session-properties:3501): WARNING **: Could not save /usr/share/gnome/autostart/nm-applet.desktop file GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
Offhand this looks like a bug either in orbit or in some accessibility code. I'm reassigning to atk as it appears prominently in the backtrace.
Hi Tom: I'm afraid not much can be made of that backtrace. Also, there's no indication of what the user was doing when the crash occurred. Looks like a crash on exit, is that correct? Also, if reproducible, please try with gail+at-spi HEAD. Standard boilerplate "need better stack trace" message follows...: Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** This bug has been marked as a duplicate of 416370 ***