Version-Release number of selected component: gnome-shell-3.24.2-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_monitor_get_main_output executable: /usr/bin/gnome-shell journald_cursor: s=c7819c8d1d564b3fbae0f0ac62b0a0d5;i=371b25;b=47e1a8fa91384267a25b6212c44d6ced;m=249478efb2;t=554a813d5ebc2;x=5cd91bb05091ad5f kernel: 4.11.9-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 meta_monitor_get_main_output at backends/meta-monitor.c:172 #1 meta_monitor_get_vendor at backends/meta-monitor.c:268 #2 logical_monitor_has_monitor at backends/meta-input-settings.c:746 #3 meta_input_settings_find_logical_monitor at backends/meta-input-settings.c:789 #4 update_device_display at backends/meta-input-settings.c:869 #5 apply_mappable_device_settings at backends/meta-input-settings.c:1078 #6 check_add_mappable_device at backends/meta-input-settings.c:1255 #10 g_signal_emit_by_name at gsignal.c:3487 #11 add_device at x11/clutter-device-manager-xi2.c:563 #12 translate_hierarchy_event at x11/clutter-device-manager-xi2.c:623
Created attachment 1300931 [details] File: backtrace
Created attachment 1300932 [details] File: cgroup
Created attachment 1300933 [details] File: core_backtrace
Created attachment 1300934 [details] File: cpuinfo
Created attachment 1300935 [details] File: dso_list
Created attachment 1300936 [details] File: environ
Created attachment 1300937 [details] File: limits
Created attachment 1300938 [details] File: maps
Created attachment 1300939 [details] File: open_fds
Created attachment 1300940 [details] File: proc_pid_status
Created attachment 1300941 [details] File: var_log_messages
Created attachment 1300942 [details] File: exploitable
Similar problem has been detected: When laptop in suspend, connection additional HDMI moitor. Wake up laptop and get this error. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_monitor_get_main_output executable: /usr/bin/gnome-shell journald_cursor: s=c7819c8d1d564b3fbae0f0ac62b0a0d5;i=53e364;b=85c0eea68b6f49a49d268dacefb651fd;m=104ee8916a;t=555d7f07c4803;x=cb7cc853995c3496 kernel: 4.11.11-300.fc26.x86_64 package: gnome-shell-3.24.3-1.fc26 reason: gnome-shell killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I attached an external monitor reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_monitor_get_main_output executable: /usr/bin/gnome-shell journald_cursor: s=26ba0c023611487a89de19e7b4de4b70;i=105b9e;b=b494041523194b069c5e00da1b5891ca;m=11e221101;t=5562a82c2dbb4;x=60a53c33f1bdf37b kernel: 4.11.8-300.fc26.x86_64 package: gnome-shell-3.24.3-1.fc26 reason: gnome-shell killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
My laptop was also in suspend while I attached the monitor, I just forgot about it while filling out the form but Alex Gluck's comment reminded me.
Similar problem has been detected: Woke from suspend with an external monitor attached via USB-C reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_monitor_get_main_output executable: /usr/bin/gnome-shell journald_cursor: s=c89d34ecb8ed4d9d87beb0f046e3ba4a;i=2d421e;b=c0087a3bc7fe43ab9d1c25765d06b7c3;m=c6ae55f8d;t=557c375c5da06;x=f92ac2e36e28c603 kernel: 4.12.8-300.fc26.x86_64 package: gnome-shell-3.24.3-1.fc26 reason: gnome-shell killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I woke up the laptop from suspend reporter: libreport-2.9.1 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: meta_monitor_get_main_output executable: /usr/bin/gnome-shell journald_cursor: s=1f49eba510c94ba9ac6e34c46dee1c62;i=11090f;b=c61ade292fea443bae50d018620d2d36;m=2be210d456;t=557cf1947c0ce;x=16dc44aaa1b5fa65 kernel: 4.12.5-300.fc26.x86_64 package: gnome-shell-3.24.3-1.fc26 reason: gnome-shell killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I Locked the screen, let the montior go into power save mode, waited a few minutes and unlocked the screen. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_monitor_get_main_output executable: /usr/bin/gnome-shell journald_cursor: s=a698abaa77cd4007949a77bb66d9cc88;i=d07526;b=6cbb5631e9ed4bb8b0f68c8300e30175;m=880d745;t=55a6b68db7dc7;x=48a9dc26538ce843 kernel: 4.12.14-300.fc26.x86_64 package: gnome-shell-3.24.3-2.fc26 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Crash occurred when opening Document Viewer from a message in an EWS account in Evolution. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_monitor_get_main_output executable: /usr/bin/gnome-shell journald_cursor: s=87d3e50818b646ac810ba9d2a5ebc8dc;i=44468;b=2c2b238886604faaacb47af235b0be5a;m=1080b4471e;t=55ca14116fc65;x=5ca2534ecf2aa16a kernel: 4.13.9-200.fc26.x86_64 package: gnome-shell-3.24.3-2.fc26 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I should add I also get seemingly related crashes in Xwayland, same symptoms. Leave the computer for it to go to sleep, come back to a login screen. I can't report the Xwayland bugs because the backtrace is always apparently unusable according to Abrt and it won't let me submit it. Retrace here: https://retrace.fedoraproject.org/faf/reports/1911767/ Not sure if this is tied to this issue?
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.