gwibber-bugs team mailing list archive

[Ken VanDine <ken.vandine@xxxxxxxxxxxxx>]

@aj00200:  are you still getting this same problem?  Or perhaps you had
upgraded gwibber and the gwibber-service hadn't restarted since the
upgrade?

Your particular traceback looks like the gwibber-service process you had
running was from 2.32 and the client was 3.0.  If you are still getting
this same error, please open a new bug for it.

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

Title:
  gwibber crashed with DBusException in call_blocking() on startup

Status in Gwibber:
  New
Status in “gwibber” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gwibber

  gwibber 2.32.2-0ubuntu2 crashes on startup from "Internet" menu, on
  maverick desktop with current updates.

  (The traceback looks the same as many other bugs which each have many
  duplicates, but they all look flagged as invalid or fix-released.  As
  I cannot choose between them, I've opened a new report so that the
  experts can decide.  Sorry if this makes extra work.)

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: gwibber 2.32.2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  Architecture: i386
  Date: Mon Jan 10 01:01:26 2011
  ExecutablePath: /usr/bin/gwibber
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
  InterpreterPath: /usr/bin/python2.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gwibber
  ProcEnviron:
   LANG=en_NZ.utf8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/gwibber']
  SourcePackage: gwibber
  Title: gwibber crashed with DBusException in call_blocking()
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare