← Back to team overview

desktop-packages team mailing list archive

[Bug 821607] 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

** This bug is no longer a duplicate of private bug 829335
** This bug has been marked a duplicate of bug 676981
   [MASTER] gwibber-accounts crashed with DBusException in call_blocking()

-- 
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/821607

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:
  Happened when authenticating a second twitter account.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gwibber 3.1.4+r1093-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: Fri Aug  5 13:59:16 2011
  ExecutablePath: /usr/bin/gwibber-accounts
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110321)
  InterpreterPath: /usr/bin/python2.7
  ProcCmdline: python /usr/bin/gwibber-accounts
  ProcEnviron:
   LANGUAGE=es_DO:es:en_US:en
   LANG=es_DO.UTF-8
   LC_MESSAGES=es_DO.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: Upgraded to oneiric on 2011-08-05 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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