Description of problem: don't know Version-Release number of selected component: gnome-shell-3.16.3-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: update_clock executable: /usr/bin/gnome-shell global_pid: 12965 kernel: 4.1.3-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 update_clock at gnome-wall-clock.c:345 #1 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1794 #2 _g_closure_invoke_va at gclosure.c:831 #5 g_settings_real_change_event at gsettings.c:296 #6 ffi_call_unix64 at ../src/x86/unix64.S:76 #7 ffi_call at ../src/x86/ffi64.c:525 #8 g_cclosure_marshal_generic_va at gclosure.c:1561 #9 _g_closure_invoke_va at gclosure.c:831 #12 settings_backend_path_changed at gsettings.c:397 #13 g_settings_backend_invoke_closure at gsettingsbackend.c:267 Potential duplicate: bug 1198085
Created attachment 1062180 [details] File: backtrace
Created attachment 1062181 [details] File: cgroup
Created attachment 1062182 [details] File: core_backtrace
Created attachment 1062183 [details] File: dso_list
Created attachment 1062184 [details] File: environ
Created attachment 1062185 [details] File: limits
Created attachment 1062186 [details] File: maps
Created attachment 1062187 [details] File: mountinfo
Created attachment 1062188 [details] File: namespaces
Created attachment 1062189 [details] File: open_fds
Created attachment 1062190 [details] File: proc_pid_status
Created attachment 1062191 [details] File: var_log_messages
Just experienced this with gnome-shell-3.16.4.1.fc22.x86_64 Found this line in my journal Nov 05 11:05:18 mastershake kernel: gnome-shell[2585]: segfault at 23 ip 00007f0ccacf025f sp 00007ffc07660ec0 error 4 in libgnome-desktop-3.so.10.0.0[7f0ccacd1000+38000]
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.