'Twas brillig, and Brian J. Murrell at 12/12/08 12:35 did gyre and gimble: > On Fri, 2008-12-12 at 13:17 +0100, Lennart Poettering wrote: >> On Thu, 11.12.08 22:48, Brian J. Murrell (brian at interlinx.bc.ca) wrote: >> >>> I've noticed a number of times on my Ubuntu Intrepid machine that Pidgin >>> seems to get it's pulseaudio connection hung up. Normally I only see a >>> listing in the Volume Control applet for pidgin for the brief time it >>> takes to send whatever short sound alert it wants to send. >>> >>> Every now and then though I will see an entry in it for Pidgin that >>> doesn't go away, yet there is no currently playing sound and no more >>> sounds will come through from pidgin until I restart it, to release the >>> hung up stream. >>> >>> Anyone seen this or know why it happens, or if there is a less intrusive >>> way than restarting pidgin, to have it's stream reset? Terminate Stream >>> will make it go away, but pulseaudio will still not receive (or play) >>> any more sounds from pidgin until it's restarted. >> I am note sure how pidgin plays event sounds these days. > > I think this is what you want: > > $ grep Pidgin ~/.pulse/volume-restore.table > pulsecore/protocol-native.c$Pidgin > > Or maybe this is much more useful: It's kinda hard to tell from that how it works internally... you'd really need to look at the pidgin code, but as Lennart said (seems obvious now he said it!) Pidgin should use libcanberra... Not sure what that means from a cross platform perspective tho'... I'm not sure libcanberra works on windows yet... Lennart? Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
