Thank you for taking the time to report this bug. This issue has been
fixed in newer versions of Ubuntu, and Jaunty is EOL. Thus, I am closing
this bugtask.
** Changed in: monsterz (Ubuntu Jaunty)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubu
Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the
report. The bug has been fixed in newer releases of Ubuntu.
** Changed in: monsterz (Ubuntu Intrepid)
Status: New => Invalid
--
monsterz.py crashed with error in blit()
https://bugs.launchpad.net/bugs/275492
You recei
Hi Philippe,
The version in karmic comes from Debian, the patch was taken by them a
few months ago, and we synced to debian again for karmic.
The version in Intrepid always had the problem, and has seen no updates,
so it is still obviously there.
As to the version in Jaunty, I am somewhat surpri
This is still unfixed in Intrepid and Jaunty because the patch only got
included into the package, but not applied during building. The
revision in Karmic (-3) fixes this issue and is reportedly installable
on Intrepid.
** Also affects: monsterz (Ubuntu Intrepid)
Importance: Undecided
S
@Arnaud
Ok I ran through the manual install using the deb file found here
http://launchpadlibrarian.net/22300806/monsterz_0.7.1-2ubuntu1_i386.deb
- still get the same lock error.
and here is what fixed it:
First I removed the monsterz that was installed from the repo.
Then ran the gnome deb inst
@Jon
The latest version 0.7.1-2ubuntu1 is not in the intrepid repositories
(see https://launchpad.net/ubuntu/+source/monsterz), only in the
upcoming jaunty version
To make it work, the work around is to manually install the jaunty
version (it works fine, this is how I made it work at home).
To d
Running the latest 0.7.1-2ubuntu1 from the intrepid repositories and I
am running into the lock error:
$ monsterz
Traceback (most recent call last):
File "/usr/share/games/monsterz/monsterz.py", line 1998, in
main()
File "/usr/share/games/monsterz/monsterz.py", line 1993, in main
mon
I installed manually the corrected package (jaunty) on my intrepid
laptop. It unbreaks the game here (I had to play several games to
confirm it :) ).
Thanks a lot for your work David.
--
monsterz.py crashed with error in blit()
https://bugs.launchpad.net/bugs/275492
You received this bug notific
Hi David,
Thanks for the packaging, I was fearing the patch would sit in idle for a
long time.
I will try the jaunty package on my (still intrepid) setup. Will report
tonight.
Thanks,
Arnaud
On Sun, Feb 8, 2009 at 10:00 PM, David Futcher
wrote:
> The Fedora patch is the same patch as attached
The Fedora patch is the same patch as attached to this bug. I have
uploaded it (0.7.1-2ubuntu1), so should be in Jaunty by tomorrow. If
someone can test this and post the results back here, I want to make
sure the bug has been caught.
--
monsterz.py crashed with error in blit()
https://bugs.launc
This bug was fixed in the package monsterz - 0.7.1-2ubuntu1
---
monsterz (0.7.1-2ubuntu1) jaunty; urgency=low
* debian/patches/020_fix_blit_crash.diff:
- monsterz.py: Fix crash on startup in blit() function (LP: #275492)
- Thanks to Arnaud Jeansen and Rafał Psota.
-- D
Fedora seems to have a patch to fix this. I'll look at applying it in
the Ubuntu package.
** Changed in: monsterz (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => David Futcher (bobbo)
--
monsterz.py crashed with error in blit()
https://bugs.launchpad.net/bugs/275492
You
As the package in Ubuntu is directly imported from Debian, I contacted the
Debian maintainer (which also happens to be the main developer upstream) to
point him to this bug and this patch.
It is still a non issue in Debian (the unstable pygame version is inferior to
1.8.1), so I hope he will be
Patch generated using 'bzr diff'. I will be on vacation for the next few
days, so I won't be able to generate a real debdiff or ask for an upload
until January.
Anyone from MOTU to have a look at this ? Thanks.
** Attachment added: "For loop changes for pygame 1.8.1"
http://launchpadlibrarian.
I spent some time on it tonight (first time at reading python :().
It seems that at two points in the codebase, a pygame surface cannot be
blit because the surface is still locked (there is an unlock() before
the blit, but it seems to fail). Those two points are the copyright
surface (this is the
Same here, (X)Ubuntu 8.10 both on AMD64 as well as on a i386 system.
--
monsterz.py crashed with error in blit()
https://bugs.launchpad.net/bugs/275492
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
I can confirm this bug under Ubuntu 8.10 on amd64 systems (I've tried
2).
** Changed in: monsterz (Ubuntu)
Status: New => Confirmed
--
monsterz.py crashed with error in blit()
https://bugs.launchpad.net/bugs/275492
You received this bug notification because you are a member of Ubuntu
Bugs
Seems related to what I'm seeing here, a crash a few seconds after start
up :
[EMAIL PROTECTED]:~$ monsterz
Traceback (most recent call last):
File "/usr/share/games/monsterz/monsterz.py", line 1998, in
main()
File "/usr/share/games/monsterz/monsterz.py", line 1993, in main
monsterz.
I did a fresh install of Intrepid from Hardy, and I am experiencing the same
problem.
I have attached a screen shot of what terminal says.
** Attachment added: "1234.png"
http://launchpadlibrarian.net/19317887/1234.png
--
monsterz.py crashed with error in blit()
https://bugs.launchpad.net/b
** Visibility changed to: Public
--
monsterz.py crashed with error in blit()
https://bugs.launchpad.net/bugs/275492
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
20 matches
Mail list logo
