On Sat, Mar 14, 2009 at 09:12:06PM -0400, Jan Muszynski wrote: > Not quite as bad as I previously stated. I had a setting wrong in > adacious and it does work in 14-2 using the pulseaudio interface. > However the ESD interface is dead in 14.2 across the board.
The biggest change in -2 was the move to per-user esound socket, if your installed esound was still trying to use a global one that would have caused the issue. > The Tests also fail for alsa and oss in 14-1. Since Pulse is > controlling everything I suspect that this part makes sense. So > perhaps this bug should really be against the esound-compat plugin. Yes, everything should go through pulseaudio which is the only application directly accessing your sound card. http://pulseaudio.org/wiki/PerfectSetup has information on how to set this up correctly. > One additional data point. In Pulse Audio Manager, in the Client tab, > both 14-1 and 14-2 list a Console Kit Session, a XSMP session, and a > Pilse Audio Manager Session. However that's ALL that 14-2 gas. 14-1 > though also has about 19 entries for "EsounD Client (Unix socket > client)". 14-2 has none. The sample Cache tab for 14-1 has a number of > entries for different esound.gtk-events-2/<system sound>. 14-2 is > empty. All the other tabs in Pulse Audio Manager appear to be > identical. That would be explained by your esound not working. Closing this bug as it doesn't seem to be a pulseaudio one, if it still occurs with recent versions of esound please reopen it. Sjoerd -- The more you complain, the longer God lets you live. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
