From Fedora Project Wiki
m
m
Line 102: Line 102:
  
 
== Dependencies ==
 
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
+
The tasks lists in the Scope section are spread across a number of upstream modules and packages: plasma-workspace, kwin, kf5-kwayland, sddm.
 
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
N/A (not a System Wide Change)
 
  
 
== Contingency Plan ==
 
== Contingency Plan ==

Revision as of 07:21, 15 January 2018

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.


Wayland By Default in KDE

Summary

Owner

  • Name: Jan Grulich
  • Email: <jgrulich@redhat.com>
  • Release notes owner:

Current status

  • Targeted release: Fedora 28
  • Last updated: 2018-01-15
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

We will change SDDM to use wayland by default for Plasma. We will also attempt to automatically fall back to Xorg in cases where wayland is unavailable (like nvidia). There will still be option to use Plasma session on Xorg to those who don't want to switch to Wayland yet.

Benefit to Fedora

Using Wayland instead of X gives much better basis for isolating applications from each other and the system.

Scope

  • Proposal owners:
    • Make SDDM to use wayland session as default.
    • Make sure that wayland session is working as good as X11 session and there is no big feature gap for regular user usage.
  • Other developers:
    • Qt applications that rely on X11-specific API need to be patched to work under Wayland.
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

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 SDDM 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

  1. Boot a fresh F28 KDE Spin install.
  2. Verify that the session chooser offers 'Plasma', 'Plasma (Wayland)', and that 'Plasma (Wayland)' is selected by default.
  3. Log into 'Plasma (Wayland) and verify that it gives you Wayland (you can verify this by opening any KDE app and going to Help → About "app" and checking that it says "Wayland windowing system").
  1. Log into the Wayland-based session again
  2. Use the desktop normally, and verify that there are no obvious instabilities, or Wayland-specific bugs or performance problems
  1. Choose 'Plasma' session (X11 based one)
  2. Verify that X11 session is still working for those who don't want to use or can't use Wayland session

User Experience

The user experience of the Wayland session is identical to that of the X session.

Dependencies

The tasks lists in the Scope section are spread across a number of upstream modules and packages: plasma-workspace, kwin, kf5-kwayland, sddm.

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes