gwibber-service crashed with IOError in get_avatar_path(): [Errno 36] File name too long: u'/home/richard/.cache/gwibber/avatars/https:secure.gravatar.comavatar.php?gravatar_id=e61dae1a5d9c44632c8a67781fd15dc3&default=https%3A%2F%2Fidenti.ca%2Ftheme%2Fneo%2Fdefault-avatar-stream.png&size=48'

Bug #859757 reported by Richard Merren on 2011-09-26
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Undecided
Unassigned

Bug Description

This message appeard after startup and login. I had not actually accessed the gwibber ui at all before getting this message.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber-service 3.1.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Mon Sep 26 10:26:57 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 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/richard/.cache/gwibber/avatars/https:secure.gravatar.comavatar.php?gravatar_id=e61dae1a5d9c44632c8a67781fd15dc3&default=https%3A%2F%2Fidenti.ca%2Ftheme%2Fneo%2Fdefault-avatar-stream.png&size=48'
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Richard Merren (richard-merren) wrote :
Richard Merren (richard-merren) wrote :

Additional note: this may have been before I obtained a wifi connection, so it may be that there was no response from gravatar.

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 #845374, 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.

tags: removed: need-duplicate-check
visibility: private → public
visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers