Hide Forgot
Version-Release number of selected component: gnome-shell-3.11.2-3.fc21 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: desktop_entry_unref executable: /usr/bin/gnome-shell kernel: 3.12.1-2.fc21.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 desktop_entry_unref at /lib/libgnome-menu-3.so.0 #1 g_slist_foreach at /lib/libglib-2.0.so.0 #2 cached_dir_free at /lib/libgnome-menu-3.so.0 #3 emit_monitors_in_idle at /lib/libgnome-menu-3.so.0 #4 g_idle_dispatch at /lib/libglib-2.0.so.0 #6 g_main_context_iterate.isra.23 at /lib/libglib-2.0.so.0 #8 meta_run at /lib/libmutter.so.0
Created attachment 828160 [details] File: backtrace
Created attachment 828161 [details] File: cgroup
Created attachment 828162 [details] File: core_backtrace
Created attachment 828163 [details] File: dso_list
Created attachment 828164 [details] File: environ
Created attachment 828165 [details] File: exploitable
Created attachment 828166 [details] File: limits
Created attachment 828167 [details] File: maps
Created attachment 828168 [details] File: open_fds
Created attachment 828169 [details] File: proc_pid_status
Created attachment 828170 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
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.