Bug 585482

Summary: [abrt] crash in PySolFC-2.0-2.fc12: game.py:2979:pload:AssertionError: Invalid or damaged PySolFC save file
Product: [Fedora] Fedora Reporter: marco
Component: PySolFCAssignee: Stewart Adam <s.adam>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: s.adam
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:44d3f650
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 15:30:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
File: backtrace none

Description marco 2010-04-24 10:14:35 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
cmdline: /usr/bin/python /usr/share/PySolFC/pysol.py --sound-mod=pygame
component: PySolFC
executable: /usr/share/PySolFC/pysol.py
package: PySolFC-2.0-2.fc12
reason: game.py:2979:pload:AssertionError: Invalid or damaged PySolFC save file
release: Fedora release 12 (Constantine)

game.py:2979:pload:AssertionError: Invalid or damaged PySolFC save file

Traceback (most recent call last):
  File "/usr/share/PySolFC/pysol.py", line 32, in <module>
  File "/usr/lib/python2.6/site-packages/pysollib/main.py", line 363, in main
  File "/usr/lib/python2.6/site-packages/pysollib/app.py", line 517, in mainloop
    self.runGame(id, random)
  File "/usr/lib/python2.6/site-packages/pysollib/app.py", line 631, in runGame
  File "/usr/lib/python2.6/site-packages/pysollib/game.py", line 557, in restoreGameFromBookmark
    game = self._undumpGame(p, self.app)
  File "/usr/lib/python2.6/site-packages/pysollib/game.py", line 3014, in _undumpGame
    initial_seed = pload(long)
  File "/usr/lib/python2.6/site-packages/pysollib/game.py", line 2979, in pload
    assert isinstance(obj, t), err_txt
AssertionError: Invalid or damaged PySolFC save file

Local variables in innermost frame:
p: <cPickle.Unpickler object at 0x214e610>
obj: 1496716960132431502
t: <type 'long'>
err_txt: u'Invalid or damaged PySolFC save file'

Comment 1 marco 2010-04-24 10:14:37 UTC
Created attachment 408799 [details]
File: backtrace

Comment 2 Stewart Adam 2010-04-24 19:53:16 UTC
It looks like your PySolFC save file is invalid or corrupted. Was it created using this version of PySolFC?

Comment 3 Bug Zapper 2010-11-03 16:25:35 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 4 Bug Zapper 2010-12-03 15:30:20 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.