Hello Jan, thank you for the hint. It is indeed a concurrency problem. I got the problem once again and had a look at my process list. There were two instances of aplay running, blocking the sounddevice. Sending them SIGTERM solved the problem / freed it again.
Remains the question why sometimes an aplay process does not terminate well... So it may still be a bug. Regards, Martin On Mon, Feb 11, 2013 at 05:50:40PM +0100, Jan Niehusmann wrote: > Maybe some kind of concurrency problem? Psi may call aplay again while > an earlier instance is still running. > > Regards, > Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
