https://bugs.kde.org/show_bug.cgi?id=368063
Christian Hartmann <hartmann.christ...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hartmann.christ...@gmail.co
| |m
--- Comment #57 from Christian Hartmann <hartmann.christ...@gmail.com> ---
just to reensure, that the daemon not started is the issue here.
this numlock issue drove me nuts since three month or so.
other isssue: i've disabled key repeating on longer press and this
also didn't work as exspected. since i've started the daemon
manualy also this feature is going ..
i'm quite confident in saying: i've never ever changed the behavior
of this autostart setting. i've actualy didn't know about this one
to the day.
(running neon)
closing words:
i do not feel very comfortabel with a setting, where 0 (zero) is
for *en*abling something. same with "do not change setting"
just deletes the whole NumLock line in kcminputrc. if one never
touched the setting, no line in the rc file feels right, but the
moment, the user *does* set the behavior this explicit setting
should reflect in a file. just my 2ct, sorry
--
You are receiving this mail because:
You are watching all bug changes.
