Description of problem: using chrome under fedora26, window closed suddenly and crash report came up Version-Release number of selected component: gnome-shell-3.26.2-1.fc27 Additional info: 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=5153346d4d944966b29bc99645c27b83;i=bac7c0;b=9f6c2ba0c22e42caad080791af9fadb0;m=4975151f8;t=55f17057c63c7;x=fa7c0a6375f2b13f kernel: 4.13.13-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 Potential duplicate: bug 1510210
Created attachment 1360140 [details] File: backtrace
Created attachment 1360141 [details] File: cgroup
Created attachment 1360142 [details] File: core_backtrace
Created attachment 1360143 [details] File: cpuinfo
Created attachment 1360144 [details] File: dso_list
Created attachment 1360145 [details] File: environ
Created attachment 1360146 [details] File: exploitable
Created attachment 1360147 [details] File: limits
Created attachment 1360149 [details] File: maps
Created attachment 1360150 [details] File: mountinfo
Created attachment 1360151 [details] File: open_fds
Created attachment 1360152 [details] File: proc_pid_status
Created attachment 1360153 [details] File: var_log_messages
*** Bug 1518869 has been marked as a duplicate of this bug. ***
*** Bug 1519031 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Powered off monitor and powered back on. Was greeted with logon screen, and a gnome-shell crashed warning and empty desktop upon logging 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=9d3266d2e6ea4311834d63ae18c172aa;i=e7459;b=aab67318f3664527bb5916a323755481;m=2092f1a5f;t=55f27ac5e6fb1;x=a52c969b4205ffeb kernel: 4.13.15-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 1519488 has been marked as a duplicate of this bug. ***
*** Bug 1519525 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Crashed after re-login after screen lock 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=b5bf40a2e71b4f32ab5487790ba75d79;i=242458;b=d1ca0f31f8574b3d8e748ac41d31c72b;m=e01972552;t=55f6bd7021a8d;x=ea4784005bd686bc kernel: 4.13.16-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 1520142 has been marked as a duplicate of this bug. ***
*** Bug 1520143 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Looks like this happens either when the machine attempts to go to sleep or wakes up again. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=1ae54ce3078c42ed87de4ff62375b21e;i=1536f4;b=8bd23ea3c3934dbda52e191c4328ccfb;m=17038e85a;t=55f944ebd4085;x=f3f206ba52e49c9b kernel: 4.13.16-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: Laptop left untouched for a while, issue occured on suspend or resume. I have two display adapters: Intel and Nvidia one (sth. called Optimus Laptop (ref: bumblebee), issue may be somehow related to that.. 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=974fb27cb1844b36907a44ee55d5f622;i=11ba;b=d42a9f42e0904c00a00f0bc4f7b15a26;m=2a3ff3318d;t=55fa5c6dfe533;x=df6837ed81d9a186 kernel: 4.13.16-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
In my case it is also a Laptop with Optimus configuration (Thinkpad W530), so that might be a causing factor.
Similar problem has been detected: Woke up screen after it went to sleep because of no activity. 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=95720a6d0b29400680a3708f429d1533;i=4626;b=04d42b824a084831a25069f15e85e6ac;m=14b058b91;t=55fc579914821;x=950eee23cee26ca1 kernel: 4.13.16-302.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: turning off monitor causes gnome session to log out. after logging back in I get a SIGSEGV error either from gnome-shell or from wayland. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: meta_logical_monitor_get_scale executable: /usr/bin/gnome-shell journald_cursor: s=f4640025399d44b5a0ecbe8fd1e74181;i=5eb91;b=fef4d9018ab44871a85af72cbb94ba62;m=149105c0;t=55fcb1770cccf;x=fa5a6681aad9cf1b kernel: 4.13.16-302.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: Left my computer to auto stand-by, come back to find it still on and gnome-shell crashed and I'm back at the login screen. So machine doesn't go into stand-by and I lose my session. This is happening pretty regularly. I can pretty much guarantee that unless I manually suspend, gnome-shell crashes. I've disabled all my extensions. Most of the time, only Firefox is running. 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=1ae54ce3078c42ed87de4ff62375b21e;i=170147;b=d5b6681d0c9d48939fe9b2eb32171c3e;m=b3d89545d;t=55fcf5d09cb3e;x=fb4813a2fae8ac8a kernel: 4.13.16-302.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: Unplugged a USB cable to a Belkin SOHO KVM, reconnected it, looked at screen and my login session was gone. 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=a621a5ed293f437d9d1883f5cbd98702;i=cd55;b=cbea5515399644179ab42bac0b912237;m=4cc5421351;t=55fd4b0bc0b57;x=4f895c422840d2b5 kernel: 4.13.16-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: 1. boot f27 live iso 2. use gnome menu to lock screen 3. observe dpmi shut off screen 4. press shift to wake up 5. observe gnome has crashed, now at login screen 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=1dba8430151d4a2a9c0a3ca8533d9493;i=780;b=e06c4b30c94f4e5eba43763216b6bcd2;m=387cce3;t=55ffc4c4e5142;x=d1be4d68b0d73c29 kernel: 4.13.9-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
This seems to be the upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=788788 There's a patch here that seems promising: https://bug788764.bugzilla-attachments.gnome.org/attachment.cgi?id=361654&action=diff&collapsed=&context=patch&format=raw&headers=1 I haven't been able to try it yet because mutter on rawhide is out of sync with pipewire header files so it's not building. I'll give it a try as soon as I can though... this bug is driving me nuts, with GNOME crashing every time the screensaver runs.
Similar problem has been detected: I just upgraded from v26 to v27. All went fine. I was running 2 KVM instances, 3 Chrome tabs, one was playing Pandora through external speakers. THen I went upstairs to take a short break. By the time I came back down, I noticed music wasn't playing anymore. Moving mouse woke up the lock screen. After getting in, it says XWayLand crashed. The screen was as if nothing was running. I was able to get on KVM and shut them down properly. Then I rebooted Fedora machine. After logging in, I turned off screen inactivity lock & suspension in power settings. After lunch, i noticed same thing happened. This time, it says GNome shell crash. 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=686c801610d6407d9b10c46f901527d0;i=3d938;b=f5978e0cbc1d45c9ab6969a9f9572161;m=29b82ea54;t=560162e6719b4;x=4fe5fe3c337d7fd6 kernel: 4.14.3-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
(In reply to Russell Griffiths from comment #0) > Description of problem: > using chrome under fedora26, window closed suddenly and crash report came up > > Version-Release number of selected component: > gnome-shell-3.26.2-1.fc27 > > Additional info: > 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=5153346d4d944966b29bc99645c27b83;i=bac7c0; > b=9f6c2ba0c22e42caad080791af9fadb0;m=4975151f8;t=55f17057c63c7; > x=fa7c0a6375f2b13f > kernel: 4.13.13-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 > > Potential duplicate: bug 1510210 Have stopped bug by disabling extensions in Chrome browser. Not sure which one, will re enable one by one til we find ghe culprit
(In reply to Russell Griffiths from comment #32) > Have stopped bug by disabling extensions in Chrome browser. > Not sure which one, will re enable one by one til we find ghe culprit You might have stopped tripping the bug on your system, but it's different from the majority of reports here. There are lots of ways to hit this bug--same backtrace--the main ones are slow wake from DPMS or disconnecting a monitor.
Agreed. I'm not using Chrome on my system and hitting this bug. So possibly not application related.
I tried a build of mutter with both the patches from https://bugzilla.gnome.org/show_bug.cgi?id=788788 and https://bugzilla.gnome.org/show_bug.cgi?id=788764 but GNOME still crashes if I shut off my monitor. Not sure if the crash is the same or other related problems, but just wanted to follow up to mention that those patches don't fully resolve the problem, at least.
Similar problem has been detected: The session seems to crash when left for a while, not while using it. Possibly caused when the screensaver cuts 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=0c59f0327266481d9167a521ae620dff;i=d35;b=b0efdc4e435f4a76a738c29e2f18d3aa;m=1af2acd5d;t=56025e4d00c57;x=452ac7a259361e8f kernel: 4.14.3-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: 500
*** Bug 1525932 has been marked as a duplicate of this bug. ***
*** Bug 1527216 has been marked as a duplicate of this bug. ***
I've disabled the monitor sleep and the issue seems to go away. Only problem is, monitors always stay on.
*** Bug 1542499 has been marked as a duplicate of this bug. ***
Is there an ETA for a fix for this? It's driving me crazy and totally undermines my use of Gnome.
*** Bug 1553095 has been marked as a duplicate of this bug. ***
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.