Bug 598025 - [abrt] crash in evolution-2.30.1-6.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in evolution-2.30.1-6.fc13: raise: Process /usr/bin/evolution wa...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:91ed7b9411f0e0e75c566e8bdc1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-31 09:32 UTC by rokko1974
Modified: 2010-06-30 11:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-30 11:09:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.05 KB, text/plain)
2010-05-31 09:32 UTC, rokko1974
no flags Details

Description rokko1974 2010-05-31 09:32:49 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
comment: Evolution crash every time I open it, after a random time (2-20 minutes). This problem occurs since the upgrade from Fedora 12 to Fedora 13 using preupgrade.
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 91ed7b9411f0e0e75c566e8bdc17e956aacbf62a
kernel: 2.6.33.4-95.fc13.i686.PAE
package: evolution-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Open evolution
2.wait a few minutes (perhaps the error occurs when evolution automatically checks for incoming email, but I'm not really sure)
3.

Comment 1 rokko1974 2010-05-31 09:32:52 UTC
Created attachment 418225 [details]
File: backtrace

Comment 2 rokko1974 2010-06-03 07:13:07 UTC
2010-06-03

More debug informations:

I've done the following steps, but crash still present:

1) I've done the evolution configuration backup from the file menu
2) switched to runlevel 3
3) deleted the following paths: ~/.evolution ; ~/.gconf/apps/evolution ; ~/.gnome2_private/Evolution
4) switched again to runlevel 5
5) opened evolution and restored the evolution configuration backup above, then closed it
6) deleted .#evolution.sbd, Drafts*, Inbox*, Outbox*, Sent*, MY_MAIL_ARCHIVES* from ~/.evolution/mail/local
7) re-imported Inbox, Outbox, MY_MAIL_ARCHIVES

Launching Evolution from shell:

$ evolution
(evolution:10917): e-data-server-DEBUG: Loading categories from "/home/myuser/.evolution/categories.xml"
(evolution:10917): e-data-server-DEBUG: Loaded 35 categories

** (evolution:10917): CRITICAL **: categories_icon_theme_hack: assertion `filename != NULL && *filename != '\0'' failed
** (evolution:10917): DEBUG: Loading Exchange MAPI Plugin 

** (evolution:10917): DEBUG: MAPI listener is constructed with 0 listed MAPI accounts 

** (evolution:10917): CRITICAL **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached

** (evolution:10917): CRITICAL **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached

***MEMORY-ERROR***: evolution[10917]: GSlice: assertion failed: sinfo->n_allocated > 0
Abortito (core dumped)


$ rpm -q gtkhtml3 glib2
gtkhtml3-3.30.1-1.fc13.i686
glib2-2.24.1-1.fc13.i686

Comment 3 aibias 2010-06-07 17:09:44 UTC
Package: evolution-2.30.1-6.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


Comment
-----
I was doing nothing with evolution but it crashed. Evolution is crasching often after the upgrade to Fedora 13 from Fedora 12 with preupgrade program. The crash appear in the same way, without (seems) any reason.
(Probably  automatic check for new mail every 10 minutes?).

Comment 4 rokko1974 2010-06-08 06:10:44 UTC
update to evolution-2.30.1-8.fc13.i686: problem still present

Comment 5 rokko1974 2010-06-30 11:08:53 UTC
Problem seems solved upgrading to evolution-2.30.2-1.fc13.i686
No more crashes for about 17 hours at the moment (before this upgrade there were 5-6 core dumps every hour!)


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