Summary: | Autostart script with custom XKB layout is erased when logging in | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Joel <joel.porquet> |
Component: | kcm_autostart | Assignee: | Andriy Rysin <arysin> |
Status: | RESOLVED NOT A BUG | ||
Severity: | major | CC: | kde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Joel
2015-11-19 20:58:22 UTC
I forgot to add in the bug description that my custom xkb layout is installed through an autostart script. I played a bit more with it and found that the script is executed but is quickly overridden when Plasma starts. Basically, I created a script that performs the xkb modification and also touches a file in my home. After logging into Plasma, the file is created in my home but the xkb modification is not effective. If I relaunch the script by itself, I get my custom xkb layout. My guess is that my custom layout run by the autostart script is quickly erased by a another layout configuration from Plasma. >My guess is that my custom layout run by the autostart script is quickly erased by a another layout configuration from Plasma.
Correct. A background daemon that makes the UI follow the user's settings.
We can't simultaneously have tools that set keyboard layouts for users and sometimes not set the keyboard layout.
You should be able to disable the keyboard layout daemon with
system settings -> startup and shutdown -> background services -> keyboard.
|