gwibber crashed with KeyError in setup_ui(): 'stream'

Bug #731630 reported by Nicolas Schirrer
46
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: gwibber

I just restarted gwibber after this crash occurred : https://bugs.launchpad.net/gwibber/+bug/542748
And it crashed and prompted this bug report.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber 2.91.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Tue Mar 8 23:08:24 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110124.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with KeyError in setup_ui(): 'stream'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Nicolas Schirrer (nicolas-schirrer) wrote :
Revision history for this message
Nicolas Schirrer (nicolas-schirrer) wrote :

Killing gwibber-service doesn't solve this issue, gwibber still refuses to launch (though it did previously, yet very slowly).

tags: removed: need-duplicate-check
Victor Vargas (kamus)
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
Victor Vargas (kamus)
visibility: private → public
Revision history for this message
Ron Lusk (luskwater) wrote :

Not sure what I can add: I have three streams (two Twitter lists and Facebook) that the system should be displaying when it comes up.

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

Hey Nicolas have you tried to upgrade your gwibber release to the latest available in Natty? by the way, this issue could be also related to a parameter in your gconf settings.

Changed in gwibber (Ubuntu):
status: New → Incomplete
Revision history for this message
Ron Lusk (luskwater) wrote :

What parameter in the gconf settings, please?

And when I inquire of apt-get, I'm told that I already have the latest gwibber release installed.

What is "Incomplete" about this bug report that we can help with?

Revision history for this message
Nicolas Schirrer (nicolas-schirrer) wrote :

Hi Kamus,

Sorry for my late answer: coming back from a trip I performed the updates, and the problem seems solved for today.

Revision history for this message
Matt Bailey (mattb90) wrote :

Attempting to open Gwibber for the first time results in this issue - I have three streams (all Twitter), and can't get Gwibber to open as a result.

Changed in gwibber (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
DavidW617 (davidw617) wrote :

It seems that sometimes when Gwibber crashes (for me it was https://bugs.launchpad.net/gwibber/+bug/542748) it messes up a gconf key. Particularly the one in apps/gwibber/preferences/streams. Mine was set to [{}]. I changed that to [] and Gwibber launched but no streams were visible. I hit the Gwibber menu button and then New Stream and Gwibber works for me again. Now the value in gconf for me is: [{"account": null, "transient": false, "stream": "messages"}].

I hope this helps get the bug fixed.

Revision history for this message
Mace (xmacex) wrote :

Thanks ^Again617, i had the same "[{}]" in apps/gwibber/preferences/streams. Removed it and now Gwibber starts up again properly. The other gwibber-* commands were working all the time, but just not the Gwibber main window.

Revision history for this message
crazyserver (crazyserver) wrote :

It can be solved by code bt adding a test on line 254 of client.py:

    self.update_menu_availability()
    for stream in streams:
- if stream["stream"]:
+ if "stream" in stream and stream["stream"]:
        gobject.idle_add(lambda: self.service.UpdateIndicators(stream["stream"]))

Revision history for this message
Bilal Shahid (s9iper1) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better,
this should be fixed in the upcoming 3.3.4 release.

Changed in gwibber (Ubuntu):
status: Confirmed → Invalid
Bilal Shahid (s9iper1)
Changed in gwibber (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gwibber (Ubuntu) because there has been no activity for 60 days.]

Changed in gwibber (Ubuntu):
status: Incomplete → Expired
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.