Bug 1321624

Summary: [abrt] evolution: g_mutex_clear(): evolution-alarm-notify killed by SIGABRT
Product: [Fedora] Fedora Reporter: hx
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: hx, lucilanga, mbarnes, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/72d5477dca595de642ce5f515e017f5edcb5af06
Whiteboard: abrt_hash:adabf2ad82e493288c9203f434513679ffc87466;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-25 06:30:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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 hx 2016-03-28 16:31:24 UTC 
Version-Release number of selected component:
evolution-3.18.5.2-1.fc23

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/evolution-alarm-notify
crash_function: g_mutex_clear
executable:     /usr/libexec/evolution/evolution-alarm-notify
global_pid:     2346
kernel:         4.4.6-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #2 g_mutex_clear at gthread-posix.c:1302
 #3 e_flag_free at e-flag.c:232
 #4 e_client_wait_for_connected_sync at e-client.c:2018
 #5 client_wait_for_connected_thread at e-client.c:1863
 #6 g_task_thread_pool_thread at gtask.c:1287
 #8 g_thread_proxy at gthread.c:778

Potential duplicate: bug 1234988
Comment 1 hx 2016-03-28 16:31:30 UTC 
Created attachment 1140910 [details]
File: backtrace
Comment 2 hx 2016-03-28 16:31:32 UTC 
Created attachment 1140911 [details]
File: cgroup
Comment 3 hx 2016-03-28 16:31:33 UTC 
Created attachment 1140912 [details]
File: core_backtrace
Comment 4 hx 2016-03-28 16:31:35 UTC 
Created attachment 1140913 [details]
File: dso_list
Comment 5 hx 2016-03-28 16:31:36 UTC 
Created attachment 1140914 [details]
File: environ
Comment 6 hx 2016-03-28 16:31:37 UTC 
Created attachment 1140915 [details]
File: limits
Comment 7 hx 2016-03-28 16:31:39 UTC 
Created attachment 1140916 [details]
File: maps
Comment 8 hx 2016-03-28 16:31:41 UTC 
Created attachment 1140917 [details]
File: mountinfo
Comment 9 hx 2016-03-28 16:31:42 UTC 
Created attachment 1140918 [details]
File: namespaces
Comment 10 hx 2016-03-28 16:31:45 UTC 
Created attachment 1140919 [details]
File: open_fds
Comment 11 hx 2016-03-28 16:31:46 UTC 
Created attachment 1140920 [details]
File: proc_pid_status
Comment 12 hx 2016-03-28 16:31:48 UTC 
Created attachment 1140921 [details]
File: var_log_messages
Comment 13 Milan Crha 2016-03-30 12:59:28 UTC 
Thanks for a bug report. I saw the crash several times, but I was never able to reliably reproduce it myself. By any chance, are you able to reproduce the crash?
Comment 14 hx 2016-10-22 10:23:08 UTC 
Sorry, I think I can not reproduce since recent update to Fedora 25
Comment 15 Milan Crha 2016-10-25 06:30:35 UTC 
Thanks for the update. That's okay, the crash doesn't happen consistently, as far as I can tell. I'll mark this as a duplicate of an older bug, which points to an upstream bug (through another duplicate).

*** This bug has been marked as a duplicate of bug 1234988 ***