ubuntuone-launch crashed with DBusException in __new__()

[djchandler]

Binary package hint: ubuntuone-client

New report even though descriptions of two other bugs match, but this is AMD64 instead of i386; libubuntuone-1.0-1 (0.2.102-0ubuntu1, 0.3.0-0ubuntu1) and python-ubuntuone (0.2.102-0ubuntu1, 0.3.0-0ubuntu1) have been updated since last report close to matching this description. I update at least once a day as well as safe-upgrade.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ubuntuone-client 1.1.91-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic x86_64
Architecture: amd64
Date: Mon Apr 12 14:32:24 2010
ExecutablePath: /usr/bin/ubuntuone-launch
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ubuntuone-launch
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/ubuntuone-launch']
SourcePackage: ubuntuone-client
Title: ubuntuone-launch crashed with DBusException in __new__()
UbuntuOneSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UbuntuOneSyncdaemonExceptionsLog:

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 #558591, 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.

[djchandler (djchandler)]

Bug #558591 is apparently private and can't be accessed by me. will someone please subscribe me to this bug?

[Mitch Towner (kermiac)]

Hi djchandler. I have set bug #558591 to public as it contains no private/ sensitive information. You will now be able to view that "master" bug report.