Version-Release number of selected component: gnome-shell-3.10.0.1-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/gnome-shell-calendar-server crash_function: calendar_sources_init executable: /usr/libexec/gnome-shell-calendar-server kernel: 3.11.1-300.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #2 calendar_sources_init at calendar-server/calendar-sources.c:190 #3 g_type_create_instance at gtype.c:1868 #4 g_object_new_internal at gobject.c:1746 #7 calendar_sources_get at calendar-server/calendar-sources.c:276 #8 app_new at calendar-server/gnome-shell-calendar-server.c:773 #9 on_bus_acquired at calendar-server/gnome-shell-calendar-server.c:989 #10 connection_get_cb at gdbusnameowning.c:480 #11 g_simple_async_result_complete at gsimpleasyncresult.c:777 #12 complete_in_idle_cb at gsimpleasyncresult.c:789
Created attachment 804896 [details] File: backtrace
Created attachment 804897 [details] File: cgroup
Created attachment 804898 [details] File: core_backtrace
Created attachment 804899 [details] File: dso_list
Created attachment 804900 [details] File: environ
Created attachment 804901 [details] File: limits
Created attachment 804902 [details] File: maps
Created attachment 804903 [details] File: open_fds
Created attachment 804904 [details] File: proc_pid_status
Another user experienced a similar problem: I had chrome running icloud.com mail - logged out of Fedora 20 to reset video card - saw error when I logged back into Fedora reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/gnome-shell-calendar-server crash_function: calendar_sources_init executable: /usr/libexec/gnome-shell-calendar-server kernel: 3.12.5-302.fc20.i686+PAE package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell-calendar-server killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Seen with gnome-shell-3.10.3-6.fc20. I've filed it upstream.