Red Hat Bugzilla – Bug 1254771
[abrt] evolution-data-server: mem_error(): evolution-calendar-factory-subprocess killed by SIGABRT
Last modified: 2016-07-19 13:33:54 EDT
Version-Release number of selected component:
cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2473x5 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2473/5
runlevel: N 5
Thread no. 1 (4 frames)
#2 mem_error at gslice.c:1439
#3 slab_allocator_free_chunk at gslice.c:1321
#4 private_thread_memory_cleanup at gslice.c:785
#5 __nptl_deallocate_tsd at pthread_create.c:175
Created attachment 1064448 [details]
Created attachment 1064449 [details]
Created attachment 1064450 [details]
Created attachment 1064451 [details]
Created attachment 1064452 [details]
Created attachment 1064453 [details]
Created attachment 1064454 [details]
Created attachment 1064455 [details]
Created attachment 1064456 [details]
Created attachment 1064457 [details]
Created attachment 1064458 [details]
Created attachment 1064459 [details]
Thanks for a bug report. It looks like a memory corruption related to your evolution-ews calendar(s). I do not see from the backtrace what could cause it, neither what you were doing before the crash (it could be also an automatic update of the calendar).
By any chance, do you know what you were doing with the calendar before the crash, if anything directly? Is this anyhow reproducible, please?
All I know is that I might have lost connection to the network while moving the laptop.
Also, I had some problems configuring the corporate proxy. I don't know if it was at the same moment evolution crashed, but maybe it's related. It's an authenticated proxy.
I configure the proxy through Gnome, and let evolution use system settings.
Thanks for the update. Most of it sounds like a one-time change. And apart of the second bug report I'm afraid we cannot do much with it, especially if it was just a one-time crash, unreproducible.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.