Bug 421486 - No input in nested session
Summary: No input in nested session
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: libinput (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR major
Target Milestone: ---
Assignee: Andrey
URL: https://invent.kde.org/plasma/plasma-...
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-13 22:16 UTC by Andrey
Modified: 2020-07-14 17:02 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey 2020-05-13 22:16:40 UTC 
SUMMARY
When run nested on Wayland, startplasma-wayland starts session with no input.

This is due it tries to always use libinput by default, which is inappropriate for nested session.
Seems internally it passes the option to kwin:
  --libinput                              Enable libinput support for input
                                          events processing. Note: never use in
                                          a nested session.
 

STEPS TO REPRODUCE
1. run startplasma-wayland in Wayland session

OBSERVED RESULT
no input in the launched session

EXPECTED RESULT
session launch and reacts on input

WORKAROUND
pass any non-destructive option to startplasma-wayland, other than --libinput.
Example:
> startplasma-wayland --exit-with-session=/usr/libexec/startplasma-waylandsession
Comment 1 Andrey 2020-06-25 21:04:55 UTC 
The problem seems here:
https://invent.kde.org/plasma/plasma-workspace/-/blob/master/startkde/startplasma-wayland.cpp#L93

> args = QStringList { QStringLiteral("--xwayland"), QStringLiteral("--libinput"), ...

Probably we need to test if we are nested or not before passing "--libinput".