Bug 652917 - [abrt] evolution-2.32.0-2.fc14: g_object_unref: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.0-2.fc14: g_object_unref: Process /usr/bin/evolution wa...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a58a22aa8e9daa9a20659fe39f6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-13 14:06 UTC by Alex
Modified: 2010-11-15 09:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-15 09:00:42 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (59.67 KB, text/plain)
2010-11-13 14:06 UTC, Alex
no flags Details


Links
System ID Priority Status Summary Last Updated
GNOME Bugzilla 634890 None None None Never

Description Alex 2010-11-13 14:06:17 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: g_object_unref
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.x86_64
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289655954
uid: 500

How to reproduce
-----
1.
2.
3.
Evolution was crashed when few entryies were moved from one address book to another one by means of mouse drag and drop.
Actually, all the entries appear moved BUT one entry even being copied left in the original location. This particular entry was neither first nor last in the display order

Comment 1 Alex 2010-11-13 14:06:20 UTC
Created attachment 460233 [details]
File: backtrace

Comment 2 Milan Crha 2010-11-15 09:00:42 UTC
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates.

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


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