Description of problem: I was trying to add attendees to a new calendar entry I was creating Version-Release number of selected component: evolution-data-server-3.28.5-1.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.Calendarx2436x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2436/2 crash_function: pvl_next executable: /usr/libexec/evolution-calendar-factory-subprocess journald_cursor: s=d153c11c59084fc1af3f882cbc362bab;i=2efb69;b=7d3fb1cd89a64f15a16d4c027998cbbd;m=3433b2ae7;t=5757d23a10203;x=e4b19e28944ae9db kernel: 4.18.5-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 pvl_next at /usr/src/debug/libical-3.0.3-2.fc28.x86_64/src/libical/pvl.c:466 #1 icalcomponent_remove_component at /usr/src/debug/libical-3.0.3-2.fc28.x86_64/src/libical/icalcomponent.c:508 #2 e_cal_backend_file_receive_objects at /usr/src/debug/evolution-data-server-3.28.5-1.fc28.x86_64/src/calendar/backends/file/e-cal-backend-file.c:3489 #3 cal_backend_receive_objects at /usr/src/debug/evolution-data-server-3.28.5-1.fc28.x86_64/src/calendar/libedata-cal/e-cal-backend-sync.c:810 #4 cal_backend_receive_objects_thread at /usr/src/debug/evolution-data-server-3.28.5-1.fc28.x86_64/src/calendar/libedata-cal/e-cal-backend.c:3253 #5 cal_backend_dispatch_thread at /usr/src/debug/evolution-data-server-3.28.5-1.fc28.x86_64/src/calendar/libedata-cal/e-cal-backend.c:275 #7 g_thread_proxy at gthread.c:784
Created attachment 1484609 [details] File: backtrace
Created attachment 1484610 [details] File: cgroup
Created attachment 1484611 [details] File: core_backtrace
Created attachment 1484612 [details] File: cpuinfo
Created attachment 1484613 [details] File: dso_list
Created attachment 1484614 [details] File: environ
Created attachment 1484615 [details] File: exploitable
Created attachment 1484616 [details] File: limits
Created attachment 1484617 [details] File: maps
Created attachment 1484618 [details] File: mountinfo
Created attachment 1484619 [details] File: open_fds
Created attachment 1484620 [details] File: proc_pid_status
Thanks for a bug report. Just to make a connection to another bug, which happened at the same time: bug #1630787
If I read the backtrace properly, then you've received a meeting "invitation" mail which cancelled either whole meeting or an instance of a recurring meeting. You clicked in Evolution's UI to "Update Calendar", while you've stored this meeting in one of the On This Computer calendars. Evolution sent this cancelled event to the calendar and the calendar backend had been updating the locally stored information about it, while the backend process crashed. Am I close to the circumstances, please? The backtrace even shows the event UID, with which it's easy to find it. It's "CE7E38931706A309C12582D3002B6DC4-Lotus_Notes_Generated" (quotes for clarity only). Having it for testing would be nice (it can be found in ~/.local/share/evolution/calendar/ in one of the files of the subfolders), together with the corresponding invitation email, but I understand it contains plenty of private information, which might be hard to remove. Thus maybe if you could confirm the above guesses and check what the offending event looks like both in the local calendar and in the invitation mail (is recurring? is yes, does it have detached instances?), thus I could try to reproduce this here.
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.