Version-Release number of selected component: evolution-data-server-3.36.0-1.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/evolution-addressbook-factory.service cmdline: /usr/libexec/evolution-addressbook-factory crash_function: soup_cookie_free executable: /usr/libexec/evolution-addressbook-factory journald_cursor: s=a91e44343d0847a2b39199436275739c;i=23f7;b=d11980eaa3164fcaa98b889b5003479e;m=28c9769a9;t=5a207c35eed48;x=cdf7df6853589e2f kernel: 5.6.0-0.rc7.git0.2.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 xsession_errors:
Created attachment 1674850 [details] File: backtrace
Created attachment 1674851 [details] File: core_backtrace
Created attachment 1674852 [details] File: cpuinfo
Created attachment 1674853 [details] File: dso_list
Created attachment 1674854 [details] File: environ
Created attachment 1674855 [details] File: limits
Created attachment 1674856 [details] File: maps
Created attachment 1674857 [details] File: mountinfo
Created attachment 1674858 [details] File: open_fds
Created attachment 1674859 [details] File: proc_pid_status
Thanks for a bug report. While there are filled similar bug reports against evolution-data-server I believe this one belongs to libsoup, because the evolution-ews code (which is related and shown in the backtrace a lot) doesn't access soup_cookie directly at all, thus I move this bug to libsoup for further investigation.
*** Bug 1821514 has been marked as a duplicate of this bug. ***
*** Bug 1823869 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This might be related to the fact that I was disabling one of the displays through GNOME settings. I thinks this issue happened just after making the change to the display configuration. reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/evolution-calendar-factory.service cmdline: /usr/libexec/evolution-calendar-factory crash_function: soup_cookie_free executable: /usr/libexec/evolution-calendar-factory journald_cursor: s=45bbaf3cc7d64a3692403c3dc6fa8c63;i=c683;b=7c828e3a14274177b5308aa8a49f03f3;m=1876082430;t=5a4f53ce3bdd1;x=34b6c6eed2dfdcb9 kernel: 5.6.7-300.fc32.x86_64 package: evolution-data-server-3.36.2-1.fc32 reason: evolution-calendar-factory killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1900567 has been marked as a duplicate of this bug. ***
*** Bug 1915805 has been marked as a duplicate of this bug. ***
*** Bug 1916946 has been marked as a duplicate of this bug. ***
I think this is caused by the evolution-ews, its threading within the notification code is possibly causing trouble here, with some other aspects I'm investigating right now. I'm moving this to the evolution-ews.
*** Bug 1906187 has been marked as a duplicate of this bug. ***
*** Bug 1842729 has been marked as a duplicate of this bug. ***
*** Bug 1840522 has been marked as a duplicate of this bug. ***
*** Bug 1883935 has been marked as a duplicate of this bug. ***
I fixed this with commit [1] upstream, which is for 3.39.2+ and 3.38.4+ of the evolution-ews. [1] https://gitlab.gnome.org/GNOME/evolution-ews/-/commit/7eca6d662a6b229ad2276a42b58ce4df51d67240