Comment 3 for bug 275492

Seems related to what I'm seeing here, a crash a few seconds after start up :

arnaud@dell-desktop:~$ monsterz
Traceback (most recent call last):
  File "/usr/share/games/monsterz/monsterz.py", line 1998, in <module>
    main()
  File "/usr/share/games/monsterz/monsterz.py", line 1993, in main
    monsterz.go()
  File "/usr/share/games/monsterz/monsterz.py", line 1271, in go
    iterator()
  File "/usr/share/games/monsterz/monsterz.py", line 1381, in iterate_menu
    self.copyright_draw()
  File "/usr/share/games/monsterz/monsterz.py", line 1300, in copyright_draw
    system.blit(scroll, (13, 437))
  File "/usr/share/games/monsterz/monsterz.py", line 403, in blit
    self.background.blit(surf, coords)
pygame.error: Surfaces must not be locked during blit

I spent some time tracking this down (this was a regression from hardy) :
monsterz intrepid (0.7.1) + pythom-pygame intrepid (1.8.1) =>blit error
monsterz hardy (0.7.0) + pythom-pygame intrepid (1.8.1) => blit error
monsterz intrepid (0.7.1) + pythom-pygame hardy (1.7.1) => works fine

I read on a pygame mailing list that locking changes were made in 1.8.x, this seems to break monsterz

This has been seen on Gentoo as well :
http://bugs.gentoo.org/show_bug.cgi?id=238774

And has also been relayed upstream, but no reply so far:
http://sam.zoy.org/monsterz/msg00092.html