We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
In KDE Plasma's System Settings, in the Keyboard section, there is an option to automatically enable NumLock when opening a desktop session.
For some reason, this doesn't work on Solus. No matter what is selected, NumLock will stay off and you need to enable it manually.
I tried both the X11 and the Wayland sessions and it fails in both.
This isn't an upstream KDE bug because it works on every other distribution I have tried with the same Plasma release (6.2.5).
NumLock should be enabled.
NumLock is disabled.
Shannon (stable)
Plasma
Solus 4.6 KDE Plasma 6.2.5 KDE Frameworks 6.10.0 Qt 6.8.1 Linux 6.12.9-312.current (64-bit)
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Please confirm there isn't an open report for this issue
Summary
Hello,
In KDE Plasma's System Settings, in the Keyboard section, there is an option to automatically enable NumLock when opening a desktop session.
For some reason, this doesn't work on Solus. No matter what is selected, NumLock will stay off and you need to enable it manually.
I tried both the X11 and the Wayland sessions and it fails in both.
This isn't an upstream KDE bug because it works on every other distribution I have tried with the same Plasma release (6.2.5).
Steps to reproduce
Expected result
NumLock should be enabled.
Actual result
NumLock is disabled.
Environment
Repo
Shannon (stable)
Desktop Environment
Plasma
System details
Solus 4.6
KDE Plasma 6.2.5
KDE Frameworks 6.10.0
Qt 6.8.1
Linux 6.12.9-312.current (64-bit)
Other comments
No response
The text was updated successfully, but these errors were encountered: