evolution crashed with signal 5 in main()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| evolution (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Hi!
It seems strange, I thought I’ve already repported this bug, but Launchpad didn’t propose it.
Maybe it has been linked to a private one. If it is the case, please remove this repport.
The bug appears precisely at the moment I tried to display an already sent mail.
I already have this bug before, and it appears to always appear on a sent mail with an attachment from a Google adress (maybe I’ve misset it?).
Hoping apport collected enough informations.
Martin.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evolution 3.2.2-0ubuntu0.1
ProcVersionSign
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CheckboxSubmission: 01a18e0a74cbde3
CheckboxSystem: f134069bba09873
CrashCounter: 1
Date: Thu Jan 26 16:47:52 2012
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: evolution --component=mail
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.utf8
SHELL=/bin/bash
Signal: 5
SourcePackage: evolution
StacktraceTop: main ()
Title: evolution crashed with signal 5 in main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video
| Martin Constantino–Bodin (martin-bodin) wrote | #1 |
| visibility: | private → public |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #857043, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.