← Back to team overview

desktop-packages team mailing list archive

[Bug 819579] Re: gwibber-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.

 

*** This bug is a duplicate of bug 741621 ***
    https://bugs.launchpad.net/bugs/741621

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 #741621, 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

** Attachment removed: "Dependencies.txt"
   https://bugs.launchpad.net/bugs/819579/+attachment/2248317/+files/Dependencies.txt

** Attachment removed: "ProcMaps.txt"
   https://bugs.launchpad.net/bugs/819579/+attachment/2248318/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   https://bugs.launchpad.net/bugs/819579/+attachment/2248319/+files/ProcStatus.txt

** This bug has been marked a duplicate of bug 741621
   gwibber-service crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name org.desktopcouch.CouchDB was not provided by any .service files

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/819579

Title:
  gwibber-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.

Status in “gwibber” package in Ubuntu:
  New

Bug description:
  gwibber-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.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gwibber-service 3.1.4+r1083-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
  Uname: Linux 3.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue Aug  2 04:09:38 2011
  ExecutablePath: /usr/bin/gwibber-service
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110731)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
  ProcEnviron:
   SHELL=/bin/bash
   LANG=ro_RO.UTF-8
  PythonArgs: ['/usr/bin/gwibber-service']
  SourcePackage: gwibber
  Title: gwibber-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.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  gwibber.log:
   2011-08-02 04:09:12,777 - Gwibber Service - INFO - Running from the system path
   2011-08-02 04:09:38,760 - Gwibber Service - INFO - Running from the system path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/819579/+subscriptions