desktopcouch-service crashed with DBusException in call_blocking(): 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 #698246 reported by pschonmann
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
desktopcouch (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: desktopcouch

Clicked on Couch DB accidentally in evolution ( contacts ) I have no ubuntuone login.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: desktopcouch 0.6.9b-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7
Uname: Linux 2.6.37-11-generic x86_64
Architecture: amd64
Date: Thu Jan 6 20:13:42 2011
ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=en_AG.utf8
 LANGUAGE=en
 LANG=cs_CZ.utf8
PythonArgs: ['/usr/lib/desktopcouch/desktopcouch-service']
SourcePackage: desktopcouch
Title: desktopcouch-service crashed with DBusException in call_blocking(): 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.
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
pschonmann (pschonmann) wrote :
tags: removed: need-duplicate-check
pschonmann (pschonmann)
visibility: private → public
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, this bug report is about a DBus client failing to connect with the DBus backend and to really understand the issue we need the crash from the DBus backend not from the client. Client crashes are prevented from being report by apport in Precise and in the event that the backend crashes apport should report those ass separate. Because of the previously stated reasons I am setting this bug report to Invalid.

Changed in desktopcouch (Ubuntu):
status: New → Invalid
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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