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 628797 - seahorse can't read and remove Password Keyring which name is entered in Cyrillics
seahorse can't read and remove Password Keyring which name is entered in Cyri...
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: general
2.30.x
Other Linux
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2010-09-04 22:00 UTC by Vincent Untz
Modified: 2010-09-05 13:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Untz 2010-09-04 22:00:01 UTC
Forwarding https://bugzilla.novell.com/show_bug.cgi?id=635743:

With LANG=ru_RU.UTF-8:
At creation Password Keyring with a name "Основная" there is an error:
(seahorse:9152): Gtk-WARNING **: Failed to set text from markup due to error
parsing markup: Ошибка в строке 1 на символе 142: Недопустимый UTF-8 текст в
имени — неправильная последовательность «
\xffffffd0\xffffffbe\xffffffd1\xffffff81\xffffffd0\xffffffbd\xffffffd0\xffffffbe\xffffffd0\xffffffb2\xffffffd0\xffffffbd\xffffffd0\xffffffbe\xffffffd0\xffffffb9»
...

Or with LANG=en_US.UTF-8
(seahorse:9126): Gtk-WARNING **: Failed to set text from markup due to error
parsing markup: Error on line 1 char 139: Invalid UTF-8 encoded text in name -
not valid '
\xffffffd0\xffffffbe\xffffffd1\xffffff81\xffffffd0\xffffffbd\xffffffd0\xffffffbe\xffffffd0\xffffffb2\xffffffd0\xffffffbd\xffffffd0\xffffffbe\xffffffd0\xffffffb9'

Reproducible: Always

Steps to Reproduce:
1.Run LANG=ru_RU.UTF-8 seahorse
2.Create Password Keyring with name: Основная
Actual Results:  
1. seahorse can't read and remove Password Keyring which name: Основная
2. Error: (seahorse:9152): Gtk-WARNING **: Failed to set text from markup due
to error parsing markup: ...

Expected Results:  
1. Read and remove Password Keyring which name: Основная
2. No errors

locale
LANG=ru_RU.UTF-8
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES="ru_RU.UTF-8"
LC_PAPER="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_MEASUREMENT="ru_RU.UTF-8"
LC_IDENTIFICATION="ru_RU.UTF-8"
LC_ALL=
Comment 1 Stef Walter 2010-09-05 01:08:53 UTC
Which version are you running exactly?

I thought this was fixed by this libgnome-keyring commit:


commit ad6da9a5377d98a7af0f543e0745a83735df4bcd
Author: Pablo Castellano <pablog@src.gnome.org>
Date:   Tue Jul 27 17:30:54 2010 +0200

    [dbus] Fix encoding problems with keyring names and foreign characters.
    
     * Creating keyrings with a label that contained non-ascii charaters
       was broken.


And this gnome-keyring commit:


commit ad6da9a5377d98a7af0f543e0745a83735df4bcd
Author: Pablo Castellano <pablog@src.gnome.org>
Date:   Tue Jul 27 17:30:54 2010 +0200

    [dbus] Fix encoding problems with keyring names and foreign characters.
    
     * Creating keyrings with a label that contained non-ascii charaters
       was broken.
Comment 2 Vincent Untz 2010-09-05 13:46:10 UTC
Ah, I was looking at the git history of seahorse. This is in GNOME 2.30.1, so those commits were definitely not there. I guess I should just backport them.