Wayland By Default
Change the default session selection in gdm to prefer the Wayland-based GNOME session over the X11-based one.
- Name: Matthias Clasen Ray Strode Jonas Ådahl Olivier Fourdan Marek Chalupa
- Email: email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com
- Release notes owner:
- Product: Workstation
- Responsible WG: Workstation
- Targeted release: Fedora 25
- Last updated: 2016-08-23
- Tracker bug: 1277927
We will change GDM to use wayland by default for GNOME. The code will automatically fall back to Xorg in cases where wayland is unavailable (like nvidia). Users will be able to disable wayland by setting WaylandEnable=false in /etc/gdm/custom.conf but there will no longer be two separate menu items for GNOME on Wayland and GNOME on X11.
Benefit to Fedora
Using Wayland instead of X gives a much better basis for isolating applications from each other and the system.
- Proposal owners:
- merge the gnome-wayland.desktop and gnome.desktop into one file that is distributed into both /usr/share/wayland-sessions and /usr/share/xsessions. since they have same filename, the wayland one will "win". - DONE
- Make gdm hide Wayland sessions from the session chooser if we know they will not work (because the login screen had to fall back to X) - DONE
- Close remaining feature parity gaps between the Wayland and the X11 session:
- See the Wayland features page for a complete list of features.
- game support (needs pointer locking api)
- details panel in control center needs to show hardware graphics device
- input methods - DONE
- on-screen keyboard - DONE
- hi-dpi support - DONE
- tablet support
- startup notification - DONE
- touch proxy for xwayland - DONE
- accessibility features - Screen reader and visual bell are DONE
- output rotation / randr like features
- triple-monitor setups
- primary selection - DONE (discussion)
- dnd actions and cancellation - DONE
- extra mouse buttons
- Other developers:
- GTK+ applications that use X11-specific APIs need to be patched to explicitly use the GDK X backend
- Popup and dialog placement issues in applications
- Release engineering: No release engineering changes needed
- Policies and guidelines: No policy or guideline changes needed
Systems using certain graphics hw or graphics drivers (matrox, qxl) may have problems running the Wayland session. In these (rare) cases, users may have to configure gdm to use X11 (although automatic fallback should work most of the time). If we don't manage to close all the feature parity gaps entirely, then users relying on those features may have to choose the X11-based session.
How To Test
- Boot a fresh F25 workstation install.
- Verify that the login screen is running under Wayland (you can do so by looking for a process called gdm-wayland-session in ps -ef output)
- Verify that the session chooser offers 'GNOME', 'GNOME on X11' and 'GNOME Classic', and that 'GNOME' is selected by default.
- Log into all three of these sessions and verify that 'GNOME' gives you Wayland (you can verify this by bringing up the GTK+ inspector in a gtk3 application and checking what backend is used), while the other two end up with X11.
- Change the gdm configuration by adding WaylandEnable=false and reboot
- Verify that the login screen comes up under X
- Verify that only X-based sessions are offered in the session chooser
- Log into the Wayland-based session again
- Use the desktop normally, and verify that there are no obvious instabilities, or Wayland-specific bugs or performance problems
The user experience of the Wayland session is identical to that of the X session.
The tasks lists in the Scope section are spread across a number of upstream modules and packages: gtk3, gnome-shell, mutter, libinput, Xorg, gdm.
- Contingency mechanism: Rename /usr/share/wayland-sessions/gnome.desktop to /usr/share/wayland-sessions/gnome-wayland.desktop so it doesn't preempt the X11 session file anymore, thereby keeping the X-based session as the default and adding wayland back to the list.
- Contingency deadline: beta
- Blocks release? no
- Blocks product? no