Bug 356851 - System keyboard layout ctrl capslock requires re-apply after log out
Summary: System keyboard layout ctrl capslock requires re-apply after log out
Status: REPORTED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard (show other bugs)
Version: 5.5.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Andriy Rysin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-17 20:23 UTC by Tory Anderson
Modified: 2021-03-09 07:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tory Anderson 2015-12-17 20:23:55 UTC
Using an external keyboard on my laptop, Configure Desktop -> Hardware -> Input Devices -> Keyboard -> Advanced -> Caps Lock key behavior -> Make Caps Lock an additional CTRL is enabled. The setting is remembered insomuch as it retains the check mark from log-in to log-in, but each log-in it will not, in actuality, be working until I uncheck, check, "Apply". Also needs to be applied again whenever the system has returned to log-in screen due to inactivity. 

Possibly related to bug 353413, which deals with remembering settings and fixing by re-applying.

Reproducible: Always

Steps to Reproduce:
1. plug in external keyboard
2. Check Keyboard -> Advanced -> Caps Lock key behavior -> Make Caps Lock an additional CTRL, apply
3. Log out, log back in

Actual Results:  
Keyboard -> Advanced -> Caps Lock key behavior -> Make Caps Lock an additional CTRL will show as selected, but behavior does not agree. 

Expected Results:  
Capslock should remain an additional ctrl.
Comment 1 Stephan Diestelhorst 2016-02-26 13:51:50 UTC
I have a similar problem and investigated it here: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1545293

Also, bug 355354 might be related.
Comment 2 Justin Zobel 2021-03-09 07:29:37 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.