gwibber-service crashed with BadStatusLine in _read_status()

Bug #524011 reported by Ryan Steele
102
This bug affects 22 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gwibber

The crash occurred while update-manager was running, but I can't say for sure it was the cause. Gwibber itself was not running. The OS is running within a VirtualBox VM.

ProblemType: Crash
Architecture: amd64
Date: Thu Feb 18 10:59:00 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
Package: gwibber-service 2.29.90-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_CA.utf8
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with BadStatusLine in _read_status()
Uname: Linux 2.6.32-13-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Ryan Steele (rgsteele) wrote :
tags: removed: need-duplicate-check
Ryan Steele (rgsteele)
visibility: private → public
Revision history for this message
Robert Collins (lifeless) wrote :

Occurs for me whenever I try to run gwibber.

Revision history for this message
Victor Vargas (kamus) wrote :

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

Changed in gwibber (Ubuntu):
status: New → Incomplete
Revision history for this message
Ryan Steele (rgsteele) wrote :

I just upgraded to 2.29.92 and can confirm the problem is still occurring.

Changed in gwibber (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Omer Akram (om26er) wrote :

Ryan, are there any specific steps that will reproduce this crash? This will help us solve the issue for you

Changed in gwibber (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Ryan Steele (rgsteele) wrote :

The crash occurs immediately upon starting Gwibber. No user interface elements of the application are ever displayed.

The application was working previously on Lucid. At that time, I had added my Twitter account. This is the only account that was added.

Changed in gwibber (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Guillaume Lanquepin-Chesnais (guyomel) wrote :

I wasn't on my computer when the crash occur, but Gwibber was running since a while and I don't have a Twitter account, only identi.ca and Facebook. When it crashed I can not reload it.

I hope it's help.

Revision history for this message
Michael Sheldon (michael-sheldon) wrote :

This appears to be a problem related to desktopcouch. Killing desktopcouch-service and then starting gwibber (which will then restart desktopcouch-service itself) cause it to start working again.

Revision history for this message
Ryan Steele (rgsteele) wrote :

Deleting the ~/.gconf/apps/gwibber/ directory and re-creating my profile has resolved the issue for me for now.

Revision history for this message
Victor Vargas (kamus) wrote :

Since this issue has a long time without activity and was fixed after restore gwibber config I will close this report for now but if this issue reappears in latest release please reopened again, Thanks.

Changed in gwibber (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.