Description of problem: This crash occurred in an openQA test: https://openqa.fedoraproject.org/tests/36382 . That test boots the live image, switches to a VT and fiddles about with packages a bit to ensure an update is available, then switches back to the desktop and just sits there for 10 minutes to see what notifications show up. During that ten minutes idle time, Shell crashed and the system wound up back at GDM, which you can see in the video on the Logs & Assets tab. Version-Release number of selected component: gnome-shell-3.22.0-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: wl_resource_post_event executable: /usr/bin/gnome-shell global_pid: 1591 kernel: 4.8.0-0.rc6.git0.1.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 wl_resource_post_event at src/wayland-server.c:194 #1 wl_pointer_send_leave at /usr/include/wayland-server-protocol.h:3409 #2 meta_wayland_pointer_send_leave at wayland/meta-wayland-pointer.c:758 #3 meta_wayland_pointer_broadcast_leave at wayland/meta-wayland-pointer.c:785 #4 meta_wayland_pointer_set_focus at wayland/meta-wayland-pointer.c:814 #5 repick_for_event at wayland/meta-wayland-pointer.c:540 #6 meta_wayland_pointer_update at wayland/meta-wayland-pointer.c:548 #7 meta_display_handle_event at core/events.c:216 #8 event_callback at core/events.c:401 #9 _clutter_event_process_filters at clutter-event.c:1913
Created attachment 1204899 [details] File: backtrace
Created attachment 1204900 [details] File: cgroup
Created attachment 1204901 [details] File: core_backtrace
Created attachment 1204902 [details] File: dso_list
Created attachment 1204903 [details] File: environ
Created attachment 1204904 [details] File: exploitable
Created attachment 1204905 [details] File: limits
Created attachment 1204906 [details] File: maps
Created attachment 1204907 [details] File: mountinfo
Created attachment 1204908 [details] File: namespaces
Created attachment 1204909 [details] File: open_fds
Created attachment 1204910 [details] File: proc_pid_status
Created attachment 1204911 [details] File: var_log_messages
oh, the test does move the mouse pointer every 2 minutes to avoid the screensaver kicking in. the crash may have happened when it was doing that. openQA sends pointer events via VNC (using qemu's built-in VNC server).
The test also has crash logs from one second after the GNOME Shell crash for gjs and evolution-alarm-notify. The gjs report shows as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1379125 . The evolution-alarm-notify crash I reported as https://bugzilla.redhat.com/show_bug.cgi?id=1379445 .
*** Bug 1379450 has been marked as a duplicate of this bug. ***
So I looked through the past results in openQA and I *think* this is the first time we've hit this crash. However, this test is quite new - it's only really been running in production for the last couple of days - so we can't say for sure that the crash is new (we have other tests that boot to the desktop and do stuff, but none that just sit about moving the pointer occasionally for ten minutes).
I think it'll be fixed by "wayland/pointer: Unset pointer focus when disabled" in https://bugzilla.gnome.org/show_bug.cgi?id=771646 .
I'll nominate this for a Beta freeze exception, then, because Shell crashes are bad (especially now, with Wayland, they don't just result in an automatic restart of Shell and a crash notification, but dump you back to GDM). As the Beta freeze will be in effect in a few hours, the procedure for getting this fixed in Beta would be to do a mutter build with the fix backported (and ideally as few other changes as possible) and submit it as an update marked as fixing this bug. Assuming this gets accepted as an FE issue, qa and releng would then together pull the fix in through the freeze.
I was asked to give a +1 on this FE, so here it is. :-)
well, I asked you to vote, which *way* you vote is up to you. If you don't think it's worthy, go ahead and vote your conscience ;)
mutter-3.22.0-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-c0d544981f
+1 FE here.
That's +3, marking accepted.
mutter-3.22.0-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Similar problem has been detected: I tried to reproduce bug 1379098. I switched to VT and back to GNOME several times (6 or 7 times) in a row, immediately. Right after that GNOME crashed. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: wl_resource_post_event executable: /usr/bin/gnome-shell global_pid: 6909 kernel: 4.8.1-1.fc25.x86_64 package: gnome-shell-3.22.1-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
It seems this is not fixed after all. Or it is a different crash with the same traceback. The first time I tried this, comment 26 was created, but second time I tried it, I reproduced bug 1379098 instead. Maybe they are closely related (or there are 2 races).
I don't think openqa has hit this lately, so removing that tag.
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.