Bug 675772 - [abrt] evolution-data-server-2.32.1-1.fc14: ber_free_buf: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-data-server-2.32.1-1.fc14: ber_free_buf: Process /usr/libexe...
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:e63fcb56e97b5ec47828c9a7cc8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-07 17:22 UTC by Brian Millett
Modified: 2011-02-08 11:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-08 11:08:07 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (13.54 KB, text/plain)
2011-02-07 17:22 UTC, Brian Millett
no flags Details


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

Description Brian Millett 2011-02-07 17:22:44 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
crash_function: ber_free_buf
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.38-0.rc3.git0.1.fc15.x86_64
package: evolution-data-server-2.32.1-1.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297096884
uid: 500

How to reproduce
-----
1.
2.don't know
3.

Comment 1 Brian Millett 2011-02-07 17:22:46 UTC
Created attachment 477462 [details]
File: backtrace

Comment 2 Milan Crha 2011-02-08 11:08:07 UTC
Thanks for a bug report. I moved this upstream as [1]. 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=641825


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