Bug 1235935

Summary: [abrt] evolution: g_main_context_acquire(): evolution killed by SIGABRT
Product: [Fedora] Fedora Reporter: Johan De Wit <johan>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: lucilanga, mbarnes, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4225002d8c3e1c0a75e53662bbebd3acb53dd4a9
Whiteboard: abrt_hash:6ac82213856c3a3969b24bf50ac6b0f627cad3d7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 08:33:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Johan De Wit 2015-06-26 06:43:10 UTC
Description of problem:
 Evolution just crashed on me.

This was the first time it happened.

This is the automated bug reporting in action.


Version-Release number of selected component:
evolution-3.16.3-2.fc22

Additional info:
reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        evolution
crash_function: g_main_context_acquire
executable:     /usr/bin/evolution
global_pid:     2434
kernel:         4.0.4-303.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #4 g_main_context_acquire at gmain.c:3187
 #7 gtk_main at gtkmain.c:1219

Comment 1 Johan De Wit 2015-06-26 06:43:13 UTC
Created attachment 1043414 [details]
File: backtrace

Comment 2 Johan De Wit 2015-06-26 06:43:14 UTC
Created attachment 1043415 [details]
File: cgroup

Comment 3 Johan De Wit 2015-06-26 06:43:16 UTC
Created attachment 1043416 [details]
File: core_backtrace

Comment 4 Johan De Wit 2015-06-26 06:43:19 UTC
Created attachment 1043417 [details]
File: dso_list

Comment 5 Johan De Wit 2015-06-26 06:43:20 UTC
Created attachment 1043418 [details]
File: environ

Comment 6 Johan De Wit 2015-06-26 06:43:21 UTC
Created attachment 1043419 [details]
File: limits

Comment 7 Johan De Wit 2015-06-26 06:43:23 UTC
Created attachment 1043420 [details]
File: maps

Comment 8 Johan De Wit 2015-06-26 06:43:24 UTC
Created attachment 1043421 [details]
File: mountinfo

Comment 9 Johan De Wit 2015-06-26 06:43:26 UTC
Created attachment 1043422 [details]
File: namespaces

Comment 10 Johan De Wit 2015-06-26 06:43:28 UTC
Created attachment 1043423 [details]
File: open_fds

Comment 11 Johan De Wit 2015-06-26 06:43:29 UTC
Created attachment 1043424 [details]
File: proc_pid_status

Comment 12 Johan De Wit 2015-06-26 06:43:30 UTC
Created attachment 1043425 [details]
File: var_log_messages

Comment 13 Milan Crha 2015-06-26 10:12:45 UTC
Thanks for a bug report. This crashed due to this assertion error:
> assertion failed: (context->owner_count == 0
and looking into the var_log_messages there were more issues printed on the console before the actual crash.

I do not see any such crash myself, thus I'm rather asking, doe sit crash for you each start of the evolution, or after some time? Is there any pattern of the actions you do that would lead to the crash, like some steps for a reproducer, please?

The backtrace also shows that you were creating an appointment from a mail message. Whether it's related or not is hard to tell. If I guess properly, then you tried to create the appointment in a Google calendar.

Comment 14 Johan De Wit 2015-06-26 11:52:16 UTC
I dont know what i was doing when evolution crashed.  

It does crash sometimes, but mostly when it is running for some time.  Not at startup.  

I will update this ticket whenever this happens again, and pay more attention what i did before the crash

Comment 15 Johan De Wit 2015-06-27 11:24:18 UTC
Evolution crashed again.

I was marking mails using the 'mark mail a junk' button

Comment 16 Milan Crha 2015-06-29 05:53:53 UTC
*** Bug 1236293 has been marked as a duplicate of this bug. ***

Comment 17 Milan Crha 2015-06-29 08:33:40 UTC
The above bug #1236293 provides a different backtrace, but at least claims a memory corruption, leading to a better place. That's filled upstream in GLib as this [1] bug report. I'm closing this in favour of [1]. Please see it for any further updates.

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