Bug 705578 - [abrt] evolution-2.32.2-1.fc14: XInternAtom: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
[abrt] evolution-2.32.2-1.fc14: XInternAtom: Process /usr/libexec/evolution/2...
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
14
i686 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
abrt_hash:face23a00212baee31ef990e4fc...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-05-17 17:34 EDT by David
Modified: 2011-05-18 01:54 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-05-18 01:54:55 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 (25.98 KB, text/plain)
2011-05-17 17:34 EDT, David
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 625179 None None None Never

  None (edit)
Description David 2011-05-17 17:34:41 EDT
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 26606 bytes
cmdline: /usr/libexec/evolution/2.32/evolution-alarm-notify
component: evolution
Attached file: coredump, 2449408 bytes
crash_function: XInternAtom
executable: /usr/libexec/evolution/2.32/evolution-alarm-notify
kernel: 2.6.35.13-91.fc14.i686
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1305486906
uid: 500

How to reproduce
-----
1.
2.
3.
This came up after sending a email.
Comment 1 David 2011-05-17 17:34:44 EDT
Created attachment 499476 [details]
File: backtrace
Comment 2 Milan Crha 2011-05-18 01:54:55 EDT
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=625179

Note You need to log in before you can comment on or make changes to this bug.