gwibber-bugs team mailing list archive

[czajkowski <laura@xxxxxxxxxxxxxxx>]

Just upgraded from Maverick to natty, couldn't send any tweets/dents.
Stopped and restarted all services.   Ran echo "delete from
messages;vacuum;" | sqlite3 ~/.config/gwibber/gwibber.sqlite


started gwibber again, and it just crashed.

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/724918

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:
  New
Status in “gwibber” package in Ubuntu:
  New

Bug description:
  Binary package hint: gwibber

  just launched gwibber and got this crash message.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gwibber 2.91.90-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic i686
  Architecture: i386
  CheckboxSubmission: 4afb8c68a8fa5938a80183a271a939ea
  CheckboxSystem: c460f5739f7c8446c3d18c3e0e7c5745
  Date: Fri Feb 25 08:36:02 2011
  ExecutablePath: /usr/bin/gwibber
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gwibber
  ProcEnviron:
   LANGUAGE=es_CL:es:en_GB:en
   LANG=en_US.UTF-8
   LC_MESSAGES=es_CL.utf8
   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.
  UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare video