gwibber-service crashed with GError in notify()

[Daniel Holbach]

Binary package hint: gwibber

No idea exactly why it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.25-lowlatency 2.6.35.3
Uname: Linux 2.6.35-19-lowlatency i686
Architecture: i386
Date: Sat Aug 28 09:56:04 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100816)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with GError in notify()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Bilal Akhtar (bilalakhtar)]

hehe, dholbach filing a bug :) I am having the same problem, someone please see!

[Omer Akram (om26er)]

Bilal, patches are always welcome ;-)

[Bilal Akhtar (bilalakhtar)]

On Tue, 2010-08-31 at 12:13 +0000, Omer Akram wrote:
> Bilal, patches are always welcome ;-)

I shall look at this bug tomorrow; It appears an easy fix, since I know
what's causing the error. When Gwibber queries Twitter about a person's
pic after a tweet, for some reason the API doesn't return an image
immediately. Gwibber doesn't check if an image is returned or not, it
simply turns the returned data into a Pixbuf (no data in this case),
hence causing the error and letting the service crash.

[Bilal Akhtar (bilalakhtar)]

Okay, so the last line in the Traceback means
Unknown image file format

Thanks to Google Translate !

[Bilal Akhtar (bilalakhtar)]

Not setting to In Progress since I cannot confirm whether I would be able to fix it or not. Assigning me though.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #622812, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.