Bug 844829 - [abrt] evolution-2.32.3-1.fc14: camel_msgport_try_pop: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.3-1.fc14: camel_msgport_try_pop: Process /usr/bin/evolu...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6529d1719482d63f338d55b54f7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-01 00:33 UTC by Larry O'Leary
Modified: 2012-08-01 03:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-01 03:16:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (59.11 KB, text/plain)
2012-08-01 00:33 UTC, Larry O'Leary 		no flags Details
View All

Description Larry O'Leary 2012-08-01 00:33:07 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 60524 bytes
cmdline: evolution
comment: Evolution had been working fine for a very long time. Recently, it began to hang at startup. I deleted all remanence of Evolution and attempted to re-install but this issue still occurs. The only way I can get Evolution to start is to use --offline mode. Then, go to online mode once it is started.
component: evolution
Attached file: coredump, 158674944 bytes
crash_function: camel_msgport_try_pop
executable: /usr/bin/evolution
kernel: 2.6.35.14-106.fc14.x86_64
package: evolution-2.32.3-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1343780231
uid: 500

How to reproduce
-----
1. Start Evolution
Comment 1 Larry O'Leary 2012-08-01 00:33:09 UTC 
Created attachment 601618 [details]
File: backtrace
Comment 2 Larry O'Leary 2012-08-01 03:16:22 UTC 
Closing this as I logged it against Fedora 14.
Note You need to log in before you can comment on or make changes to this bug.