Description of problem: Version-Release number of selected component: gnome-shell-3.28.0-1.fc28 Additional info: reporter: libreport-2.9.4 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell journald_cursor: s=1a9836efc54b47039beef57c18610ce4;i=10a7486;b=a470ac63709145a5a864720fdd584b07;m=5bf475a0;t=569a016d82cbe;x=3002176bbc628931 kernel: 4.16.1-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:539 #1 thread_memory_magazine1_alloc at gslice.c:842 #2 g_slice_alloc at gslice.c:1016 #3 g_slice_alloc0 at gslice.c:1051 #4 g_object_notify_queue_freeze at gobject.c:241 #5 g_object_freeze_notify at gobject.c:1130 #6 clutter_actor_set_allocation at clutter-actor.c:10215 #7 st_widget_allocate at ../src/st/st-widget.c:420 #8 st_box_layout_allocate at ../src/st/st-box-layout.c:288 #9 clutter_actor_allocate_internal at clutter-actor.c:9972 Potential duplicate: bug 758808
Created attachment 1420677 [details] File: backtrace
Created attachment 1420678 [details] File: cgroup
Created attachment 1420679 [details] File: core_backtrace
Created attachment 1420680 [details] File: cpuinfo
Created attachment 1420681 [details] File: dso_list
Created attachment 1420682 [details] File: environ
Created attachment 1420683 [details] File: limits
Created attachment 1420684 [details] File: maps
Created attachment 1420685 [details] File: mountinfo
Created attachment 1420686 [details] File: open_fds
Created attachment 1420687 [details] File: proc_pid_status
Created attachment 1420688 [details] File: var_log_messages
Similar problem has been detected: I plugged in a TV via HDMI. The screen showed graphical glitches, then Gnome Shell crashed and I was logged out, with all running graphical programs terminated. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell journald_cursor: s=26dcbd78d85a41fca5c38d1b1a6fb42d;i=5af5c3;b=19a98601eb764cc28ce01d3fa245fd44;m=2511231;t=56ac315195127;x=bbdc8c2187372cdb kernel: 4.16.4-300.fc28.x86_64 package: gnome-shell-3.28.1-2.fc28 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1427332 [details] File: backtrace
I got this issue when connected laptop to external monitor as well. Also abrt helped to file two different stack traces, the other one is https://bugzilla.redhat.com/show_bug.cgi?id=1566329
*** Bug 1573620 has been marked as a duplicate of this bug. ***
*** Bug 1575252 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.