Seahorse shows keyring with no name

Bug #570345 reported by Pierre Faivre
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: seahorse

Hello
I have Ubuntu 10.04 and in seahorse, i have one item with no name for each time system tried to create a password in defaut keyring.
I cannnot delete this keyrings and cannot change passsword

When I launch seahorse in terminal I have the following message for each item :

(seahorse:3247): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Erreur à la ligne 1, caractère 58 : Texte codé en UTF-8 non valide dans le nom - «  par_d\xffffffc3\xffffffa9faut » est non valide

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: seahorse 2.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Apr 26 20:32:28 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SourcePackage: seahorse

Tags: ops+
Revision history for this message
Pierre Faivre (pierrefaivre2002) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, seems similar to the issue on bug #553759, could you run grep -r /usr/share/locale-* par_défault and list results in a comment?

Revision history for this message
Pierre Faivre (pierrefaivre2002) wrote :

here's the result :
grep: par_défault: Aucun fichier ou dossier de ce type

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you run grep -r par_défault /usr/share/locale-* rather?

Revision history for this message
Sebastien Bacher (seb128) wrote :

or locale without the - too

Revision history for this message
Pierre Faivre (pierrefaivre2002) wrote :

here's is the result :

Fichier binaire /usr/share/locale-langpack/fr/LC_MESSAGES/psql-8.4.mo concordant

Revision history for this message
Sebastien Bacher (seb128) wrote :

it seems to be an ubuntuone-client, it happens when it does create the keyring, if the keyring is created by an another software it works correctly

affects: seahorse (Ubuntu) → ubuntuone-client (Ubuntu)
Changed in ubuntuone-client (Ubuntu):
assignee: nobody → Ubuntu One Ops+ team (ubuntuone-ops+)
importance: Undecided → Medium
tags: added: ops+
Curtis Hovey (sinzui)
Changed in ubuntuone-client (Ubuntu):
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.