After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 442068 - numlock key bug on non ascii char
numlock key bug on non ascii char
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
2.18.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-29 13:53 UTC by Sebastien Bacher
Modified: 2008-02-27 21:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Sebastien Bacher 2007-05-29 13:53:01 UTC 
The bug has been described on https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/110567

"Binary package hint: gnome-panel

Une erreur est survenue lors du chargement ou de l'enregistrement des informations de configuration de gnome-settings-daemon. Certains de vos paramètres de configuration ne fonctionneront peut-être pas correctement.

Nom de clé ou de répertoire incorrect: « /desktop/gnome/peripherals/keyboard/host-çIkoLAta-laptop/0/numlock_on » : « ? » n'est pas un caractère ASCII, aussi il n'est pas autorisé dans un nom de clé
Nom de clé ou de répertoire incorrect: « /desktop/gnome/peripherals/keyboard/host-çIkoLAta-laptop/0/numlock_on » : « ? » n'est pas un caractère ASCII, aussi il n'est pas autorisé dans un nom de clé
...
 /desktop/gnome/peripherals/keyboard/host-cIkoLAta-laptop:
  /desktop/gnome/peripherals/keyboard/host-cIkoLAta-laptop/0:
   numlock_on = false"
Comment 1 Jens Granseuer 2007-05-29 19:42:02 UTC 
RFC 1034 (http://www.ietf.org/rfc/rfc1034.txt) says:

"For example, when naming a mail domain, the user should satisfy both the
rules of this memo and those in RFC-822.  When creating a new host name,
the old rules for HOSTS.TXT should be followed.  This avoids problems
when old software is converted to use domain names.

The following syntax will result in fewer problems with many
applications that use domain names (e.g., mail, TELNET).

<domain> ::= <subdomain> | " "

<subdomain> ::= <label> | <subdomain> "." <label>

<label> ::= <letter> [ [ <ldh-str> ] <let-dig> ]

<ldh-str> ::= <let-dig-hyp> | <let-dig-hyp> <ldh-str>

<let-dig-hyp> ::= <let-dig> | "-"

<let-dig> ::= <letter> | <digit>

<letter> ::= any one of the 52 alphabetic characters A through Z in
upper case and a through z in lower case

<digit> ::= any one of the ten digits 0 through 9"


Note the absence of fancy characters. In any case, is there a reliable way to determine the encoding used for a hostname? Without one, we won't have a way to convert to valid ASCII anyway.
Comment 2 Jens Granseuer 2008-02-27 21:43:52 UTC 
I believe this is fixed in svn now.