gwibber-accounts crashed with RuntimeError in find_pid()

[Juanje Ojeda]

Binary package hint: gwibber

gwibber-accounts creashed when I clicked on the accounts menu at Fast User Switch the first time I run the system after a fresh installation.

ProblemType: Bug
Architecture: i386
Date: Fri Feb 26 04:24:06 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
Package: gwibber 2.29.90.1-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=es_ES.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SourcePackage: gwibber
Uname: Linux 2.6.32-14-generic i686

[Juanje Ojeda (juanje)]

The problem is the desktop-couch was not running. The desktop-couch is launched by Gwibber, but this is not launched at the begging of the session, so the desktop-couch service is not launched when gwibber-accounts is called.

If the Gwibber is running the menu entry for the accounts works fine.

[Victor Vargas (kamus)]

Please could you upgrade to latest version of gwibber (2.29.92) and check if this problem is still affecting you? Thanks in advance!

[Tomáš Honzák (thonzak)]

Upgrade to gwibber version 2.29.92.1-0ubuntu1 resolved the problem for me. Thanks!

[Victor Vargas (kamus)]

@Juan, please could you check if this issue is still affecting you under gwibber 2.29.92-1? Thanks!

[Juanje Ojeda (juanje)]

I got gwibber-service and gwibber version 2.29.92.1-0ubuntu1 but still have a problem.

The traceback is different but it happends under the same circunstances. It seems that it's not the same issue. Acctually the new error has its own bug:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/536702

[Victor Vargas (kamus)]

@Juanje, Please could you upgrade to latest version of gwibber 2.29.95 and desktopcouch 0.6.3 and check if this issue is still affecting you? Thanks!

[Victor Vargas (kamus)]

@Juanje, any news about this issue? is still affecting you in latest gwibber release? Thanks!

[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!