Bug 699959 - [abrt] evolution-data-server-2.32.0-1.fc14: g_logv: Process /usr/libexec/e-calendar-factory was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-data-server-2.32.0-1.fc14: g_logv: Process /usr/libexec/e-ca...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:65b913b0145788b677b8c82bc65...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-27 04:23 UTC by Fabian D
Modified: 2011-04-27 05:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-27 05:59:14 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (27.18 KB, text/plain)
2011-04-27 04:23 UTC, Fabian D 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 638092 0 None None None Never

Description Fabian D 2011-04-27 04:23:47 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/e-calendar-factory
component: evolution-data-server
crash_function: g_logv
executable: /usr/libexec/e-calendar-factory
kernel: 2.6.35.6-45.fc14.x86_64
package: evolution-data-server-2.32.0-1.fc14
rating: 3
reason: Process /usr/libexec/e-calendar-factory was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1303068219
uid: 500
Comment 1 Fabian D 2011-04-27 04:23:51 UTC 
Created attachment 495106 [details]
File: backtrace
Comment 2 Milan Crha 2011-04-27 05:59:14 UTC 
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=638092
Note You need to log in before you can comment on or make changes to this bug.