← Back to team overview

desktop-packages team mailing list archive

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

 

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

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.

** Tags removed: need-duplicate-check

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

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

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

** This bug has been marked a duplicate of bug 700667
   gwibber crashed with DBusException in call_blocking() on startup

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

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.

Status in “gwibber” package in Ubuntu:
  New

Bug description:
  On start up Gwibber reports a crash,  speaking to Ken van dine on irc I did killall -9 gwibber-service; gwibber-service -d -o
   and restarted Gwibber, it still won't start and crash report came again.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gwibber 3.0.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic i686
  Architecture: i386
  Date: Mon Jul 18 17:54:00 2011
  ExecutablePath: /usr/bin/gwibber
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gwibber
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_IE.UTF-8
   LC_MESSAGES=en_GB.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 (126 days ago)
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

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