evolution crashed with SIGSEGV in camel_exchange_folder_construct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution-exchange |
Fix Released
|
Critical
|
|||
evolution-exchange (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: evolution
After some Ubuntu updates (evolution 2.26.1-0ubuntu2), evolution started
crashing on startup. Downgrading the package didn't help, so maybe upgrade was
just a coincidence, so I am posting this here.
I can even reproduce the bug in evolution's offline mode: all I have to do is
navigate to my Inbox folder, so this time it is not related to communication
with the server, but probably with reading of some cached data from the disk.
The console is not very informative:
$ evolution --offline
** (evolution:5483): DEBUG: mailto URL command: evolution %s
** (evolution:5483): DEBUG: mailto URL program: evolution
** (evolution:5483): DEBUG: EI: SHELL STARTUP
Segmentation fault (core dumped)
I have also reported the bug upstream: http://
ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/evolution
Package: evolution 2.26.1-0ubuntu2
ProcCmdline: /usr/bin/evolution --component=mail
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
camel_
exchange_
camel_
mail_tool_
get_folder_exec (m=0x9b120f0) at mail-ops.c:1214
Title: evolution crashed with SIGSEGV in camel_exchange_
Uname: Linux 2.6.28-12-generic i686
UserGroups: adm admin audio cdrom dhcp dialout dip disk floppy fuse lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt sambashare scanner scard vboxusers video
Changed in evolution-exchange: | |
status: | Unknown → New |
Changed in evolution-exchange: | |
status: | New → Invalid |
Changed in evolution-exchange: | |
status: | Unknown → In Progress |
Changed in evolution-exchange: | |
importance: | Unknown → Critical |
Changed in evolution-exchange: | |
status: | In Progress → Fix Released |
Thanks for the report. but tehre's no need to report the bug twice upstream and on launchpad.