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
*** This bug is a duplicate of bug 397961 ***
https://bugs.launchpad.net/bugs/397961
** This bug has been marked a duplicate of bug 397961
pitivi crashed with SIGSEGV in PyObject_IsInstance()
--
pitivi segfaults immediately
https://bugs.launchpad.net/bugs/396013
You received this bug
Public bug reported:
Binary package hint: monsterz
Source package: monsterz
Debian unstable version: 0.7.1-3
Ubuntu version: 0.7.1-2ubuntu1
An ubuntu delta had to be made for LP: #275492, it has now been taken in
the unstable version of the Debian package (debian bug #523877).
There is no
** Tags added: sync
--
sync request: monsterz
https://bugs.launchpad.net/bugs/380965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
Fix was released almost a month ago as meta-gnome2-2.22.2~4ubuntu6,
marking fix released
** Changed in: meta-gnome2 (Ubuntu)
Status: Fix Committed = Fix Released
--
Cannot install version libbrasero-media0_2.26.0 because of nautilus-cd-burner
already installed !
Please note also that this conflict appears on the initial installation
of ubuntu (in my case, using the alternate install CD on a ps3).
Proposed debdiff looks good (thanks Philippe), two conflicting packages
in the same meta package are obviously wrong.
--
Cannot install version
@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
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
/275492
You received this bug notification because you are a direct subscriber
of the bug.
--
Arnaud Jeansen
arnaud.jean...@gmail.com
--
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
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
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
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
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 module
main()
File /usr/share/games/monsterz/monsterz.py, line 1993, in main
13 matches
Mail list logo
