[X2Go-User] Redirect only specific sound devices?
Buddy Butterfly
buddy.butterfly at web.de
Sat Aug 24 15:50:45 CEST 2013
Hi Mike,
sorted it out. So, if someone is interested, here is how to do
it. I tested it on Kubuntu 12.10.
On Ubuntu, pulse is in session mode by default. This means, it
obviously starts an instance per session. This is why I could
not see any devices when unsetting PULSE_CLIENTCONFIG. So,
to make it work, pulse has to be started system wide at boot.
Background on how to do it:
http://rudd-o.com/linux-and-free-software/how-to-make-pulseaudio-run-once-at-boot-for-all-your-users
What I did:
1. In /etc/init/pulseaudio.conf
activate the line
start on runlevel [2345]"
which is commented out by default.
2. In /etc/pulse/client.conf set
default-server = /var/run/pulse/native
autospawn = no
3. Place the users that should have sound into group "pulse-access".
4. Reboot.
Only drawback is that KDE does not show the devices in system settings
anymore when natively using the system. But sound in KDE is working
perfekt. Devices can be seen with KMIX and outputs can also be
redirected (select output streams, right click on the currently playing
stream and choose move to....).
When you now connect via x2go everything is fine and the sound
gets redirected to the local system. But you can now start voip and
other programs to use the local sound devices with unsetting
$PULSE_CLIENTCONFIG beforehand. Example running in konsole:
unset PULSE_CLIENTCONFIG
jitsi
Runs jitis with the local sound devices. It can be configured to use
usb sound card of a headset directly, etc.
Cheers,
Matt
Am 20.08.2013 12:38, schrieb Buddy Butterfly:
>
> 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
>>
>>
>>
>>
>>
>
>
More information about the x2go-user
mailing list