Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2006-05-14 Thread Francesco Poli
On Sun, 14 May 2006 02:40:03 +0200 Aurelien Jarno wrote: Hi, This bug has been reported long time ago and I am not able to reproduce it here. New versions of libsdl1.2 have been uploaded since then. Could you please give a try with the latest version in sid and tell me if the bug is still

Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2006-05-13 Thread Aurelien Jarno
Hi, This bug has been reported long time ago and I am not able to reproduce it here. New versions of libsdl1.2 have been uploaded since then. Could you please give a try with the latest version in sid and tell me if the bug is still present ? Thanks, Aurelien -- .''`. Aurelien Jarno

Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2005-07-30 Thread Francesco Poli
On Tue, 19 Jul 2005 01:35:03 +0200 Moritz Muehlenhoff wrote: If you mean simply issuing 'aptitude install libsdl1.2debian-all' as root (thus removing the conflicting libsdl1.2debian-oss), it would be an easy test, I would say (are there any side-effects, assuming I do not touch the

Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2005-07-18 Thread Moritz Muehlenhoff
Francesco Poli wrote: Which libsdl1.2debian variant are you using? Are you possibly using -oss? You guessed! :-o $ aptitude search libsdl1.2debian i libsdl1.2debian - Simple DirectMedia Layer p libsdl1.2debian-all - Simple DirectMedia Layer (with

Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2005-07-15 Thread Elias Kunnas
Hello, I had similar behavior with prboom, only that it has not crashed once but hung in a few seconds every time of starting it, and if it was fullscreen, made it necessary to restart X. I found out using -nosound made it work properly so it looks like a problem with audio. I'm using SDL ALSA

Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2005-07-12 Thread Moritz Muehlenhoff
severity 315722 important thanks [Sorry for the late reply, I've been busy lately] Which libsdl1.2debian variant are you using? Are you possibly using -oss? If so, could you please try it with -alsa or -all? Second test: I ran sarge prboom inside gdb and was astonished. Inside gdb, prboom

Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2005-07-12 Thread Francesco Poli
On Tue, 12 Jul 2005 11:42:09 +0200 Moritz Muehlenhoff wrote: [...] [Sorry for the late reply, I've been busy lately] That's no problem! :) Which libsdl1.2debian variant are you using? Are you possibly using -oss? You guessed! :-o $ aptitude search libsdl1.2debian i libsdl1.2debian

Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2005-06-25 Thread Francesco Poli
Package: prboom Version: 2:2.2.6-2 Severity: grave Justification: renders package unusable I recently upgraded from woody (oldstable) to sarge (stable) and now I cannot play freedoom anymore. When launched from a terminal under X11, prboom loads freedoom's `doom2.wad' and starts the game. I

Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2005-06-25 Thread Moritz Muehlenhoff
Francesco Poli wrote: Package: prboom Version: 2:2.2.6-2 Severity: grave Justification: renders package unusable I recently upgraded from woody (oldstable) to sarge (stable) and now I cannot play freedoom anymore. This seems like a system specific issue, I can't reproduce this problem on

Bug#315722: prboom: randomly gets signal 11 after a very very short playing time

2005-06-25 Thread Francesco Poli
On Sat, 25 Jun 2005 15:06:05 +0200 Moritz Muehlenhoff wrote: Can you run prboom with catchsegv please or send a backtrace from gdb? (Preferably with enabled debug symbols) I tried hard to do so, but still no luck... :-( What I did: ___ First test: I used catchsegv on sarge prboom,