Version-Release number of selected component: evolution-data-server-3.24.6-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory webcal --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx1826x11 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/1826/11 crash_function: webcal_to_http_method executable: /usr/libexec/evolution-calendar-factory-subprocess journald_cursor: s=200ba611675442429934ac76527ab302;i=6580;b=1a61efc9cb374e6e9c28b045a1dea698;m=31c82148d;t=55b424e578083;x=8908d09e1d05f5c8 kernel: 4.12.13-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 webcal_to_http_method at /usr/src/debug/evolution-data-server-3.24.6/src/calendar/backends/http/e-cal-backend-http.c:254 #1 cal_backend_http_load at /usr/src/debug/evolution-data-server-3.24.6/src/calendar/backends/http/e-cal-backend-http.c:573 #2 e_cal_backend_http_open at /usr/src/debug/evolution-data-server-3.24.6/src/calendar/backends/http/e-cal-backend-http.c:970 #3 cal_backend_open at /usr/src/debug/evolution-data-server-3.24.6/src/calendar/libedata-cal/e-cal-backend-sync.c:620 #4 cal_backend_open_thread at /usr/src/debug/evolution-data-server-3.24.6/src/calendar/libedata-cal/e-cal-backend.c:1560 #5 cal_backend_dispatch_thread at /usr/src/debug/evolution-data-server-3.24.6/src/calendar/libedata-cal/e-cal-backend.c:241 #7 g_thread_proxy at gthread.c:784
Created attachment 1337070 [details] File: backtrace
Created attachment 1337071 [details] File: cgroup
Created attachment 1337072 [details] File: core_backtrace
Created attachment 1337073 [details] File: cpuinfo
Created attachment 1337074 [details] File: dso_list
Created attachment 1337075 [details] File: environ
Created attachment 1337076 [details] File: limits
Created attachment 1337077 [details] File: maps
Created attachment 1337078 [details] File: open_fds
Created attachment 1337079 [details] File: proc_pid_status
Created attachment 1337080 [details] File: var_log_messages
Created attachment 1337081 [details] File: exploitable
Thanks for a bug report. I see from the backtrace that one of your On The Web calendars (or tasks, or memos) failed to open due to it having either none or broken URL set. It at least look like that. Could you verify that all your On The Web calendars (tasks/memos) have set correct URL, please? Finding which one causes the crash, eventually finding the consequences which lead to the crash, would help to properly fix the issue. I made a change upstream which will prevent the crash [1], that's for 3.27.1+ and a similar change for 3.26.2+, but I do not know whether it'll truly fix the root of the issue. That's the reason why I ask for the above information. Thanks in advance. [1] https://git.gnome.org/browse/evolution-data-server/commit/?id=01a01ef52
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.