pithos crashed with AttributeError in on_gst_error(): 'NoneType' object has no attribute 'message'

[Noel Arzola]

I got Pandora does not support your client version message then this crash occured

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: pithos 0.3.10-1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Thu Sep 29 10:10:11 2011
ExecutablePath: /usr/bin/pithos
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/pithos
PythonArgs: ['/usr/bin/pithos']
SourcePackage: pithos
Title: pithos crashed with AttributeError in on_gst_error(): 'NoneType' object has no attribute 'message'
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/pithos", line 519, in on_gst_error
     self.current_song.message = "Error: "+str(err)
 AttributeError: 'NoneType' object has no attribute 'message'
UpgradeStatus: Upgraded to oneiric on 2011-09-28 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #846627, so it 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. Feel free to continue to report any other bugs you may find.

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[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 #846627, 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.