On Mon, Jan 22, 2007 at 10:06:03AM +0200, Eddy Petrișor wrote: > > On Sat, Jan 20, 2007 at 08:39:20AM +0200, Eddy Petrişor wrote: > >> This behaviour can be reliably reproduced on my system with this > >> sequence:
> >> 1) make sure there is no running instance of the player: > >> [EMAIL PROTECTED] ~ $ killall beep-media-player > >> beep-media-player: no process killed > >> 2) start the player: > >> [EMAIL PROTECTED] ~ $ beep-media-player > >> 3) start playing a song and close the player while is playing (through > >> the graphical interface) - this will result in music still being played > >> - BUG! > >> 4) CTRL+Z in the console > > Definitely not reproducible here. When I click the X in the corner of the > > GUI, the process exits. Likewise if I choose 'quit' from the menu. > What arch? I am using amd64 (on an Intel Core 2 Duo). I was testing on i386. I've now just tested on amd64 (remote displaying to i386). Still not reproducible. > >> Because it causes unexpected behaviour (doesn't die when it should > >> terminate) and thus occupies memory making unrelated software not start > >> I think this is bug should be critical. > >> Even if the bug is downgraded (is at least important), Etch should not > >> ship the software in such a broken state. > > Even if this bug was reproducible, I don't see how a process not exiting > > should ever be critical. > As I said, unrelated software do not start since they are killed by the kernel > due to lack of resources (taken by the running instances of bmp "running" in > the background). Yes, I understand what you said the *problem* it caused was, but that doesn't sound critical to me at all. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
