** Changed in: control-center (Ubuntu)
Status: Needs Info = Rejected
--
NumLock, ScrollLock and CapsLock status isn't saved
https://bugs.launchpad.net/bugs/77593
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
It isn't really an issue anymore. After several restarts NumLock is
still on. Unless someone else is experiencing this problem, this bug can
be rejected.
--
NumLock, ScrollLock and CapsLock status isn't saved
https://bugs.launchpad.net/bugs/77593
You received this bug notification because you
At my computer is the exact path
/desktop/gnome/peripherals/keyboard/host-hostname/0/numlock_on and numlock_on
is on.
And I discover while writing this that NumLock is on, which it isn't always. If
I select numlock_on gconf-editor is showing an error message wich says: 'This
key has no
The no scheme message is normal, the key is written by gnome-settings-
daemon. Could you look at the value of the gconf key where you don't get
numlock? It's supposed to restore the state which was used during the
previous session, are you sure you didn't stop numlock?
--
NumLock, ScrollLock and
After a restart NumLock was still on. numlcok_on and remeber_numlock_state are
selected.
I think it isn't a bug (anymore), maybe it's added in GNOME 2.18
What do you mean with the value of the gconf key where I don't get numlock?
--
NumLock, ScrollLock and CapsLock status isn't saved
** Changed in: control-center (Ubuntu)
Sourcepackagename: None = control-center
--
NumLock, ScrollLock and CapsLock status isn't saved
https://bugs.launchpad.net/bugs/77593
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
The numlock value is stored to /desktop/gnome/peripherals/keyboard/host-
hostname/numlock_on, is the key updated correctly when you restart?
** Changed in: control-center (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Unconfirmed = Needs
