ubuntuone-control-panel-gtk crashed with Error in uri_hook(): Erro on opening file "/home/my_name/Desktop/Ubuntu": File or folder not found

[Gustavo Guidorizzi]

Binary package hint: ubuntuone-control-panel

(1) Description: Ubuntu Natty (development branch)
Release: 11.04

(2) ubuntuone-control-panel:
  Instalado: 0.9.0-0ubuntu1
  Candidato: 0.9.0-0ubuntu1
  Tabela de versão:
 *** 0.9.0-0ubuntu1 0
        500 http://br.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

(3) I had just sync'ed my Ubuntu One account and I tried to open a local folder
showing on UO Control Panel.

(4) The folder didn't open and a error message popped-up. UO didn't crash, though.

Notes: Natty was running on VirtualBox 4.0.4 and the folder name had spaces and accent marks in it.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-control-panel-gtk 0.9.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
Architecture: amd64
Date: Fri Mar 4 01:33:03 2011
ExecutablePath: /usr/bin/ubuntuone-control-panel-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ubuntuone-control-panel-gtk
ProcEnviron:
 LANGUAGE=pt_BR:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/ubuntuone-control-panel-gtk']
SourcePackage: ubuntuone-control-panel
Title: ubuntuone-control-panel-gtk crashed with Error in uri_hook(): Erro ao iniciar arquivo "/home/gustavo/Área de Trabalho/Ubuntu": Arquivo ou diretório não encontrado
UpgradeStatus: Upgraded to natty on 2011-03-03 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #728601, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.