Description of problem: I docked the laptop. Version-Release number of selected component: gnome-shell-3.18.1-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell global_pid: 2039 kernel: 4.1.6-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:535 #1 thread_memory_magazine1_alloc at gslice.c:842 #2 g_slice_alloc at gslice.c:998 #3 g_list_insert_before at glist.c:394 #4 find_source_list_for_priority at gmain.c:1000 #5 source_add_to_context at gmain.c:1034 #6 g_source_attach_unlocked at gmain.c:1115 #7 g_source_attach at gmain.c:1173 #8 g_idle_add_full at gmain.c:5508 #9 meta_later_add at core/util.c:904 Potential duplicate: bug 758808
Created attachment 1089715 [details] File: backtrace
Created attachment 1089716 [details] File: cgroup
Created attachment 1089717 [details] File: core_backtrace
Created attachment 1089718 [details] File: dso_list
Created attachment 1089719 [details] File: environ
Created attachment 1089720 [details] File: exploitable
Created attachment 1089721 [details] File: limits
Created attachment 1089722 [details] File: maps
Created attachment 1089723 [details] File: mountinfo
Created attachment 1089724 [details] File: namespaces
Created attachment 1089725 [details] File: open_fds
Created attachment 1089726 [details] File: proc_pid_status
Another user experienced a similar problem: Waking the machine after suspend with a external monitor plugged in (it wasn't plugged when the machine was suspended). reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 10e8566dc9cb6f4576136845732742676800000014320000 crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell global_pid: 2188 kernel: 4.2.5-300.fc23.x86_64 package: gnome-shell-3.18.1-1.fc23 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: computer got locked after unused for a while, got thrown out right away after re-login, login again: the session before the computer get locked is gone. Fedora 23. upgraded with fedup from F22 reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell global_pid: 2405 kernel: 4.2.5-300.fc23.x86_64 package: gnome-shell-3.18.1-1.fc23 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Happened when TV connected via HDMI was turned off reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell global_pid: 7147 kernel: 4.2.6-300.fc23.x86_64 package: gnome-shell-3.18.2-1.fc23 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I docked my laptop, my session logged out immediately. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell global_pid: 1989 kernel: 4.2.6-301.fc23.x86_64 package: gnome-shell-3.18.3-1.fc23 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: various problems with nautilus and all opening and closing of various applications reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell global_pid: 2428 kernel: 4.2.7-300.fc23.x86_64 package: gnome-shell-3.18.3-1.fc23 reason: gnome-shell killed by SIGSEGV runlevel: N 5 txt: txt type: CCpp uid: 1000
Now my Gnome Shell crashes every day after logging in.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.