Description of problem: Booted. Started some applications. Walked away. . After some time, came back. Screen was blank. Pressed 'shift'. System now showed log-on screen. Version-Release number of selected component: gnome-shell-3.26.1-1.fc27 Additional info: reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=0feaff53abdc422785ebe79eb4ae0d2d;i=7114;b=f65121dec16d49adb5de42b68ac3ba6a;m=14989bcd4;t=55b2fd147b9e1;x=78af82616f3bcdc5 kernel: 4.13.5-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 meta_logical_monitor_get_scale at backends/meta-logical-monitor.c:181 #1 get_window_geometry_scale_for_logical_monitor at wayland/meta-window-wayland.c:73 #2 meta_window_wayland_get_geometry_scale at wayland/meta-window-wayland.c:637 #3 meta_window_wayland_move_resize_internal at wayland/meta-window-wayland.c:211 #4 meta_window_move_resize_internal at core/window.c:3962 #5 meta_window_move_resize_now at core/window.c:4205 #6 idle_move_resize at core/window.c:4240 #7 call_idle_later at core/util.c:866 #13 meta_run at core/main.c:648
Created attachment 1336745 [details] File: backtrace
Created attachment 1336746 [details] File: cgroup
Created attachment 1336747 [details] File: core_backtrace
Created attachment 1336748 [details] File: cpuinfo
Created attachment 1336749 [details] File: dso_list
Created attachment 1336750 [details] File: environ
Created attachment 1336751 [details] File: exploitable
Created attachment 1336752 [details] File: limits
Created attachment 1336753 [details] File: maps
Created attachment 1336754 [details] File: open_fds
Created attachment 1336755 [details] File: proc_pid_status
Created attachment 1336756 [details] File: var_log_messages
Similar problem has been detected: Rebooted. All I did was to connect to wired ethernet -- did not start applications. Left system sitting there. When some time later I came back, the display was blank. Pressed 'shift' , and the system showed me the log-in screen. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=0feaff53abdc422785ebe79eb4ae0d2d;i=859a;b=afa14ec1da18480f93b024de72ea9771;m=6bf86564;t=55b32a3f81fa0;x=5d8ca611136d5e3 kernel: 4.13.5-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: 1. Run firefox, terminal 2. Lock computer and leave it for some time 3. Come back to crash report I've had issues with Fedora (26, 27b) randomly freezing under similar conditions (very light load) which has to be reset using the power button, this may be related. This is the first time it's been able to recover - the previous times the system wasn't locked. The crash seems to be hastened when playing music from youtube or from the disk using CMUS. Attempts to resolve random freezing (10 min~2 hour intervals): - Disable screen blanking in xorg.conf.d - Update BIOS (ASUS Prime X370-PRO - BIOS revision 0902) - Upgrade Fedora to 27b - Use mainline kernel - Replace thermal paste on CPU, reseat graphics card - Add amd_iommu=fullflush iommu=pt to GRUB_CMDLINE_LINUX These last two seemed to have stabilised everything, the system hadn't crashed while in use for 1 1/2 days, until now. Configuration: AMD Ryzen 5 1600 Radeon RX 480 (using amdgpu) journalctl -b -p err -- Logs begin at Mon 2017-10-09 23:55:27 BST, end at Tue 2017-10-17 12:38:51 BST. -- Oct 17 11:14:33 localhost.localdomain kernel: ACPI Error: Needed [Integer/String/Buffer], found [Region] ffff91511e971d80 (20170728/exresop-424) Oct 17 11:14:33 localhost.localdomain kernel: ACPI Exception: AE_AML_OPERAND_TYPE, Could not execute arguments for [IOB2] (Region) (20170728/nsinit-426) Oct 17 11:14:34 localhost.localdomain kernel: amdgpu 0000:28:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff Oct 17 10:14:51 localhost.localdomain kernel: sp5100_tco: I/O address 0x0cd6 already in use Oct 17 10:14:51 localhost.localdomain kernel: kvm: disabled by bios Oct 17 10:14:51 localhost.localdomain kernel: kvm: disabled by bios Oct 17 10:15:32 localhost.localdomain spice-vdagent[1510]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Oct 17 10:15:54 localhost.localdomain spice-vdagent[2011]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Oct 17 10:16:15 localhost.localdomain pulseaudio[1888]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Oct 17 12:16:13 localhost.localdomain gnome-session-binary[1704]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 17 12:16:15 localhost.localdomain systemd-coredump[6622]: Process 1825 (gnome-shell) of user 1000 dumped core. Stack trace of thread 1825: #0 0x00007fb98e892230 meta_logical_monitor_get_scale (libmutter-1.so.0) #1 0x00007fb98e91d26b meta_window_wayland_get_geometry_scale (libmutter-1.so.0) #2 0x00007fb98e91d6e1 meta_window_wayland_move_resize_internal (libmutter-1.so.0) #3 0x00007fb98e8e2fe3 meta_window_move_resize_internal (libmutter-1.so.0) #4 0x00007fb98e8e3b44 idle_move_resize (libmutter-1.so.0) #5 0x00007fb98e8dce9f call_idle_later (libmutter-1.so.0) #6 0x00007fb9903b0597 g_idle_dispatch (libglib-2.0.so.0) #7 0x00007fb9903b3bb7 g_main_context_dispatch (libglib-2.0.so.0) #8 0x00007fb9903b3f60 g_main_context_iterate.isra.25 (libglib-2.0.so.0) #9 0x00007fb9903b4272 g_main_loop_run (libglib-2.0.so.0) #10 0x00007fb98e8cffdc meta_run (libmutter-1.so.0) #11 0x00005578fe262267 main (gnome-shell) #12 0x00007fb98e24903a __libc_start_main (libc.so.6) #13 0x00005578fe26237a _start (gnome-shell) I tried to make this report as complete as possible, if there's anything else you need, please let me know and I'll send it along. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=0cdd9868887542f1bb70d08a9778855c;i=a2d2;b=e4ff0d45a85748c098b79ed41019344d;m=1b361e92a;t=55bbc4061f6dc;x=60749a52b1c04ab1 kernel: 4.14.0-0.rc4.git4.1.vanilla.knurd.1.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1339682 [details] File: backtrace
Recurrent problem, happened under exactly the same conditions today. Running Firefox, Emacs and terminal - locked, came back, logged in to a blank desktop with a "GNOME Shell quit unexpectedly" message.
*** Bug 1506228 has been marked as a duplicate of this bug. ***
*** Bug 1508390 has been marked as a duplicate of this bug. ***
*** Bug 1508811 has been marked as a duplicate of this bug. ***
*** Bug 1509363 has been marked as a duplicate of this bug. ***
*** Bug 1509500 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This happens every time I lock my screen or it goes to sleep. It also happens when I switch to another machine via KVM (the device not the kernel feature) everything is connected up with displayport reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=6e93c329ebc3467e8ab2079b21a03d03;i=2904d;b=8636692433204dd2b3b5dc21f6e6ac51;m=323c4ee15;t=55d827d438170;x=7babbb42067ceb5b kernel: 4.13.11-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1511699 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Just disconnect monitor which was connected via HDMI reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=080dd602856d412c9a43640ef29bfca7;i=2b9a50;b=7d61f60d9e2d41b79c90654b1032f43d;m=37303547;t=55da6ba2faf72;x=1eba314d896db020 kernel: 4.13.12-300.fc27.x86_64+debug package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I allowed my session to lock. When unlocking the gnome session died and all applications were closed. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=5f436a2f3268471d87d74ebe94d6b5aa;i=18b1d5;b=2226bb31000d41a495ef4490418f47ee;m=12943a9a2;t=55db80e56bc09;x=a3b3cfc3897deb1c kernel: 4.13.11-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Turn off monitor connected via Display Port while logged in. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=77d908ac7e0047c088e5c5c70d2f0a70;i=56861;b=11a255cc39854c77bdaccfa70f00e59e;m=178bb05fc;t=55df5fec14aad;x=ca4f9373790bee31 kernel: 4.13.12-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1513184 has been marked as a duplicate of this bug. ***
I have the same problem when returning from a locked screen. I am also getting regular xwayland crashes, which might be related.
Similar problem has been detected: Open Firefox, leave PC for a while, lock screen sets in, after unlocking gnome shell crashes reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=d9bfb4e3528844adabdee1bec9424820;i=6e05;b=0a3b441541ba4352a7be4efcd27fcd83;m=469d136f4;t=55dfa74d74159;x=7645c8283cb40096 kernel: 4.13.12-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I'm seeing many types of gnome-shell crashes, but this one seems to be caused by locking the screen and trying to log back in. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=24c25b90ba134b9f9fd6364a26c406ea;i=357cd;b=15fd771f5aeb46baa1c524c5306de177;m=1306d25a;t=55e0839f94a6a;x=13639523ca451ff5 kernel: 4.13.12-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
After very limited testing, it seems I can only reproduce this under wayland. xorg is fine.
Similar problem has been detected: Wake from monitor sleep reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=1692d9ea62f6444199f122430d33ca98;i=f6f6;b=32f7b1e9ea1e4074bbd4bb71e4fc2f04;m=931059108;t=55e177e9420f7;x=da451dcec350894c kernel: 4.13.12-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I raised this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1513807 Looks to be the same as this. Crashes after return from monitor sleep.
I think this is the same as https://bugzilla.gnome.org/show_bug.cgi?id=788764 which was fixed with https://git.gnome.org/browse/mutter/commit/?id=3572502
*** Bug 1514597 has been marked as a duplicate of this bug. ***
*** Bug 1514764 has been marked as a duplicate of this bug. ***
Can the fix be backported?
Assuming it's the same crash, loads of people have already been hit by it: https://retrace.fedoraproject.org/faf/reports/1911767/
Similar problem has been detected: I am using an ATEN KVM (DisplayPort model) and I think switching between consoles caused the Gnome shell to crash. Repro requirements: 2 PCs connected to ATEN KVM via display port and USB for keyboard and mouse Steps to repro: 1) Switch KVM to second PC 2) Switch KVM back to first PC 3) On returning to first PC, session has been logged out as Gnome shell has crashed. * Note: This crash seems to only happen periodically dmeseg shows the following errors when switching consoles [ 828.914030] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed [ 828.914062] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed [ 829.100945] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed [ 829.100967] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed [ 900.719764] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed [ 900.719786] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed [ 900.905667] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed [ 900.905688] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=3a2d24ec6c2244db974f5216bc306552;i=9f3f;b=7d9c6c73e1644bc3921d200c7bd7c0f5;m=7bedcde4;t=55e86de7b6044;x=e8f62c0a0083b291 kernel: 4.13.13-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1516143 has been marked as a duplicate of this bug. ***
Three thousand crashes so far... is a fix planned?
This is a mutter issue, not gnome-shell, actually. The fix is in comment 34.
So the commit against the mutter repo will be picked up by Fedora? Any ideas on time frames?
I'm trying to run a scratch build with the patch added, but I'm bitten by bug 1514955
FWIW, I've ran a test (scratch) build with the fix added here: https://koji.fedoraproject.org/koji/taskinfo?taskID=23334681 You may want to try this build to see if that helps (I reckon it would). Being a scratch build, the files will be removed shortly. Also, worth noting, to avoid bug 1514955, remote-desktop is disabled in this build.
Fixed it for me. Quick test. Installed rebooted for good measure. logged in and started some apps. locked the screen putting monitor to sleep. left it for a few mins. woke the screen up and no crash.
Can confirm longer term testing no problems. Appears fixed with the test (scratch) build.
Thanks Olivier wfm :-)
Read the fix for the mutter bug: -- We tried to get the geometry scale, which may depend on the main logical monitor assigned to the window. To avoid dereferencing a NULL logical monitor when headless, instead assume the geometry scale is 1. -- Wouldn't it make more sense to just keep the current scaling factor when the monitor becomes NULL? Most people are either allowing their monitor to power down due to inactivity or are switching to another display. When the monitor is reattached, scaling should be the same. If a user is switching to a different monitor, scaling can be updated then. It seems that the machine is going to have to do unnecessary scaling work when the monitor is disconnected and again when reconnected, if the scaling factor for the moniotor is !=1.
(In reply to Tony from comment #49) > Wouldn't it make more sense to just keep the current scaling factor when the > monitor becomes NULL? I think it would be better to report these concerns upstream (for example by cloning the bug upstream mentioned in comment 34).
*** Bug 1520110 has been marked as a duplicate of this bug. ***
Any reason that the fix hasn't been pushed yet? Is there something we can do to help moving this forward?
So I have some more PC doing this. Seems to be devices on display port where the monitor takes a while to start up. Must be effecting lots of people.
(In reply to Olivier Fourdan from comment #50) > (In reply to Tony from comment #49) > > Wouldn't it make more sense to just keep the current scaling factor when the > > monitor becomes NULL? > > I think it would be better to report these concerns upstream (for example by > cloning the bug upstream mentioned in comment 34). Thanks Oliver. In fact, I'm not terribly concerned about this detail. I'm more concerned that I still cannot switch inputs on my monitor without my session being destroyed. Anything I can do to help move this forward?
mutter-3.26.2-2 in testing (https://bodhi.fedoraproject.org/updates/FEDORA-2017-39b370bebf) includes the fix for this bug, thanks Rui!
Gnome is still crashing when I switch my monitor to another machine: Process 2071 (gnome-shell) crashed in image_get_buffers() Reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1531472
This is still a problem with updated mutter: [dude@chainsaw ~]# dnf list installed | grep mutter mutter.x86_64 3.26.2-2.fc27 @updates [dude@chainsaw ~]# abrt-cli list id 302d5f5b717f5cb1a0ab5e1eb8bdc4ad8a4a786f reason: image_get_buffers(): gnome-shell killed by SIGSEGV time: Fri 23 Feb 2018 09:40:23 AM EST cmdline: /usr/bin/gnome-shell package: gnome-shell-3.26.2-4.fc27 uid: 42 (gdm) count: 1 Directory: /var/spool/abrt/ccpp-2018-02-23-09:40:23.350793-1639 [dude@chainsaw ~]# I am unable to report because abrt says my backtraces are "unusable" but offers no reason why. If there is anything at all I can do to help resolve this issue, please let me know. As things are now, getting any work done on this platform is difficult.
Similar problem is reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=788834
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.