From Fedora Project Wiki
m
m
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{admon/important | 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.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
+
= Wayland By Default in KDE =
 
 
<!-- Self Contained or System Wide Change Proposal?
 
Use this guide to determine to which category your proposed change belongs to.
 
 
 
Self Contained Changes are:
 
* changes to isolated/leaf package without the impact on other packages/rest of the distribution
 
* limited scope changes without the impact on other packages/rest of the distribution
 
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
 
 
 
System Wide Changes are:
 
* changes that does not fit Self Contained Changes category touching
 
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
 
* changing system defaults
 
 
 
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
 
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). 
 
 
 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
 
-->
 
 
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
 
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
= Wayland By Default in KDE <!-- The name of your change proposal --> =
 
  
 
== Summary ==
 
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
+
Change the default session selection in SDDM to prefer the Wayland-based Plasma session over the X11-based one.
  
 
== Owner ==
 
== Owner ==
Line 97: Line 73:
 
# Choose 'Plasma' session (X11 based one)
 
# Choose 'Plasma' session (X11 based one)
 
# Verify that X11 session is still working for those who don't want to use or can't use Wayland session
 
# Verify that X11 session is still working for those who don't want to use or can't use Wayland session
 +
 +
== Known issues ==
 +
* https://community.kde.org/Plasma/Wayland_Showstoppers
 +
* https://community.kde.org/Plasma/5.12_Errata#Wayland
  
 
== User Experience ==
 
== User Experience ==

Latest revision as of 16:31, 15 January 2018

Wayland By Default in KDE

Summary

Change the default session selection in SDDM to prefer the Wayland-based Plasma session over the X11-based one.

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

Known issues

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: qt5-qtbase, qt5-qtwayland, plasma-workspace, kwin, kf5-kwayland, sddm.

Contingency Plan

  • Contingency mechanism: Change back that 'Plasma' session will be used by default instead of 'Plasma (Wayland)' and offer 'Plasma (Wayland)' session on the spin as a secondary option.
  • Contingency deadline: beta
  • Blocks release? no
  • Blocks product? no

Documentation

N/A (not a System Wide Change)

Release Notes