gwibber-service crashed with ValueError in <module>()

[Heero]

Binary package hint: gwibber

This bug don't close gwibber. So it can also be abort what has the bug.
You are using Ubuntu 10.04 LTS
                - the Lucid Lynx - released in April 2010 and supported until April 2013.

Gwibber package is 2.29.91-0ubuntu1.

ProblemType: Crash
Architecture: amd64
Date: Mon Mar 8 19:11:31 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
InterpreterPath: /usr/bin/python2.6
Package: gwibber-service 2.29.91-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with ValueError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/gwibber-service", line 9, in <module>
     if int(popen("pidof -x gwibber-service").read()) != getpid():
 ValueError: invalid literal for int() with base 10: '3918 3915 3914 3702\n'
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video

[Pedro Villavicencio (pedro)]

Thanks for the report Heero, is this still an issue for you with latest Gwibber on Lucid? Please test it and comment back, Thanks in advance!.

[Heero (heero2007)]

Yes, it is. The programm isn't colapsed. It runs without a bug, but aport report a crash.

[Victor Vargas (kamus)]

@Heero, Please could you run under latest version of gwibber: gwibber --debug > gwibber-debug.txt and attach resulted output of this file to your report (following your steps to reproduce this issue), 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!