Description of problem: 1st boot after install Fedora 22 alpha netinstall on virtual box. Virtual box running on Fedora 21 Version-Release number of selected component: gnome-shell-3.16.0-1.fc22 Additional info: reporter: libreport-2.5.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 1439 kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64+debug runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #0 _g_log_abort at gmessages.c:315 #3 wrapped_gobj_toggle_notify at gi/object.cpp:1063 #4 g_settings_backend_invoke_closure at gsettingsbackend.c:271 #9 meta_run at core/main.c:437
Created attachment 1010389 [details] File: backtrace
Created attachment 1010390 [details] File: cgroup
Created attachment 1010391 [details] File: core_backtrace
Created attachment 1010392 [details] File: dso_list
Created attachment 1010393 [details] File: environ
Created attachment 1010394 [details] File: limits
Created attachment 1010395 [details] File: maps
Created attachment 1010396 [details] File: mountinfo
Created attachment 1010397 [details] File: namespaces
Created attachment 1010398 [details] File: open_fds
Created attachment 1010399 [details] File: proc_pid_status
Created attachment 1010400 [details] File: var_log_messages
Another user experienced a similar problem: i was trying gnome-software to move libreoffice applications into a folder in the shell view. reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 27646 kernel: 4.0.4-301.fc22.x86_64 package: gnome-shell-3.16.2-1.fc22 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
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.