Error on right click on properties of a vectorial layer .shp

[marcobra (Marco Braida)]

Binary package hint: thuban

Description: Ubuntu 9.04
Release: 9.04

Running Thuban...

apt-cache policy thuban
thuban:
  Installato: 1.2.0-2.1ubuntu1
  Candidato: 1.2.0-2.1ubuntu1
  Tabella versione:
 *** 1.2.0-2.1ubuntu1 0
        500 http://archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

On right click on a .shp layer with mouse to edit properties i get this error...

Si è verificata una eccezione non prevista:
'ascii' codec can't decode byte 0xc3 in position 8: ordinal not in range(128)
(per piacere segnala l'errore a http://thuban.intevation.org/bugtracker.html)

Traceback (most recent call last):
  File "/usr/lib/thuban/Thuban/UI/mainwindow.py", line 297, in invoke_command
    command.Execute(self.Context())
  File "/usr/lib/thuban/Thuban/UI/command.py", line 121, in Execute
    apply(self.function, (context,) + self.args + args, kw)
  File "/usr/lib/thuban/Thuban/UI/mainwindow.py", line 1071, in call_method
    apply(getattr(context.mainwindow, methodname), args)
  File "/usr/lib/thuban/Thuban/UI/mainwindow.py", line 793, in LayerEditProperties
    self.OpenLayerProperties(layer)
  File "/usr/lib/thuban/Thuban/UI/mainwindow.py", line 807, in OpenLayerProperties
    self.OpenOrRaiseDialog(name, dialog_class, layer, group = group)
  File "/usr/lib/thuban/Thuban/UI/mainwindow.py", line 430, in OpenOrRaiseDialog
    dialog = dialog_class(self, name, *args, **kw)
  File "/usr/lib/thuban/Thuban/UI/classifier.py", line 769, in __init__
    LayerProperties.__init__(self, parent, name, layer)
  File "/usr/lib/thuban/Thuban/UI/layerproperties.py", line 31, in __init__
    self.SetTitle(layer.Title())
  File "/usr/lib/thuban/Thuban/UI/layerproperties.py", line 160, in SetTitle
    NonModalNonParentDialog.SetTitle(self, _("Layer Properties") + title)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 8: ordinal not in range(128)

Thank you

[Bas Couwenberg (sebastic)]

Thuban is dead upstream, if a newer Ubuntu release doesn't have the fix for this issue, it's unlikely to ever get fixed.