Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played
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
Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played
On Mon, Feb 11, 2013 at 05:23:01PM +0100, Martin Teufel wrote: > My problem with the situation: What _if_ aplay plays correctly all the > time, but in psi it breaks the sound after a while? > (At the moment, for me, it seems to be the case.) 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
Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played
Hi Jan, > Psi just calls an external program to play sounds. You can configure > the command to use in general/options/sound/player. that's interesting, but makes sense. > Do you have a player manually configured? No, I don't have a player configured manually. The configuration is empty. > If the configuration is empty, psi autodetects if it should use "play" > or "aplay". (aplay in case /proc/asound exists, play otherwise). Yes, /proc/asound/ exists. It should use aplay then, assuming you're right. > Does the same problem occur if you play sounds by manually calling > 'aplay' (or 'play')? I'm testing it at the moment, but not so far. My problem with the situation: What _if_ aplay plays correctly all the time, but in psi it breaks the sound after a while? (At the moment, for me, it seems to be the case.) Best regards, Martin On Mon, Feb 11, 2013 at 04:39:57PM +0100, Jan Niehusmann wrote: > Psi just calls an external program to play sounds. You can configure the > command to use in general/options/sound/player. > > If the configuration is empty, psi autodetects if it should use "play" > or "aplay". (aplay in case /proc/asound exists, play otherwise). > > In any case, I don't see how the behaviour you describe could be a psi > bug. (Of course, I could be wrong.) > > Do you have a player manually configured? > > Does the same problem occur if you play sounds by manually calling > 'aplay' (or 'play')? > > Regards, > Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played
Hi Martin, On Sat, Feb 02, 2013 at 02:22:07PM +0100, Martin Teufel wrote: > After some sound-notifications were played, the sounddevice somehow > breaks. I.e. no more sounds are played (of course psi tries to) and I > can't output any sound/music at all (e.g. with mplayer or something). Psi just calls an external program to play sounds. You can configure the command to use in general/options/sound/player. If the configuration is empty, psi autodetects if it should use "play" or "aplay". (aplay in case /proc/asound exists, play otherwise). In any case, I don't see how the behaviour you describe could be a psi bug. (Of course, I could be wrong.) Do you have a player manually configured? Does the same problem occur if you play sounds by manually calling 'aplay' (or 'play')? Regards, Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played
Package: psi Version: 0.14-2 Severity: important Tags: upstream After some sound-notifications were played, the sounddevice somehow breaks. I.e. no more sounds are played (of course psi tries to) and I can't output any sound/music at all (e.g. with mplayer or something). Please feel free to mail me if I may help finding the cause. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.38-bpo.2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages psi depends on: ii libaspell15 0.60.6-4 GNU Aspell spell-checker runtime l ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libqca2 2.0.2-1libraries for the Qt Cryptographic ii libqca2-plugin-ossl 0.1~20070904-4 QCA OSSL plugin for libqca2 ii libqt4-dbus 4:4.6.3-4+squeeze1 Qt 4 D-Bus module ii libqt4-network4:4.6.3-4+squeeze1 Qt 4 network module ii libqt4-qt3support 4:4.6.3-4+squeeze1 Qt 3 compatibility library for Qt ii libqt4-xml4:4.6.3-4+squeeze1 Qt 4 XML module ii libqtcore44:4.6.3-4+squeeze1 Qt 4 core module ii libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module ii libstdc++64.4.5-8The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-4 X11 client-side library ii libxss1 1:1.2.0-2 X11 Screen Saver extension library ii zlib1g1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages psi recommends: ii sox 14.3.1-1 Swiss army knife of sound processi Versions of packages psi suggests: ii libqca2-plugin-gnupg 2.0.0~beta3-1 QCA gnupg plugin for libqca2 pn psi-translations (no description available) ii xdg-utils1.0.2+cvs20100307-2 desktop integration utilities from -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
