Description of problem: Don't know what happen to cause the problem but it occurs often. Version-Release number of selected component: evolution-data-server-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: strcmp executable: /usr/libexec/evolution-calendar-factory kernel: 3.12.10-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 32535 Truncated backtrace: Thread no. 1 (10 frames) #0 strcmp at ../sysdeps/x86_64/strcmp.S:209 #1 g_str_equal at ghash.c:1706 #2 gweather_info_get_forecast at weather.c:2204 #3 create_weather at e-cal-backend-weather.c:396 #4 finished_retrieval_cb at e-cal-backend-weather.c:191 #5 _g_closure_invoke_va at gclosure.c:840 #8 soup_session_process_queue_item at soup-session.c:1873 #9 async_run_queue at soup-session.c:1911 #10 idle_run_queue at soup-session.c:1945 #15 dbus_server_run_server at e-dbus-server.c:222
Created attachment 863915 [details] File: backtrace
Created attachment 863916 [details] File: cgroup
Created attachment 863917 [details] File: core_backtrace
Created attachment 863918 [details] File: dso_list
Created attachment 863919 [details] File: environ
Created attachment 863920 [details] File: exploitable
Created attachment 863921 [details] File: limits
Created attachment 863922 [details] File: maps
Created attachment 863923 [details] File: open_fds
Created attachment 863924 [details] File: proc_pid_status
Created attachment 863925 [details] File: var_log_messages
Thanks for a bug report. I see in the backtrace that this crashed in a weather calendar, when processing a forecast information. Could you tell me which location(s) you've filled for the Weather calendar(s), please? I'll use it for testing and as a possible reproducer for the crash.
I've got the same issue. My location is Portland, Oregon, USA.
i should be more specific: my selected weather location is Portland, Oregon, USA
Thanks for the hint. I configured Portland/Oregon weather calendars in my evolution (all three airports) and then also Portland/Maine (just in case), and I'll watch whether it'll crash to me too - it didn't yet, but it may depend on the information provided by the server.
I think I've got it. The weather calendar backend never freed the weather information source object, which is responsible for retrieving of weather information and due to this, when the backend was freed while the retrieval was still pending, the finish was called on an already freed object, which could lead to this crash. I fixed this for 3.11.91 development version of evolution-data-server, thus for 3.12.0 stable version, at: https://git.gnome.org/browse/evolution-data-server/commit/?id=a06764d
that means we won't see the fix until august or later though right?
3.12 will be released in March. I don't know when 3.12 will get into Fedora, though. Fedora is in a weird transition atm.
You are right, I'll backport the patch to 3.10.4-2.
evolution-data-server-3.10.4-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/evolution-data-server-3.10.4-2.fc20
evolution-data-server-3.10.4-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.