Menu Bug in Endgame:Singularity

[Scott Parker]

In the attached saved game (MenuBug.sav), the main menu keeps popping up, making the game unplayable. Running from the command line (see below) gives "ValueError: zero-size array to ufunc.reduce without identity" in buyable.py.

Steps to repeat:
1) Download MenuBug.sav
2) Save to ~/.endgame/saves
3) Start singularity and load the game MenuBug

Package Details:
singularity 0.30-2
Ubuntu 10.04
python 2.65.0ubuntu1
pygame 1.9.1release-0ubuntu1
numpy 1:1.3.0:0-3build1

Command line output:
Traceback (most recent call last):
  File "/usr/share/games/singularity/code/safety.py", line 58, in safe_call
    return func(*args, **kwargs)
  File "/usr/share/games/singularity/code/graphics/dialog.py", line 180, in show
    self.handle(pygame.event.Event(pygame.USEREVENT))
  File "/usr/share/games/singularity/code/graphics/dialog.py", line 306, in handle
    return self.call_handlers(handlers, event)
  File "/usr/share/games/singularity/code/graphics/dialog.py", line 318, in call_handlers
    handler(event)
  File "/usr/share/games/singularity/code/screens/map.py", line 490, in on_tick
    mins_passed = g.pl.give_time(secs)
  File "/usr/share/games/singularity/code/player.py", line 321, in give_time
    built_item = item.work_on(time = mins_passed)
  File "/usr/share/games/singularity/code/buyable.py", line 191, in work_on
    spent, self.cost_paid = self.calculate_work(*args, **kwargs)
  File "/usr/share/games/singularity/code/buyable.py", line 168, in calculate_work
    least_complete = self.min_valid(pct_complete)
  File "/usr/share/games/singularity/code/buyable.py", line 145, in min_valid
    return complete[self.total_cost > 0].min()
ValueError: zero-size array to ufunc.reduce without identity

[Sebastian Bator (eremit7)]

I could verify the issue under 11.10. Loading MenuBug.sav results in permanent popping up of the menu, whereas other saves function as expected.

This issue was already reported upstream: https://code.google.com/p/endgame-singularity/issues/detail?id=107

[Hans Joachim Desserud (hjd)]

This sounds similar to bug 576504, however that is supposed to be fixed.

[Scott Parker (scotttparker)]

The manifestation is similar, but the root cause does not appear to be. The actual error reported in the traceback is different for the the two bugs. Implementing the workaround first proposed in 576504 did not fix the bug and actually created additional bugs, presumably because the current version of python is 2.65, not 2.7.