gwibber crashed with TypeError in set_stream()

[Alexandre Gomes Gaigalas]

Binary package hint: gwibber

Crashed on lucid when i deleted a search term that was shown as a stream, won't startup again

ProblemType: Crash
Architecture: i386
Date: Wed Feb 10 11:26:14 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.29.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic-pae
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with TypeError in set_stream()
Uname: Linux 2.6.32-12-generic-pae i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Stephan Rügamer (sruegamer)]

I can confirm this..this happened exactly the same way a the reporter described.

[Sean Tilley (deadsuperhero)]

Confirmed. I still get notifications from my various streams, but the client doesn't start up.

[eric (obrowny06)]

I can't start gwibber, it crashes on startup.

[Alexandre Gomes Gaigalas (alganet)]

Any workarounds for this? It's unusable for weeks...

[Omer Akram (om26er)]

Workaround for me: I reinstalled Lucid.

On Mon, Mar 1, 2010 at 7:44 PM, Alganet <email address hidden> wrote:

> Any workarounds for this? It's unusable for weeks...
>
> --
> gwibber crashed with TypeError in set_stream()
> https://bugs.launchpad.net/bugs/519830
> You received this bug notification because you are subscribed to gwibber
> in ubuntu.
>
> Status in “gwibber” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: gwibber
>
> Crashed on lucid when i deleted a search term that was shown as a stream,
> won't startup again
>
> ProblemType: Crash
> Architecture: i386
> Date: Wed Feb 10 11:26:14 2010
> DistroRelease: Ubuntu 10.04
> ExecutablePath: /usr/bin/gwibber
> InterpreterPath: /usr/bin/python2.6
> Package: gwibber 2.29.1-0ubuntu1
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/gwibber
> ProcEnviron:
> PATH=(custom, user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-12.17-generic-pae
> PythonArgs: ['/usr/bin/gwibber']
> SourcePackage: gwibber
> Title: gwibber crashed with TypeError in set_stream()
> Uname: Linux 2.6.32-12-generic-pae i686
> UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
>
>
>

[Sean Tilley (deadsuperhero)]

It's still crashing for me with this error. At first I figured it'd be fixed with CouchDB fixes, but it's still crashing with the same issues.

I really don't want to go and just re-install everything. This computer is a multiuser computer, and has a lot of data on it. Going through a backup and then a full-blown reinstall seems like a bit much.

[Yuta Ross (ylar34)]

gwibber crashes on startup for me as well.

[Sean Tilley (deadsuperhero)]

Has a fix been released yet? I'm going crazy trying to get this to work.

[Mikkel Kamstrup Erlandsen (kamstrup)]

Attaching a patch that "fixes" this bug. It doesn't fix the root cause, but allows Gwibber to start up at least so that one can manually remove the bad stream.

The patch is against the patched .deb sources, so can readily go in debian/patches/ if accepted.

[Hugh Saunders (hughsaunders)]

I linked a branch which does pretty much the same as Mikkel Kamstrup Erlandsen's patch. Probably doesn't fix the problem correctly, but lets gwibber start.

[ElSlunko (elslunko)]

Same issue here.

[Ryan Paul (segphault)]

This is now fixed in trunk.

[Yann Dìnendal (yannbreliere)]

When I try to launch it, it crashes with this "TypeError in set_stream()", but strangely, in the messenger menu applet, Gwibber appears as launched (with the blue arrow), even before I try to launch it. The blue arrow is always there, for Gwibber.

[Doooh_Head (doooh-head)]

As of today, with the latest code available via the Update Manager, gWibber now crashes on startup.

[Omer Akram (om26er)]

Doooh_Head latest version of gwibber 2.29.93 just got uploaded to archives.
That version will reach your mirror in a few hours. It would be great if someone test if this is still an issue with gwibber 2.29.93

[Yann Dìnendal (yannbreliere)]

It works, now. :)

[Omer Akram (om26er)]

Marking this fixed now, If any one still face this with gwibber 2.29.93 feel free to open this bug again.