Bug 1583527

Summary: [abrt] evolution-data-server: closure_invoke_notifiers(): evolution-calendar-factory-subprocess killed by SIGABRT
Product: [Fedora] Fedora Reporter: Milan Bouchet-Valat <nalimilan>
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: alexl, caillon+fedoraproject, john.j5live, mcrha, rhughes, rstrode, sandmann, wallner
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7acbf1dedfe3587d7c685992bbb0ce3194b412cc
Whiteboard: abrt_hash:fb8a83593d94863c2b8daa471d53787818901a15;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 20:41:05 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: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Milan Bouchet-Valat 2018-05-29 07:47:55 UTC 
Version-Release number of selected component:
evolution-data-server-3.28.1-2.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory-subprocess --factory all --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx8178x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/8178/2
crash_function: closure_invoke_notifiers
executable:     /usr/libexec/evolution-calendar-factory-subprocess
journald_cursor: s=6ff8a1dedda74475be84a7dc8c68c8e1;i=69fde;b=e6f9f47f1cb8409fba3c43fc07a29f9a;m=5ca16d9774;t=56d533d3cf80e;x=65cc87eea9808c67
kernel:         4.16.7-300.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Potential duplicate: bug 1376583
Comment 2 Milan Bouchet-Valat 2018-05-29 07:48:02 UTC 
Created attachment 1445198 [details]
File: cgroup
Comment 3 Milan Bouchet-Valat 2018-05-29 07:48:04 UTC 
Created attachment 1445199 [details]
File: core_backtrace
Comment 4 Milan Bouchet-Valat 2018-05-29 07:48:06 UTC 
Created attachment 1445200 [details]
File: cpuinfo
Comment 5 Milan Bouchet-Valat 2018-05-29 07:48:08 UTC 
Created attachment 1445201 [details]
File: dso_list
Comment 6 Milan Bouchet-Valat 2018-05-29 07:48:09 UTC 
Created attachment 1445202 [details]
File: environ
Comment 7 Milan Bouchet-Valat 2018-05-29 07:48:10 UTC 
Created attachment 1445203 [details]
File: limits
Comment 8 Milan Bouchet-Valat 2018-05-29 07:48:13 UTC 
Created attachment 1445204 [details]
File: maps
Comment 9 Milan Bouchet-Valat 2018-05-29 07:48:14 UTC 
Created attachment 1445205 [details]
File: mountinfo
Comment 10 Milan Bouchet-Valat 2018-05-29 07:48:15 UTC 
Created attachment 1445206 [details]
File: open_fds
Comment 11 Milan Bouchet-Valat 2018-05-29 07:48:17 UTC 
Created attachment 1445207 [details]
File: proc_pid_status
Comment 12 Milan Crha 2018-05-29 08:44:41 UTC 
Thanks for a bug report. It looks like the crash happened shortly after the calendars had been opened, which can be either after start of evolution-alarm-notify or other process using those calendars. I see there are two On The Web calendars involved and several CalDAV calendars. I do not know what exactly caused the crash, though. As libsoup is involved, then maybe the things found within [1] can be related, but it's a wild guess.

Do you have configured On The Web and CalDAV calendars only/mainly (there's always at least one On This Computer calendar)? I think of adding them to my Evolution for testing purposes, though I'm not sure whether it'll help.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=781771
Comment 13 Florian Wallner 2018-06-17 13:36:45 UTC 
*** Bug 1592121 has been marked as a duplicate of this bug. ***
Comment 14 Ben Cotton 2019-05-02 21:34:15 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 15 Ben Cotton 2019-05-28 20:41:05 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.