← Back to team overview

desktop-packages team mailing list archive

[Bug 842237] 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/842237/+attachment/2359042/+files/Dependencies.txt

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

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

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

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

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:
  gwibber fails to start and gwibber-service hangs:

  lhw:~ % gwibber-service -d -o 
  Loading plugin Identi.ca version 1.1
  Loading plugin Twitter version 1.0
  Loading plugin Flickr version 1.0
  Loading plugin Facebook version 1.1
  Facebook    : DEBUG    Setting up monitors
  /usr/lib/python2.7/dist-packages/gi/module.py:138: Warning: cannot register existing type `DbusmenuMenuitem'
    g_type = info.get_g_type()
  /usr/lib/python2.7/dist-packages/gi/module.py:138: Warning: g_once_init_leave: assertion `initialization_value != 0' failed
    g_type = info.get_g_type()
  /usr/lib/python2.7/dist-packages/gi/module.py:142: Warning: g_type_get_qdata: assertion `node != NULL' failed
    type_ = g_type.pytype

  
  lhw:~ % gwibber -d -o 
  ERROR:dbus.proxies:Introspect error on com.Gwibber.Service:/com/gwibber/Service: dbus.exceptions.DBusException: 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.
  Traceback (most recent call last):
    File "/usr/bin/gwibber", line 87, in <module>
      client.Client()
    File "/usr/lib/python2.7/dist-packages/gwibber/client.py", line 623, in __init__
      self.w = GwibberClient()
    File "/usr/lib/python2.7/dist-packages/gwibber/client.py", line 40, in __init__
      self.model = gwui.Model()
    File "/usr/lib/python2.7/dist-packages/gwibber/gwui.py", line 50, in __init__
      self.services = json.loads(self.daemon.GetServices())
    File "/usr/lib/pymodules/python2.7/dbus/proxies.py", line 68, in __call__
      return self._proxy_method(*args, **keywords)
    File "/usr/lib/pymodules/python2.7/dbus/proxies.py", line 140, in __call__
      **keywords)
    File "/usr/lib/pymodules/python2.7/dbus/connection.py", line 630, in call_blocking
      message, timeout)
  dbus.exceptions.DBusException: 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.04
  Package: gwibber 3.0.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  Date: Tue Sep  6 01:50:21 2011
  ExecutablePath: /usr/bin/gwibber
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gwibber -d -o
  ProcEnviron:
   LANG=de_DE.UTF-8
   LANGUAGE=de_DE:de_DE.UTF-8:en
   SHELL=/usr/bin/zsh
   PATH=(custom, user)
  PythonArgs: ['/usr/bin/gwibber', '-d', '-o']
  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-04-17 (141 days ago)
  UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare video

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