Why is Deluge using /dev/snd/timer
Posted: Fri Jun 20, 2008 12:02 pm
I have the problem that occasionally my sound stops working. Then I scan for files blocking the sound device and usually Deluge is in the list.
Just now video wouldn't work because sound was blocked so I did "lsof | grep snd" and that is what I get:
deluge 6915 <user> 77r CHR 116,33 11232 /dev/snd/timer
deluge 6915 <user> 78u CHR 116,16 11409 /dev/snd/pcmC0D0p
Why is Deluge accessing /dev/snd/timer and /dev/snd/pcmC0D0p?
Is there any reason why Deluge should access sound on Linux? I don't have any sound settings made. There are no audio signals as far as I can tell.
Since my last posts about this topic were ignored I'd really like someone of the dev team to adress this. Why is Deluge accessing sound? What for? How can I stop it? I love the client but it's these little annoyances that keep it from being in my favorite applications list.
I use Deluge 0.5.9.2 on Ubuntu Hardy with Kernel 2.6.24-19-generic
Just now video wouldn't work because sound was blocked so I did "lsof | grep snd" and that is what I get:
deluge 6915 <user> 77r CHR 116,33 11232 /dev/snd/timer
deluge 6915 <user> 78u CHR 116,16 11409 /dev/snd/pcmC0D0p
Why is Deluge accessing /dev/snd/timer and /dev/snd/pcmC0D0p?
Is there any reason why Deluge should access sound on Linux? I don't have any sound settings made. There are no audio signals as far as I can tell.
Since my last posts about this topic were ignored I'd really like someone of the dev team to adress this. Why is Deluge accessing sound? What for? How can I stop it? I love the client but it's these little annoyances that keep it from being in my favorite applications list.
I use Deluge 0.5.9.2 on Ubuntu Hardy with Kernel 2.6.24-19-generic