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

[DavidW617]

Binary package hint: gwibber

Description: Ubuntu Natty (development branch)
Release: 11.04

gwibber:
  Installed: 2.91.93-0ubuntu1
  Candidate: 2.91.93-0ubuntu1
  Version table:
 *** 2.91.93-0ubuntu1 0
        500 http://ca.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

I am unable to launch Gwibber. Everytime I try, I get a popup telling me that a problem has been detected.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber 2.91.93-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: wl
Architecture: i386
CheckboxSubmission: 4f5564c50a42755fd0a913a86e07ee6a
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
Date: Sat Apr 2 22:21:56 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 LANG=en_HK.utf8
 LC_MESSAGES=en_CA.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber 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 natty on 2011-03-13 (20 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin mythtv netdev plugdev sambashare

[Apport retracing service (apport)]

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