https://bugs.kde.org/show_bug.cgi?id=421486
Bug ID: 421486
Summary: No input in nested session
Product: kwin
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: libinput
Assignee: kwin-bugs-n...@kde.org
Reporter: butir...@gmail.com
CC: aspotas...@gmail.com, bugsefor...@gmx.com,
butir...@gmail.com, kwin-bugs-n...@kde.org
Depends on: 412101
Target Milestone: ---
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
Referenced Bugs:
https://bugs.kde.org/show_bug.cgi?id=412101
[Bug 412101] Wayland session does not remember the last used keyboard layout.
The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is
always used after login instead.
--
You are receiving this mail because:
You are watching all bug changes.
