| Summary: | No input in nested session | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Andrey <butirsky> |
| Component: | libinput | Assignee: | Andrey <butirsky> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | aleixpol, aspotashev, bugseforuns, butirsky, kwin-bugs-null, nate |
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| URL: | https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/117 | ||
| Latest Commit: | Version Fixed In: | ||
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". |
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