Hide Forgot
Description of problem: wanted to open gnome shell application list Version-Release number of selected component: gnome-shell-3.10.0.1-1.fc20 Additional info: reporter: libreport-2.1.8 abrt_installed_version: abrt-2.1.8-1.fc20.x86_64 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell kernel: 3.11.4-302.fc20.x86_64 libreport_version: libreport-2.1.8-1.fc20.x86_64 runlevel: unknown satyr_version: satyr-0.10-1.fc20.x86_64 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:545 #1 thread_memory_magazine1_alloc at gslice.c:848 #2 g_slice_alloc at gslice.c:1007 #3 g_slist_prepend at gslist.c:267 #4 _clutter_id_pool_remove at ./clutter-id-pool.c:106 #5 _clutter_stage_release_pick_id at ./clutter-stage.c:4399 #6 clutter_actor_real_unmap at ./clutter-actor.c:1576 #7 st_widget_unmap at st/st-widget.c:529 #8 clutter_actor_set_mapped at ./clutter-actor.c:1258 #9 clutter_actor_update_map_state at ./clutter-actor.c:1436 Potential duplicate: bug 702257
Created attachment 812341 [details] File: backtrace
Created attachment 812342 [details] File: cgroup
Created attachment 812343 [details] File: core_backtrace
Created attachment 812344 [details] File: dso_list
Created attachment 812345 [details] File: environ
Created attachment 812346 [details] File: exploitable
Created attachment 812347 [details] File: limits
Created attachment 812348 [details] File: maps
Created attachment 812349 [details] File: open_fds
Created attachment 812350 [details] File: proc_pid_status
Created attachment 812351 [details] File: var_log_messages
Clicked "Activities" reporter: libreport-2.1.8 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell kernel: 3.11.5-300.fc20.x86_64 package: gnome-shell-3.10.0.1-1.fc20 reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) runlevel: unknown type: CCpp uid: 501
Fresh install, Fedora 20 alpha. NoMachine client may have been in use. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell kernel: 3.11.5-300.fc20.x86_64 package: gnome-shell-3.10.0.1-1.fc20 reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) runlevel: unknown type: CCpp uid: 1000
Fresh install, Fedora 20 alpha. NoMachine client may have been in use. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell kernel: 3.11.4-302.fc20.x86_64 package: gnome-shell-3.10.0.1-1.fc20 reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) runlevel: unknown type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.