Version-Release number of selected component: gnome-shell-3.16.2-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: update_num_workspaces executable: /usr/bin/gnome-shell global_pid: 1901 kernel: 4.0.4-201.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #4 update_num_workspaces at core/screen.c:1239 #5 emit_changed at core/prefs.c:876 #6 changed_idle_handler at core/prefs.c:902 #11 meta_run at core/main.c:437 Potential duplicate: bug 1177636
Created attachment 1032768 [details] File: backtrace
Created attachment 1032769 [details] File: cgroup
Created attachment 1032770 [details] File: core_backtrace
Created attachment 1032771 [details] File: dso_list
Created attachment 1032772 [details] File: environ
Created attachment 1032773 [details] File: limits
Created attachment 1032774 [details] File: maps
Created attachment 1032775 [details] File: mountinfo
Created attachment 1032776 [details] File: namespaces
Created attachment 1032777 [details] File: open_fds
Created attachment 1032778 [details] File: proc_pid_status
Created attachment 1032779 [details] File: var_log_messages
Another user experienced a similar problem: Hi all, thank you very much for your keen work! I was making some cleaning on my homeserver connected via Samba (I have a Wincrap laptop here ¬¬) browsing files using Files (Nautilus) and previewing pictures usiing 'Sushi' just to give it a try. Suddenly Sushi crashed and shortly after Files did too -- and after some seconds where system felt sluggish finally the desktop crashed too. Once the destkop loaded again I force a manually reload (Alt + F2, r) and since that things seems to be working okay. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: update_num_workspaces executable: /usr/bin/gnome-shell global_pid: 7927 kernel: 4.1.5-200.fc22.x86_64 package: gnome-shell-3.16.3-1.fc22 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
*** This bug has been marked as a duplicate of bug 1177636 ***