gwibber-service crashed with IOError in get_avatar_path(): [Errno 36] File name too long: u'/home/chris/.cache/gwibber/avatars/http:a1.twimg.comprofile_images1644239186WIZ-KHALIZAx-WAKEN-BAKEN-TOUR-2010-x-Best-Buy-Theatre-NYC-x-via-Ernest-Estim_-10.21.10.-Image-Copywritten-All-Rights-Reserved-2010.-Use-Without-Proper-Permission-Prohibited.-www.ernestestime.com-www.ernestestime.comcolumn046_large_normal.jpg'

[Chris Sharp]

I didn't do anything special. Apport popped up with this error.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber-service 3.2.1-0ubuntu1.3
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Nov 28 09:29:28 2011
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with IOError in get_avatar_path(): [Errno 36] File name too long: u'/home/chris/.cache/gwibber/avatars/http:a1.twimg.comprofile_images1644239186WIZ-KHALIZAx-WAKEN-BAKEN-TOUR-2010-x-Best-Buy-Theatre-NYC-x-via-Ernest-Estim_-10.21.10.-Image-Copywritten-All-Rights-Reserved-2010.-Use-Without-Proper-Permission-Prohibited.-www.ernestestime.com-www.ernestestime.comcolumn046_large_normal.jpg'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #849654, 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.