Bug 680698 - [abrt] evolution-2.91.90-1.fc15: g_list_length: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.91.90-1.fc15: g_list_length: Process /usr/bin/evolution wa...
Keywords:
Status: CLOSED DUPLICATE of bug 676497
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b2b09659f86c33b19e319b60d9e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-27 05:22 UTC by Mike Chambers
Modified: 2011-02-28 08:12 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (38.65 KB, text/plain)
2011-02-27 05:22 UTC, Mike Chambers 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mike Chambers 2011-02-27 05:22:33 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 39574 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 83951616 bytes
crash_function: g_list_length
executable: /usr/bin/evolution
kernel: 2.6.38-0.rc5.git1.1.fc15.x86_64
package: evolution-2.91.90-1.fc15
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1298783255
uid: 500

How to reproduce
-----
1.Click on Activities
2.Click on Evolution for first time
3.Menu comes up to welcome you to evolution
4.
Comment 1 Mike Chambers 2011-02-27 05:22:35 UTC 
Created attachment 481213 [details]
File: backtrace
Comment 2 Mike Chambers 2011-02-27 14:21:53 UTC 
Seems to work with latest gnome/whatever updates.
Comment 3 Milan Crha 2011-02-28 08:12:02 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

*** This bug has been marked as a duplicate of bug 676497 ***
Note You need to log in before you can comment on or make changes to this bug.