Bug 503011 - Modifying keyboard layout does not persist over reboot
Summary: Modifying keyboard layout does not persist over reboot
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard (other bugs)
Version First Reported In: 6.1.5
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-19 12:00 UTC by Nik Clayton
Modified: 2025-05-31 03:47 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nik Clayton 2025-04-19 12:00:29 UTC
SUMMARY

The keyboard layout is not restored after setting it and logging out / rebooting. After logging in it is reset to "us", and the keyboard layout I added is not in the list.

STEPS TO REPRODUCE
1. Login
2. Open the "Keyboard" system settings UI
3. Click the "Layouts" tab
4. Observe one layout is present, "us".
5. Add a new layout, "gb".
6. Remove the "us" layout.
7. Click "Apply".
8. Close the system settings UI.
9. Open Kate, and type to verify the layout is correct (e.g., £ works, # is mapped to the correct key, etc).
10. Logout / restart the computer
11. Repeat steps 1-3

OBSERVED RESULT

One layout is present, "us".

EXPECTED RESULT

One layout is present, "gb".

Existing bugs for this (e.g., 41201) seem to be about when multiple keyboard layouts are present, or when using remote-desktop clients to connect. Neither of those are the case here.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
Kernel Version: 6.11.0-24-generic (64-bit)
Graphics Platform: Wayland
Processors: 24 × 13th Gen Intel® Core™ i7-13700K
Memory: 62.5 GiB of RAM
Graphics Processor: NV134
Comment 1 John Kizer 2025-04-21 17:23:45 UTC
Hi - does your Kubuntu install also have fcitx installed, by chance?

(Looking at https://bugs.kde.org/show_bug.cgi?id=494643 , for future reference)
Comment 2 Nik Clayton 2025-04-22 10:12:09 UTC
(In reply to John Kizer from comment #1)
> Hi - does your Kubuntu install also have fcitx installed, by chance?
> 
> (Looking at https://bugs.kde.org/show_bug.cgi?id=494643 , for future
> reference)

Not that I'm aware of.

```shell
% fcitx
Command 'fcitx' not found, but can be installed with:
sudo apt install fcitx-bin
```

This is a very stock install of 24.10 downloaded and installed in March of this year.
Comment 3 duha.bugs 2025-04-29 20:34:31 UTC
The package would likely be called fcitx5. Can you check if you have that installed?
Comment 4 John Kizer 2025-04-30 18:26:58 UTC
Pending check from the reporter on package status
Comment 5 Nik Clayton 2025-05-01 09:06:58 UTC
There are some packages with that in the name, but no single "fcitx5" package.

```shell
% apt list --installed | grep fcitx5

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

fcitx5-chinese-addons-bin/oracular,now 5.1.6-2 amd64 [installed,automatic]
fcitx5-chinese-addons-data/oracular,oracular,now 5.1.6-2 all [installed,automatic]
fcitx5-chinese-addons/oracular,oracular,now 5.1.6-2 all [installed]
fcitx5-config-qt/oracular,now 5.1.6-1 amd64 [installed,automatic]
fcitx5-data/oracular,oracular,now 5.1.10-1 all [installed,automatic]
fcitx5-frontend-all/oracular,oracular,now 5.1.10-1 all [installed]
fcitx5-frontend-gtk3/oracular,now 5.1.3-1 amd64 [installed,automatic]
fcitx5-frontend-gtk4/oracular,now 5.1.3-1 amd64 [installed,automatic]
fcitx5-frontend-qt5/oracular,now 5.1.6-1ubuntu1 amd64 [installed,automatic]
fcitx5-frontend-qt6/oracular,now 5.1.6-1ubuntu1 amd64 [installed,automatic]
fcitx5-material-color/oracular,oracular,now 0.2.1-1 all [installed]
fcitx5-module-chttrans/oracular,now 5.1.6-2 amd64 [installed,automatic]
fcitx5-module-cloudpinyin/oracular,now 5.1.6-2 amd64 [installed,automatic]
fcitx5-module-fullwidth/oracular,now 5.1.6-2 amd64 [installed,automatic]
fcitx5-module-lua-common/oracular,oracular,now 5.0.13-1 all [installed,automatic]
fcitx5-module-lua/oracular,now 5.0.13-1 amd64 [installed,automatic]
fcitx5-module-pinyinhelper/oracular,now 5.1.6-2 amd64 [installed,automatic]
fcitx5-module-punctuation/oracular,now 5.1.6-2 amd64 [installed,automatic]
fcitx5-modules/oracular,now 5.1.10-1 amd64 [installed,automatic]
fcitx5-pinyin-gui/oracular,now 5.1.6-2 amd64 [installed,automatic]
fcitx5-pinyin/oracular,now 5.1.6-2 amd64 [installed,automatic]
fcitx5-table/oracular,now 5.1.6-2 amd64 [installed,automatic]
fcitx5/oracular,now 5.1.10-1 amd64 [installed,automatic]
kde-config-fcitx5/oracular,now 5.1.6-1 amd64 [installed]
libfcitx5-qt-data/oracular,oracular,now 5.1.6-1ubuntu1 all [installed,automatic]
libfcitx5-qt1/oracular,now 5.1.6-1ubuntu1 amd64 [installed,automatic]
libfcitx5-qt6-1/oracular,now 5.1.6-1ubuntu1 amd64 [installed,automatic]
libfcitx5config6/oracular,now 5.1.10-1 amd64 [installed,automatic]
libfcitx5core7/oracular,now 5.1.10-1 amd64 [installed,automatic]
libfcitx5gclient2/oracular,now 5.1.3-1 amd64 [installed,automatic]
libfcitx5utils2/oracular,now 5.1.10-1 amd64 [installed,automatic]
```
Comment 6 John Kizer 2025-05-01 18:04:48 UTC
Thanks - the comment here at https://bugs.kde.org/show_bug.cgi?id=494643#c1 would indicate that those components might be overwriting the configuration you're trying to apply in the KDE System Settings application.

Are you able to test out uninstalling those fcitx5 packages, and then seeing if this issue still occurs?
Comment 7 Bug Janitor Service 2025-05-16 03:46:54 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2025-05-31 03:47:50 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.