** Changed in: control-center (Ubuntu)
Status: Needs Info => Rejected
** Changed in: Baltix
Status: Unconfirmed => Rejected
** Changed in: control-center (upstream)
Status: Unconfirmed => Rejected
--
'localhost' hostname breaks numlock state saving
https://launchpad.net/bug
That bug is confusing, could you describe what version of Ubuntu you are
using, what you do, what happens and what you would expect? I don't
consider the numlock state being wrong after a hostname change as a bug.
People don't change hostname usually, and if they don't it's not a
problem to change
Since I need to add (127.0.0.1 loclahost) in /etc/hostname on Edgy Eft
AMD64, to inprove network speed with my router, it's look like the same
erreur appear :
Nom de clé ou de répertoire incorrect: «
/desktop/gnome/peripherals/keyboard/host-127.0.0.1 [HOTNAME]
localhost/0/numlock_on » : « » est
** Also affects: control-center (upstream)
Importance: Undecided
Status: Unconfirmed
--
'localhost' hostname breaks numlock state saving
https://launchpad.net/bugs/46959
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Also affects: Baltix
Importance: Undecided
Status: Unconfirmed
--
'localhost' hostname breaks numlock state saving
https://launchpad.net/bugs/46959
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
That feature comes from gnome-control-center, reassigning
** Changed in: gconf (Ubuntu)
Sourcepackagename: gconf => control-center
Importance: Medium => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs
--
'localhost' hostname breaks numlock state saving
https://launchpad.net/bugs/46959
