gwibber-service crashed with RuntimeError in __find_port__linux()

[Paul Sanders]

Binary package hint: gwibber

Description: Ubuntu lucid (development branch)
Release: 10.04

  Installed: 2.29.92.1-0ubuntu1
  Candidate: 2.29.92.1-0ubuntu1
  Version table:
 *** 2.29.92.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

I get this crash message when I first start up the computer.

ProblemType: Crash
Architecture: amd64
Date: Fri Mar 26 20:47:30 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
InterpreterPath: /usr/bin/python2.6
Package: gwibber-service 2.29.92.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with RuntimeError in __find_port__linux()
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Victor Vargas (kamus)]

Please could you upgrade to latest version of gwibber (2.29.94) and check if this problem is still affecting you? Additionally this issue is very similar to bug 547084 (probably a duplicate), Thanks in advance!

[Paul Sanders (paul41)]

It seems to be fixed with the latest version.

[Victor Vargas (kamus)]

@Paul, for now I will marked such Fix Released but if this issue reappears please don't feel hesitated and reopen again. Thanks!

[Nicolás Abel Carbone (nicocarbone)]

I have this problem. Using the last gwibber-service, updated on 2010-04-09.

[Paul Sanders (paul41)]

This problem has shown back up for me also.

Gwibber version 2.29.95-0ubuntu2

[Nizar Kerkeni (nizarus)]

I have this problem too (Gwibber version 2.29.95 64bit version)

[Victor Vargas (kamus)]

There is too many people affected by this issue that I will set status to incomplete and wait for a gwibber developer can take a look into this problem.

[Victor Vargas (kamus)]

Additionally, have you tried to run a rm ~/.cache/desktop-couch ~/.config/desktop-couch and
~/.local/share/desktop-couch , then start gwibber and check if this issue appears?

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!