[Bug 46959] Re: Changing hostname breaks numlock state saving

[fubarbundy]

As per the original implementation of numlock saving, I have discovered
that the numlock state is not remembered if the machine's hostname is
'localhost' (http://bugzilla.gnome.org/show_bug.cgi?id=74215#c38).

I'm changing the bug title to reflect this; either there should be a
note on the gconf key in gconf-editor to tell the user this, or numlock
should be remembered even with a 'localhost' hostname. Otherwise, how is
a normal user supposed to know why it doesn't work?

** Summary changed:

- Changing hostname breaks numlock state saving
+ 'localhost' hostname breaks numlock state saving

-- 
'localhost' hostname breaks numlock state saving
https://launchpad.net/bugs/46959