Version-Release number of selected component: evolution-data-server-3.28.2-2.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory-subprocess --factory all --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx3590x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/3590/2 crash_function: mem_error executable: /usr/libexec/evolution-addressbook-factory-subprocess journald_cursor: s=94678e37991f445287d2f28566af0e99;i=2ea15;b=94a9c937be1e4f88944bf0c0b96514cc;m=9ea76e86;t=56cff50724ebc;x=ad39b77c81b292c3 kernel: 4.16.9-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1254771
Created attachment 1441381 [details] File: backtrace
Created attachment 1441382 [details] File: cgroup
Created attachment 1441383 [details] File: core_backtrace
Created attachment 1441384 [details] File: cpuinfo
Created attachment 1441385 [details] File: dso_list
Created attachment 1441386 [details] File: environ
Created attachment 1441387 [details] File: limits
Created attachment 1441388 [details] File: maps
Created attachment 1441389 [details] File: mountinfo
Created attachment 1441390 [details] File: open_fds
Created attachment 1441391 [details] File: proc_pid_status
Thanks for a bug report. I see the crash happened with your evolution-ews account, with its address books. It's not obvious what exactly caused it. I'd guess some memory issue in the code, like when writing to an already freed memory, effectively overwriting a chunk which is occupied by something else, but it's only a guess. The backtrace shows that one of your addressbooks had been updating when the crash happened, which may or may not be related. By any chance, are you able to reproduce the crash, please? The easiest for the test would be to: a) close evolution b) kill evolution-addressbook-factory c) remove ~/.cache/evolution/addressbook (this will cause re-download of all your remote address books, including the Global Address List from the Exchange server) d) run addressbook factory from a terminal: $ /usr/libexec/evolution-addressbook-factory -w e) start evolution and go to the Contacts view (evolution -c contacts) f) select each of the Exchange address books, thus they are opened and refreshed g) check any errors on the address book factory terminal
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.
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.