[Bug 492054] Re: No sound after randomsound is started

2014-10-27 Thread GDR!
I don't think this is happening any more, there's a different problem instead: #590780 - but this one doesn't happen (to me) in 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/492054 Title: No

[Bug 492054] Re: No sound after randomsound is started

2010-05-08 Thread A.Kromic
i have exactly the same problem - randomsound prevents pulseaudio from detecting the sound device. Here is what happens: % sudo fuser -v /dev/snd/* USERPID ACCESS COMMAND /dev/snd/controlC0: root 2010 F arecord arn

[Bug 492054] Re: No sound after randomsound is started

2009-12-08 Thread Daniel T Chen
Do you have an /etc/asound.conf or/and ~/.asoundrc* ? If so, please attach its/their contents. -- No sound after randomsound is started https://bugs.launchpad.net/bugs/492054 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bug

[Bug 492054] Re: No sound after randomsound is started

2009-12-08 Thread Daniel T Chen
This symptom is due to random sound grabbing the raw hw:, which blocks for nearly all modern sound devices driven by ALSA due to lack of support for multiopen. ** Changed in: randomsound (Ubuntu) Importance: Undecided => Low ** Changed in: randomsound (Ubuntu) Status: New => Confirmed

[Bug 492054] Re: No sound after randomsound is started

2009-12-03 Thread David MarĂ­n
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/36401982/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/36401983/XsessionErrors.txt -- No sound after randomsound is started https://bugs.launchpad.net/bugs/492054 You received