ubuntuone-launch crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Bug #852423 reported by david edwards
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

fail at start

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: ubuntuone-client 1.7.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Sat Sep 17 00:50:57 2011
ExecutablePath: /usr/bin/ubuntuone-launch
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110804)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ubuntuone-launch
PythonArgs: ['/usr/bin/ubuntuone-launch']
SourcePackage: ubuntuone-client
Title: ubuntuone-launch crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
UbuntuOneSyncdaemonExceptionsLog:

UpgradeStatus: Upgraded to oneiric on 2011-09-15 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
david edwards (warriet) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

tags: removed: need-duplicate-check
visibility: private → public
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.