Hi Mike, thanks a lot for the hint. I think this is the right point to get grip at. Unfortunately it does not work. After unsetting, simply, there are no devices at all.
And as I saw, the whole KDE sound is configured as a client of the sound server of the local machine (running x2goclient). Maybe we have to start a separate pulse instance on the system? Any clue on how to do this? Cheers, Matt Am 20.08.2013 08:19, schrieb Mike Gabriel: > Hi Buddy, > > On Mo 19 Aug 2013 17:09:20 CEST Buddy Butterfly wrote: > >> for a headless system I am trying to run a headset >> locally on it. For operation I have used x2go which >> works perfect, even for sound. So this solved the >> headache with KVM ;-). >> >> Now I would like to use a headset locally on the headless >> system which is connected via USB and its own usb sound >> card (Logitech, works always perfect!). I am unable to >> get the headset to work while being connected to via x2go. >> Headset should be primarily for voip. >> >> So, how I could use this headset? Is it possible to configure >> somehwere that not all sound devices should be redirected but >> only specific ones? With this I could try to leave out the >> headset sound card. > > Easiest probably would be to unset the ENV variable PULSE_CLIENTCONFIG > before starting your VoIP application... > > """ (wrapper script untested) > #!/bin/bash > > unset PULSE_CLIENTCONFIG > ekiga > """ > > Sort of like this... > > Mike > > > > > _______________________________________________ X2Go-User mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-user
