USB sound

Basil Chupin blchupin at
Sat Oct 5 03:12:30 UTC 2013

On 05/10/13 08:14, Ric Moore wrote:
> On 10/04/2013 08:48 AM, R Kimber wrote:
>> On Thu, 03 Oct 2013 23:49:03 -0400
>> Ric Moore wrote:
>>>> I've been having problems with UBS sound for some time (it used to 
>>>> work
>>>> about 6 months ago). I find that any USB sound device that I 
>>>> connect is
>>>> not recognised, and is not listed by aplay -l
>>> sudo apt-get install pavucontrol
>>> Then open it. Under the playback tab you select the device you want to
>>> play back through from a drop down selection of all the audio devices
>>> your system sees. I switch between my USB headset and my 6.1 sound 
>>> systm
>>> all the time using that. I use the headset to not bother other's
>>> sleeping. Or, I can blow the cat out the window with 6.1. pavucontrol
>>> SHOULD be installed during the install process, but it's not. Go 
>>> figure.
>>> Ric
>> Thanks, but pavucontrol gives:-
>> Error: unable to connect to pulseaudio: OK
>> I should explain that in attempting to resolve this issue I have made 
>> many
>> changes, including disabling pulseaudio.  None of the changes worked.  I
>> then purged alsa-base, pulseaudio, and pavucontrol, and then 
>> re-installed
>> them.  This has made no difference, and pulseaudio remains disabled,
>> although I reversed the changes that I made previously, and anyway 
>> purging
>> should have removed any changed settings.
>> All the relevant modules seem to be loaded OK, including snd_usb_audio.
> Methinks if you had pavucontrol installed first, before taking a 
> hammer to everything, you might have had a chance to be listening to 
> your tunes. Even a complete purge doesn't always remove all config 
> files. Maybe look to see if you have any ~/.alsa config 
> files/directories still lying around, or ~/.asound. rm them with great 
> prejudice. Something is telling it not to work/start.
> It might be easier to re-install cleanly, which I have had to do from 
> some of my own 'hammering round pegs into square holes" sessions. Heh, 
> I've done that more than once! Or, just for grins, create a new user 
> and test my theory, unless you blew something up system wide.
> You might just go into /etc/init.d/ and type ./pulseaudio start
>     to see what error messages you see. But, if you're like me, you 
> blew it up real good. :) Ric

Or you could open a terminal and run the file on the command line. Doing 
so will show an error message showing what caused it to fail to run.


Using openSUSE 13.1, KDE 4.11.2 & kernel 3.11.3-1 on a system with-
AMD FX 8-core 3.6/4.2GHz processor
16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM
Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU

More information about the ubuntu-users mailing list