Bug 844829 - [abrt] evolution-2.32.3-1.fc14: camel_msgport_try_pop: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] evolution-2.32.3-1.fc14: camel_msgport_try_pop: Process /usr/bin/evolu...
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
14
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
abrt_hash:6529d1719482d63f338d55b54f7...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-31 20:33 EDT by Larry O'Leary
Modified: 2012-07-31 23:16 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-07-31 23:16:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (59.11 KB, text/plain)
2012-07-31 20:33 EDT, Larry O'Leary
no flags Details

  None (edit)
Description Larry O'Leary 2012-07-31 20:33:07 EDT
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-07-31 20:33:09 EDT
Created attachment 601618 [details]
File: backtrace
Comment 2 Larry O'Leary 2012-07-31 23:16:22 EDT
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.