Bug 1376561

Summary: [abrt] evolution-data-server: magazine_chain_pop_head(): evolution-calendar-factory-subprocess killed by SIGSEGV
Product: [Fedora] Fedora Reporter: pzeppegno
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: 24CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e487bf0c480d924b7fb870c30b3e00b95b168f17
Whiteboard: abrt_hash:69eedbd93ec25ef0dbb8ea72e735a35da9f55234;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 17:22:44 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: exploitable
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 pzeppegno 2016-09-15 17:40:42 UTC 
Version-Release number of selected component:
evolution-data-server-3.20.5-2.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx4187x4 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/4187/4
crash_function: magazine_chain_pop_head
executable:     /usr/libexec/evolution-calendar-factory-subprocess
global_pid:     4240
kernel:         4.7.2-200.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 magazine_chain_pop_head at gslice.c:544
 #1 magazine_chain_prepare_fields at gslice.c:619
 #2 magazine_cache_push_magazine at gslice.c:691
 #3 private_thread_memory_cleanup at gslice.c:777
 #4 __nptl_deallocate_tsd at pthread_create.c:175

Potential duplicate: bug 843528
Comment 1 pzeppegno 2016-09-15 17:40:47 UTC 
Created attachment 1201327 [details]
File: backtrace
Comment 2 pzeppegno 2016-09-15 17:40:48 UTC 
Created attachment 1201328 [details]
File: cgroup
Comment 3 pzeppegno 2016-09-15 17:40:49 UTC 
Created attachment 1201329 [details]
File: core_backtrace
Comment 4 pzeppegno 2016-09-15 17:40:52 UTC 
Created attachment 1201330 [details]
File: dso_list
Comment 5 pzeppegno 2016-09-15 17:40:53 UTC 
Created attachment 1201331 [details]
File: environ
Comment 6 pzeppegno 2016-09-15 17:40:55 UTC 
Created attachment 1201332 [details]
File: exploitable
Comment 7 pzeppegno 2016-09-15 17:40:56 UTC 
Created attachment 1201333 [details]
File: limits
Comment 8 pzeppegno 2016-09-15 17:40:58 UTC 
Created attachment 1201334 [details]
File: maps
Comment 9 pzeppegno 2016-09-15 17:40:59 UTC 
Created attachment 1201335 [details]
File: mountinfo
Comment 10 pzeppegno 2016-09-15 17:41:00 UTC 
Created attachment 1201336 [details]
File: namespaces
Comment 11 pzeppegno 2016-09-15 17:41:02 UTC 
Created attachment 1201337 [details]
File: open_fds
Comment 12 pzeppegno 2016-09-15 17:41:03 UTC 
Created attachment 1201338 [details]
File: proc_pid_status
Comment 13 pzeppegno 2016-09-15 17:41:04 UTC 
Created attachment 1201339 [details]
File: var_log_messages
Comment 14 Milan Crha 2016-09-19 12:01:11 UTC 
Thanks for a bug report. I see from the backtrace that the crash happened due to an EWS calendar. It doesn't show what exactly broke, the crashing thread usually points to a memory corruption, often caused by some core writing to an uninitialized or already freed memory.

I know these issues are pretty hard to reproduce, but just in case, are you able to reproduce this, please? If you do, then we can try to investigate further. Thanks in advance.
Comment 15 Fedora End Of Life 2017-07-25 23:03:21 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 16 Fedora End Of Life 2017-08-08 17:22:44 UTC 
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.