Bug 678041 - [abrt] evolution-2.32.1-1.fc14: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.1-1.fc14: Process /usr/libexec/evolution/2.32/evolution...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
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:19773114e5df80724d48bb870df...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 15:40 UTC by Miloslav Trmač
Modified: 2011-02-17 07:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-17 07:50:53 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (28.71 KB, text/plain)
2011-02-16 15:40 UTC, Miloslav Trmač 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Miloslav Trmač 2011-02-16 15:40:36 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/evolution/2.32/evolution-alarm-notify
component: evolution
executable: /usr/libexec/evolution/2.32/evolution-alarm-notify
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.1-1.fc14
reason: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Just logged in...
time: 1297870465
uid: 500
Comment 1 Miloslav Trmač 2011-02-16 15:40:40 UTC 
Created attachment 479133 [details]
File: backtrace
Comment 2 Milan Crha 2011-02-17 07:50:53 UTC 
Thanks for a bug report, though the backtrace doesn't contain enough information to be tracked properly. Please install debug info packages for evolution and evolution-data-server, and if you have, then please make sure they are of the same version as their master packages. And even if you have that too, then please ask ABRT folks what might go wrong here. Thanks.

Thread 1 (Thread 0x7ff7d7286980 (LWP 2152)):
#0  0x0000000000408ebe in ?? ()
No symbol table info available.
#1  0x0000000000409f1a in ?? ()
No symbol table info available.
#2  0x0000000000409c01 in ?? ()
No symbol table info available.
#3  0x0000000000407cfd in ?? ()
No symbol table info available.
Note You need to log in before you can comment on or make changes to this bug.