Description of problem: Crash on login? Version-Release number of selected component: gnome-shell-3.22.2-2.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: init_output executable: /usr/bin/gnome-shell global_pid: 1524 kernel: 4.9.8-201.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: unknown type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 init_output at backends/native/meta-monitor-manager-kms.c:790 #1 init_outputs at backends/native/meta-monitor-manager-kms.c:1120 #2 meta_monitor_manager_kms_read_current at backends/native/meta-monitor-manager-kms.c:1176 #3 meta_monitor_manager_read_current_config at backends/meta-monitor-manager.c:1371 #4 meta_monitor_manager_constructed at backends/meta-monitor-manager.c:327 #5 g_object_new_internal at gobject.c:1823 #8 create_monitor_manager at backends/meta-backend.c:275 #9 meta_backend_real_post_init at backends/meta-backend.c:287 #10 meta_backend_native_post_init at backends/native/meta-backend-native.c:259 #11 meta_init at core/main.c:493
Created attachment 1250067 [details] File: backtrace
Created attachment 1250068 [details] File: cgroup
Created attachment 1250069 [details] File: core_backtrace
Created attachment 1250070 [details] File: dso_list
Created attachment 1250071 [details] File: environ
Created attachment 1250072 [details] File: exploitable
Created attachment 1250073 [details] File: limits
Created attachment 1250074 [details] File: maps
Created attachment 1250075 [details] File: mountinfo
Created attachment 1250076 [details] File: namespaces
Created attachment 1250077 [details] File: open_fds
Created attachment 1250078 [details] File: proc_pid_status
Created attachment 1250079 [details] File: var_log_messages
Similar problem has been detected: Seems to be triggered by HDMI hotplug events (like when connected AV receiver is turned on and off). reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: init_output executable: /usr/bin/gnome-shell global_pid: 1142 kernel: 4.10.11-200.fc25.x86_64 package: gnome-shell-3.22.3-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
Lately I have been getting this crash increasingly often. Looking at the ABRT server reports it seems like it started sometime in March, so likely a regression as a result of some update.
Similar problem has been detected: Seems triggered by HDMI hotplug events reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: init_output executable: /usr/bin/gnome-shell global_pid: 6191 kernel: 4.10.14-200.fc25.x86_64 package: gnome-shell-3.22.3-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I left the computer idle. and while I was playing chess in the same room I saw gnome-shell crash. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: init_output executable: /usr/bin/gnome-shell global_pid: 1296 kernel: 4.10.17-200.fc25.x86_64 package: gnome-shell-3.22.3-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: HDMI hotplug events from connected AV receiver/TV reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: init_output executable: /usr/bin/gnome-shell global_pid: 10994 kernel: 4.11.3-200.fc25.x86_64 package: gnome-shell-3.22.3-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar crash is occurring in F26 still: Process 1762 (gnome-shell) of user 1000 dumped core. Stack trace of thread 1762: #0 0x00007fe8196dd7fd meta_monitor_manager_kms_read_current (libmutter-0.so.0) #1 0x00007fe81965ddfc meta_monitor_manager_read_current_state (libmutter-0.so.0) #2 0x00007fe8196db948 on_uevent (libmutter-0.so.0) #3 0x00007fe814f4830d g_closure_invoke (libgobject-2.0.so.0) #4 0x00007fe814f5a98e signal_emit_unlocked_R (libgobject-2.0.so.0) #5 0x00007fe814f631a5 g_signal_emit_valist (libgobject-2.0.so.0) #6 0x00007fe814f63b0f g_signal_emit (libgobject-2.0.so.0) #7 0x00007fe80ed577b4 monitor_event (libgudev-1.0.so.0) #8 0x00007fe814c70247 g_main_context_dispatch (libglib-2.0.so.0) #9 0x00007fe814c705e8 g_main_context_iterate.isra.25 (libglib-2.0.so.0) #10 0x00007fe814c70902 g_main_loop_run (libglib-2.0.so.0) #11 0x00007fe81968d38c meta_run (libmutter-0.so.0) #12 0x000055c704cc44a7 main (gnome-shell) #13 0x00007fe8130aa4da __libc_start_main (libc.so.6) #14 0x000055c704cc45ba _start (gnome-shell)
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.