linuxmint / linuxmint/cinnamon
Keyboard settings (key repetition speed) are not remembered
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 915
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 3
Description
Distribution
Arch
Package version
6.0.4
Graphics hardware in use
GTX 1660 Ti
Frequency
Always
Bug description
Settings --> Keyboard remembers key repetition and repetition speed only until the first reboot
Steps to reproduce
- Open Settings --> Keyboard.
- Set the two "repeat" & "delay" sliders to whatever lengths you want. Test them and remember the speed.
- Reboot the computer then open anything with a text box, press and hold any letter key. Observe that "repeat" & "delay" are much slower than what you have set. It's like they've gone back to some kind of default values.
Expected behavior
When the "repeat" & "delay" sliders are pulled to whatever desired values, they should be remembered even after computer reboot.
Additional information
There's a workaround to that problem. Open Keyboard settings and move the "repeat delay" slider one step to the left or to the right and then return it back to the desired position. That restores the user values.
I tried saving the values in dconf-editor and restoring them with the dump command but that doesn't seem to help. Only manually moving the slider fixes the bug.
In case it matters:
GPU Driver - 550.67, kernel 6.6.28-2-LTS.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in Settings → Keyboard and reproduce the problem by changing the repeat and delay sliders, rebooting, and checking a text box. Trace how these values are saved and restored, using the reported dconf behavior as context. Done means the selected repeat and delay values remain effective after reboot, with regression coverage if the relevant test area is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100