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
- Email: firstname.lastname@example.org email@example.com
- Release notes owner:
- Product: Workstation
- Responsible WG: Workstation
- Targeted release: Fedora 23
- Last updated: 2015-03-25
- Tracker bug: <will be assigned by the Wrangler>
We will change the default session in the gdm session selector to be the Wayland session, if both are available. If a user makes an explicit choice, we will still remember it and keep using the same session the next time he logs in.
Benefit to Fedora
Using Wayland instead of X gives a much better basis for isolating applications from each other and the system.
- Proposal owners:
- Rename the gnome-wayland.session file to gnome.session and the current gnome.session file to gnome-x.session. At the same time, change the display names around to be just 'GNOME' for the default, and 'GNOME on X11' for the X11-based session.
- 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)
- Close all remaining feature parity gaps between the Wayland and the X11 session:
- input methods
- on-screen keyboard
- hi-dpi support
- clipboard proxy for xwayland
- attached modal dialogs
- tablet support
- startup notification
- touch proxy for xwayland
- accessibility features
- output rotation
- Other developers:
- GTK+ applications that use X11-specific APIs need to be patched to explicitly use the GDK X backend
- xwayland needs to prevent access from outside the session
- 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 F23 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: Revert the changes to the session files, thereby keeping the X-based session as the default
- Contingency deadline: beta
- Blocks release? no
- Blocks product? no