← Back to team overview

desktop-packages team mailing list archive

[Bug 846661] Re: gwibber-accounts 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 676981 ***
    https://bugs.launchpad.net/bugs/676981

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 #676981, 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/846661/+attachment/2383149/+files/Dependencies.txt

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

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

** This bug has been marked a duplicate of bug 676981
   gwibber-accounts crashed with DBusException in call_blocking()

** 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/846661

Title:
  gwibber-accounts 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 just doesn't work on my set up.  It can take up to 15 minutes
  to show itself and then will gray out without actually showing
  content.   This had already been an issue with 11.4 and I have been
  using Turpial instead.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gwibber 3.1.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Sun Sep 11 07:22:36 2011
  ExecutablePath: /usr/bin/gwibber-accounts
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  InterpreterPath: /usr/bin/python2.7
  ProcCmdline: python /usr/bin/gwibber-accounts
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/gwibber-accounts']
  SourcePackage: gwibber
  Title: gwibber-accounts 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

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