Bug#440852: daemon fails to start if sound/mixer device is open

2009-07-16 Thread Joost Yervante Damad
On Sunday 07 June 2009 11:42:01 Nicolas Kratz wrote: > Hello, > > I just hit bug [1] on my sid box when installing timidity 2.13.2-25. In > my case, iceweasel, running as my normal user, kept the sound device > open, I assume via the flash plugin. Closed the browser -> daemon started. > > My .asoun

Bug#440852: daemon fails to start if sound/mixer device is open

2009-06-07 Thread Nicolas Kratz
Hello, I just hit bug [1] on my sid box when installing timidity 2.13.2-25. In my case, iceweasel, running as my normal user, kept the sound device open, I assume via the flash plugin. Closed the browser -> daemon started. My .asoundrc is attached, there is no /etc/asound*, and my sound card

Bug#440852: daemon fails to start if sound/mixer device is open

2009-05-09 Thread Joost Yervante Damad
Hi Simon, is this [1] still an issue for you? Thanks, Joost [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440852 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#440852: daemon fails to start if sound/mixer device is open

2007-09-08 Thread Joost Yervante Damad
> It is a problem for timidity mainly because system upgrades should never > fail because an user has a particular program open, even if mplayer > could be more cooperative here. It might be interesting to get some > input from the ALSA folks. Yeah... it does not happen on both of my boxes. What k

Bug#440852: daemon fails to start if sound/mixer device is open

2007-09-06 Thread Simon Richter
Hello, Joost Yervante Damad wrote: Can you verify if you can play any other sound when mplayer is running? Yes, that works, as does starting mplayer after timidity is already running. Can you verify if it happens always or sporadically? The problem is always reproducible with the descri

Bug#440852: daemon fails to start if sound/mixer device is open

2007-09-06 Thread Joost Yervante Damad
On Thursday 06 September 2007 21:22:16 Simon Richter wrote: > Hi, > > Joost Yervante Damad wrote: > > On Tuesday 04 September 2007 22:40:40 Simon Richter wrote: > >> ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave > >> > >> This is probably related to the instance of mplayer that w

Bug#440852: daemon fails to start if sound/mixer device is open

2007-09-06 Thread Simon Richter
Hi, Joost Yervante Damad wrote: On Tuesday 04 September 2007 22:40:40 Simon Richter wrote: ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave This is probably related to the instance of mplayer that was open at this time (running as a user). Can you verify if you can play

Bug#440852: daemon fails to start if sound/mixer device is open

2007-09-05 Thread Joost Yervante Damad
On Tuesday 04 September 2007 22:40:40 Simon Richter wrote: > ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave > > This is probably related to the instance of mplayer that was open at > this time (running as a user). Can you verify if you can play any other sound when mplayer is run

Bug#440852: daemon fails to start if sound/mixer device is open

2007-09-04 Thread Simon Richter
Package: timidity Version: 2.13.2-15 Severity: minor Hi, I'm running timidity in daemon mode, and the last upgrade failed with the message ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave This is probably related to the instance of mplayer that was open at this time (running as