gnome-shell crash in wayland+i915 (NOT i965) if Firefox/XWayland tries to go fullscreen using F11
In all of my Fedora machines, all of which use the i915 (NOT i965) driver, the Gnome Shell can be made to crash if I attempt to make Firefox go fullscreen using the F11 key.
I have tried to run gnome-shell through a wrapper script that sets GDK_SYNCHRONIZE=1, but I do not know if I did it correctly. The journalctl output is here: journalctl-gnome-shell-mutter-crash-1.txt Things start going wrong at the point the log start spewing out "Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!" multiple times.
List of installed packages on one example machine:
- firefox-61.0.1-3.fc28.x86_64
- gnome-shell-3.28.3-1.fc28.x86_64
- mutter-debugsource-3.28.3-3.1.fc28.x86_64
- mutter-debuginfo-3.28.3-3.1.fc28.x86_64
- mutter-3.28.3-3.1.fc28.x86_64
- mesa-libGLU-9.0.0-14.fc28.i686
- mesa-filesystem-18.0.5-3.fc28.i686
- mesa-libEGL-devel-18.0.5-3.fc28.i686
- mesa-libGLU-devel-9.0.0-14.fc28.x86_64
- mesa-libOSMesa-18.0.5-3.fc28.x86_64
- mesa-libGLES-devel-18.0.5-3.fc28.x86_64
- mesa-libglapi-18.0.5-3.fc28.i686
- mesa-lib#18 (closed).0.5-3.fc28.i686
- mesa-lib#18 (closed).0.5-3.fc28.x86_64
- mesa-libGLU-9.0.0-14.fc28.x86_64
- mesa-filesystem-18.0.5-3.fc28.x86_64
- mesa-libgbm-18.0.5-3.fc28.i686
- mesa-libE#18 (closed).0.5-3.fc28.x86_64
- mesa-libGLES-18.0.5-3.fc28.x86_64
- mesa-libglapi-18.0.5-3.fc28.x86_64
- mesa-dri-drivers-18.0.5-3.fc28.x86_64
- mesa-libxatracker-18.0.5-3.fc28.x86_64
- mesa-libOpenCL-18.0.5-3.fc28.x86_64
- mesa-libgbm-devel-18.0.5-3.fc28.x86_64
- mesa-libgbm-18.0.5-3.fc28.x86_64
- mesa-libEGL-devel-18.0.5-3.fc28.x86_64
- mesa-vulkan-drivers-18.0.5-3.fc28.x86_64
- mesa-libGL-devel-18.0.5-3.fc28.x86_64
- mesa-vulkan-drivers-18.0.5-3.fc28.i686
- mesa-libOSMesa-18.0.5-3.fc28.i686
- mesa-libE#18 (closed).0.5-3.fc28.i686
- mesa-dri-drivers-18.0.5-3.fc28.i686
- libdrm-devel-2.4.93-1.fc28.x86_64
- libdrm-2.4.93-1.fc28.i686
- libdrm-2.4.93-1.fc28.x86_64
- libwayland-client-1.15.0-1.fc28.i686
- libwayland-client-1.15.0-1.fc28.x86_64
- libwayland-cursor-1.15.0-1.fc28.i686
- libwayland-cursor-1.15.0-1.fc28.x86_64
- libwayland-egl-1.15.0-1.fc28.i686
- libwayland-egl-1.15.0-1.fc28.x86_64
- libwayland-server-1.15.0-1.fc28.i686
- libwayland-server-1.15.0-1.fc28.x86_64
- qt5-qtwayland-5.10.1-2.fc28.x86_64
- wayland-devel-1.15.0-1.fc28.x86_64
- wayland-protocols-devel-1.14-1.fc28.noarch
- xorg-x11-server-Xwayland-1.19.6-8.fc28.x86_64
- kernel-4.17.12-200.fc28.x86_64
- kernel-core-4.17.12-200.fc28.x86_64
- kernel-devel-4.17.12-200.fc28.x86_64
- kernel-devel-4.17.6-200.fc28.x86_64
- kernel-headers-4.17.12-1.fc28.x86_64
- kernel-modules-4.17.12-200.fc28.x86_64
- kernel-tools-4.17.12-200.fc28.x86_64
- kernel-tools-libs-4.17.12-200.fc28.x86_64
The video hardware in the same example machine:
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller])
Subsystem: Foxconn International, Inc. Device [105b:0ded]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at fdf00000 (32-bit, non-prefetchable) [size=512K]
I/O ports at ff00 [size=8]
Memory at d0000000 (32-bit, prefetchable) [size=256M]
Memory at fda00000 (32-bit, non-prefetchable) [size=1M]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
My observations so far:
- If I run Gnome Shell in X11 mode instead of Wayland mode, the crash does not happen.
- Apparently I need a minimum screen size to trigger the crash. My Acer Aspire One ZG5 cannot trigger the crash on its 1024x600 screen, but it can be triggered if I plug an external monitor (tested at 1280x1024), move the entire desktop there, then attempt the fullscreen Firefox. The example machine has a 1920x1200 monitor and reliably triggers the crash.
- On a large enough screen, the crash is reliable on i915. I have no access to any machine that does not use the i915 driver, so whether the crash happens outside of i915 is unknown.
- I am unable to trigger the crash if I run "mutter --wayland" and run Firefox inside that mutter session. It appears to require gnome-shell as well.
This crash has been happening since at least Fedora 23 (https://bugzilla.redhat.com/show_bug.cgi?id=1279291).
Please tell me whether and how to supply additional information that points to the cause of this crash.