evolution crashes shortly after opening when evolution-indicator is installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution-indicator (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Immediately after upgrading to raring, Evolution crashes soon after loading. I'm not sure what the specific trigger is; sometimes it crashes within under a second even with no action from me, sometimes it lasts up to a minute or so. It tends to crash reliably when I attempt to view any message (via the message preview, or via double-clicking on it with the message preview turned off), though it sometimes also seems to crash due to other triggers; I sometimes see the content of the message for a tiny fraction of a second before the crash. It has managed to receive new emails in the short length of time while it's been open (although I haven't been able to observe what those emails are). The visible symptom is that Evolution simply closes (or, on one occasion, was greyed out by Compiz due to being a stuck process, and had to be force-quit).
apport has since stopped bothering to collect crash dumps, but I've attached one of the crash dumps it did collect to this bug report. Hopefully that will provide more information as to the nature of the problem (and what specific sort of crash is involved).
Expected behaviour is for Evolution to show me the content of the message without crashing.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: evolution 3.6.4-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-27-generic i686
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
Date: Sun Jul 21 03:52:55 2013
InstallationDate: Installed on 2009-12-14 (1314 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MarkForUpload: True
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to raring on 2013-07-21 (0 days ago)
Followup: I tried running Evolution in a terminal, and opening a message via double-click to reproduce the crash. I've attached the output that it spewed to the terminal.