GNOME Bugzilla – Bug 430500
Evolution crash while using another program
Last modified: 2007-05-15 15:42:59 UTC
Distribution: Debian lenny/sid Package: Evolution Severity: critical Version: GNOME2.18.0 2.6.x Gnome-Distributor: Debian Synopsis: Evolution crash while using another program Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.18.1) Description: Description of the crash: Evolution was running and giving error message: error fetching mail. I closed all error dialogs and started a new send/recieve job. Waiting for this I meanwhile started Stellarium and while using it Stellarium crashed together with Evolution. Steps to reproduce the crash: 1. 2. 3. Expected Results: Normal program operation How often does this happen? First time for me Additional Information: Installed programs: > evolution - groupware suite with mail client and organizer > evolution-common - architecture independent files for Evolution > evolution-data-server - evolution database backend server > evolution-data-server-common - architecture independent files for Evolution Data Server > evolution-data-server-dbg - evolution database backend server with debugging symbols > evolution-data-server-dev - Development files for evolution-data-server (meta package) > evolution-dbg - debugging symbols for Evolution > evolution-dev - development library files for Evolution > evolution-exchange - Exchange plugin for the Evolution groupware suite > evolution-jescs - Evolution Connector for Sun Java Enterprise System Calendar Server (SJESCS) > evolution-plugins - standard plugins for Evolution > evolution-plugins-experimental - experimental plugins for Evolution > evolution-webcal - webcal: URL handler for GNOME and Evolution Debugging Information: Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232652608 (LWP 7794)] [New Thread -1292043376 (LWP 16126)] [New Thread -1283654768 (LWP 16125)] [New Thread -1266738288 (LWP 16124)] [New Thread -1275130992 (LWP 7858)] [New Thread -1255597168 (LWP 7854)] [New Thread -1265034352 (LWP 7818)] [New Thread -1247171696 (LWP 7816)] [New Thread -1238783088 (LWP 7813)] 0xb6c39b99 in poll () from /lib/libc.so.6
+ Trace 128386
------- Bug created by bug-buddy at 2007-04-17 00:58 ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and 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! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Hi Akhil, I had installed the depandancies: -evolution-data-server-dbg - evolution database backend server with debugging symbols -evolution-data-server-dev - Development files for evolution-data-server (meta package) -evolution-dbg - debugging symbols for Evolution -evolution-dev - development library files for Evolution -dev pkgs for libc, libglib, liborbit. NOT installed: -libx11 -libgtk -libthread I have been strugling to get good stacktraces, in evolutions case I performed # apt-get build-dep evolution, but this was obviously not enough. I have read all the different pages on getting good bug reports and followed the instructions to my best ability. Could you please tell me if it's the three missing dep's that makes this particular bug trace useless? Thanks ar
Debug info packages of evolution,evolution-data-server are fine :-) Try this to get good stack traces ! If you can reproduce it while running Evolution under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this), that might help getting a better trace if you've already got debug packages installed.
*** This bug has been marked as a duplicate of 352284 ***