Bug 714967 - [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by sign...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:071410918e225236c8c4d9ad7a0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-21 13:05 UTC by Pedro Silva
Modified: 2011-06-22 06:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-22 06:15:38 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (50.42 KB, text/plain)
2011-06-21 13:05 UTC, Pedro Silva 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


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

Description Pedro Silva 2011-06-21 13:05:56 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 51628 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 124395520 bytes
crash_function: _g_dbus_connection_get_fd_sync
executable: /usr/bin/evolution
kernel: 2.6.35.13-92.fc14.i686.PAE
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1308661355
uid: 500

How to reproduce
-----
1. Click New Message
2. Evolution hangs for about 1 or 2 minutes.
3. New Message window appears
4. Write message and click Send
5. Boom, crash!
Comment 1 Pedro Silva 2011-06-21 13:05:59 UTC 
Created attachment 505824 [details]
File: backtrace
Comment 2 Milan Crha 2011-06-22 06:15:38 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=574444
Note You need to log in before you can comment on or make changes to this bug.