Description of problem: In Fedora 23, a gnome-shell session running under X11 will put firefox in a full-screen window when pressing F11. This is the expected behavior. When running the same version of firefox and gnome-session under wayland, pressing F11 instead locks up the session completely. The keyboard becomes unresponsive, the mouse freezes, the console switch keys (Ctrl-Alt-FN) do not work either. Once this happens, I have to hard-reset the machine. Version-Release number of selected component (if applicable): firefox-42.0-2.fc23.x86_64 gnome-session-3.18.1.2-1.fc23.x86_64 kernel-core-4.2.5-300.fc23.x86_64 libwayland-cursor-1.9.0-1.fc23.x86_64 gnome-session-wayland-session-3.18.1.2-1.fc23.x86_64 libwayland-client-1.9.0-1.fc23.i686 xorg-x11-server-Xwayland-1.18.0-0.6.20151027.fc23.x86_64 libwayland-client-1.9.0-1.fc23.x86_64 libwayland-client-devel-1.9.0-1.fc23.x86_64 libwayland-server-1.9.0-1.fc23.x86_64 wayland-devel-1.9.0-1.fc23.x86_64 libwayland-cursor-devel-1.9.0-1.fc23.x86_64 ibus-wayland-1.5.11-1.fc23.x86_64 libwayland-server-1.9.0-1.fc23.i686 mesa-libwayland-egl-11.0.3-1.20151012.fc23.i686 mesa-libwayland-egl-devel-11.0.3-1.20151012.fc23.x86_64 mesa-libwayland-egl-11.0.3-1.20151012.fc23.x86_64 libwayland-cursor-1.9.0-1.fc23.i686 How reproducible: Always (under gnome wayland session) Steps to Reproduce: 1. Start Gnome under Wayland 2. Start Firefox 3. Press F11 Actual results: Session lockup. Expected results: Either a) fullscreen responsive window, as in X11, or b) failure to do anything, with session still responsive. Additional info: 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. Device 0ded Flags: bus master, fast devsel, latency 0, IRQ 27 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 fdb00000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Kernel driver in use: i915 Kernel modules: i915 I have not tried checking network responsiveness.
Looks more like Gtk3 bug.
I have also reproduced the lockup when pressing F11 on dia, which is, as far as I know, an X11 application that uses GTK2. Therefore, I think this is more of an Xwayland issue.
Still happening on Fedora 24 with: firefox-48.0.1-1.fc24.i686 gnome-shell-3.20.4-1.fc24.i686 mutter-3.20.3-1.fc24.i686 xorg-x11-server-Xwayland-1.18.4-1.fc24.i686 gtk3-3.20.9-1.fc24.i686 I can ssh into the machine during the lockup, and apparently gnome-shell and firefox are both spinning.
Still happening on Fedora 25 with: firefox-50.0-1.fc25.i686 gnome-shell-3.22.1-2.fc25.i686 mutter-3.22.1-8.fc25.i686 xorg-x11-server-Xwayland-1.19.0-0.8.rc2.fc25.i686 gtk3-3.22.2-2.fc25.i686 During the lockup, an attempt to switch to another virtual console with Ctrl-Alt-F3 and back ended up crashing Xwayland and gnome-shell.
Another crash. I found this in the system log from journalctl -b. The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1929 error_code 11 request_code 12 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Still happening. I have seen that this crash is dependent on the Wayland display size. By changing the screen resolution I have seen that at up to 1024x768 Firefox correctly goes fullscreen without crashes, at 1152x864 it goes a little sluggish, and it crashes at 1280x960 and upwards.
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.
Still happening under Fedora 27 with: firefox-57.0-2.fc27.x86_64 gnome-shell-3.26.2-1.fc27.x86_64 mutter-3.26.2-1.fc27.x86_64 xorg-x11-server-Xwayland-1.19.5-1.fc27.x86_64 gtk3-3.22.26-1.fc27.x86_64
Still happening under Fedora 27 with: firefox-57.0.1-1.fc27.x86_64 gnome-shell-3.26.2-2.fc27.x86_64 mutter-3.26.2-2.fc27.x86_64 xorg-x11-server-Xwayland-1.19.5-1.fc27.x86_64 gtk3-3.22.26-1.fc27.x86_64 Current reproducer: Have a monitor of 1440x900 or higher. Open any site A in firefox. Press F11 to bring firefox to fullscreen. Might crash on animation here. Move the mouse cursor to make the tab appear, then create a new tab. Open any site B in newly created tab. Move mouse to inside the page so that bar of tabs is dismissed and tab containing site B animates back into fullscreen.
This seems highly likely to be related to the graphics card/driver, to me. If this actually affected *any* case of running Firefox in full screen mode at moderate resolution on Wayland, we'd have thousands of reports (and it'd be broken for me, which it isn't; I just sat around using fullscreen Firefox on Wayland at 1080x1920 for ten minutes and it worked fine). Re-assigning to the Intel driver package so this gets to the Intel driver maintainers. They're likely to need rather more data to debug this, though. Can you at least boot with 'drm.debug=15' kernel parameter, reproduce the bug, and then attach the entire contents of the journal for that boot? Thanks.
Ok, I will do that as soon as possible. However, I have tried doing fullscreen with firefox using weston instead of gnome-shell, and there is no crash anywhere in that scenario, so I doubt this is purely a graphics card issue. At the very least gnome-shell is also required in addition to the (somewhat old) graphics chipset.
Yeah, issues like this often lie at a sort of intersection of the hardware and the various bits of the software stack. We can always move the assignment around as more info becomes available...
Created attachment 1370958 [details] journalctl with drm.debug=15 This is the journalctl output with a boot that has drm.debug=15 in the kernel command line and that contains the crash.
Thanks a lot! It's hard for a non-expert to read, but it does sort of look like perhaps the driver is stuck in some sort of loop before the crash. But let's leave it to the experts :) Adam, does this log help figure out what's happening to Alex, or do we need some different data from him? Thanks!
This is still happening under Fedora 28 on all of my i915 machines. I have opened a bug report upstream: https://gitlab.gnome.org/GNOME/mutter/issues/260
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Still happening with Fedora 30 (x86_64 live image). I have noticed that Firefox running in Wayland mode does *not* trigger the crash on fullscreen. This is only happening with Firefox on the default X11 mode, and only under the i915 (NOT i965) driver when using Gnome Shell as as Wayland compositor.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'. 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 30 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.
Fixed already in Fedora 32.