GNOME Bugzilla – Bug 539160
crash in Evolution Mail and Calendar: nothing... it crashed wh...
Last modified: 2008-07-23 13:04:07 UTC
What were you doing when the application crashed? nothing... it crashed when evolution was open but I wasn't using it. Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.2 2008-05-28 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25.6-55.fc9.i686 #1 SMP Tue Jun 10 16:27:49 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499902 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 172441600 vsize: 172441600 resident: 44146688 share: 24985600 rss: 44146688 rss_rlim: 4294967295 CPU usage: start_time: 1213889504 rtime: 1286 utime: 1173 stime: 113 cutime:1 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb7f4d730 (LWP 15810)] [New Thread 0xb4bf5b90 (LWP 16285)] [New Thread 0xb18fbb90 (LWP 16283)] [New Thread 0xb5671b90 (LWP 15877)] [New Thread 0xb40ffb90 (LWP 15875)] 0x00110416 in __kernel_vsyscall ()
+ Trace 200866
----------- .xsession-errors (4058 sec old) --------------------- (firefox:2594): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed /usr/lib/firefox-3.0b5/run-mozilla.sh: line 131: 2594 Terminated "$prog" ${1+"$@"} ** Message: <info> disconnected by the system bus. gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0.0'. ICE default IO error handler doing an exit(), pid = 7238, errno = 11 nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. pam-panel-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. gnome-terminal: Fatal IO error 104 (Connection reset by peer) on X server :0.0. The application 'nautilus' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. cannot open display: :0.0 Run 'gnome-panel --help' to see a full list of available command line options. --------------------------------------------------
No Evolution calls in the affected thread. Looks more like your X server crashed and that there's huge problems with your Fedora, also see the .xsession-errors output.
There are certainly a lot of bugs affecting this Fedora installation, but the .xsession-errors output that you referenced was an X crash that happened an hour before the evolution crash (https://bugzilla.redhat.com/show_bug.cgi?id=449460). That one happened right after a different evolution crash (evolution crashes for me a 20+ times per week). Whether there were evolution calls in the affected thread or not, evolution was running and then stopped running at the time that bug buddy prompted me to send a bug report, so evolution crashed and it was not a result of an X crash.
Nevertheless you are missing debug symbols for Evolution which makes submitting Evo crashers not that much helpful...
+ Trace 200877
Please install the corresponding debug packages (Evolution, Evolution-Data-Server, Gtkhtml) so we can track down and fix the issues you have.
argh... I installed the debug packages for evolution* last week. I guess when I yum updated and got new evolution packages it didn't update everything... here's what is already installed: atk-debuginfo-1.22.0-1.fc9.i386 already installed cairo-debuginfo-1.6.4-1.fc9.i386 already installed cyrus-sasl-debuginfo-2.1.22-13.fc9.i386 already installed db4-debuginfo-4.6.21-5.fc9.i386 already installed dbus-debuginfo-1.2.1-1.fc9.i386 already installed dbus-glib-debuginfo-0.74-8.fc9.i386 already installed e2fsprogs-debuginfo-1.40.8-3.fc9.i386 already installed evolution-debuginfo-2.22.2-2.fc9.i386 already installed gail-debuginfo-1.22.1-1.fc9.i386 already installed GConf2-debuginfo-2.22.0-1.fc9.i386 already installed glib2-debuginfo-2.16.3-5.fc9.i386 already installed glibc-debuginfo-2.8-3.i686 already installed gnome-keyring-debuginfo-2.22.1-1.fc9.i386 already installed gnome-vfs2-debuginfo-2.22.0-1.fc9.i386 already installed gstreamer-debuginfo-0.10.19-1.fc9.i386 already installed gtk2-debuginfo-2.12.10-2.fc9.i386 already installed gtkhtml3-debuginfo-3.18.2-1.fc9.i386 already installed krb5-debuginfo-1.6.3-10.fc9.i386 already installed libart_lgpl-debuginfo-2.3.20-1.fc9.i386 already installed libbonobo-debuginfo-2.22.0-2.fc9.i386 already installed libbonoboui-debuginfo-2.22.0-2.fc9.i386 already installed libglade2-debuginfo-2.6.2-5.fc9.i386 already installed libgnomecanvas-debuginfo-2.20.1.1-2.fc9.i386 already installed libgnome-debuginfo-2.22.0-3.fc9.i386 already installed libgnomeui-debuginfo-2.22.1-2.fc9.i386 already installed libICE-debuginfo-1.0.4-3.fc9.i386 already installed libnotify-debuginfo-0.4.4-10.fc9.i386 already installed libSM-debuginfo-1.0.2-5.fc9.i386 already installed libsoup-debuginfo-2.4.1-1.fc9.i386 already installed libX11-debuginfo-1.1.4-1.fc9.i386 already installed libxml2-debuginfo-2.6.32-2.fc9.i386 already installed nspr-debuginfo-4.7.1-0.9.1.fc9.i386 already installed nss-debuginfo-3.12.0.3-0.9.1.fc9.i386 already installed openssl-debuginfo-0.9.8g-9.fc9.i686 already installed ORBit2-debuginfo-2.14.12-3.fc9.i386 already installed pango-debuginfo-1.20.1-1.fc9.i386 already installed popt-debuginfo-1.13-3.fc9.i386 already installed zlib-debuginfo-1.2.3-18.fc9.i386 already installed Note that evolution & gtkhtml3 already have debuginfo. debuginfo-install evolution evolution-data-server gtkhtml[23] is only updating these... let me know if you'll need more: gtkhtml2-debuginfo NetworkManager-debuginfo evolution-data-server-debuginfo hal-debuginfo
Please install also evolution-exchange debug info package and in time of the crash (any you have during the work with evolution), please attach gdb to the "running" process of evolution-data-server and evolution-exchange, an attach here result of "thread apply all bt" command, so there will be sown what each of those processes does in time of the crash. As Andre said above, the initial stack trace above shows rather some dbus crash than evo crash.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!