-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
package: x2gothinclient version: 1.1.0.2
Hi,
when starting x2goclient in thinclient mode, pulseaudio gets started in the background. This blocks remote audio when using the RDP-DirectConnect feature of x2goclient.
When you do this:
/etc/init.d/x2gothinclient stop X & export DISPLAY=:0 ln -s /etc/x2go/x2gothinclient_sessions ~/.x2goclient/sessions x2goclient --thinclient
sound in an RDP-DirectConnect session works. So the Pulseaudio start takes place somewhere else - x2gothinclientd maybe? - and needs to be stopped for RDP-DirectConnect, as it blocks the audio device.
How that can be accomplished, without killing sound support for regular X2Go sessions, I don't know.
Who was the one that originally asked for the RDP-DirectConnect feature? How do they handle sound, or do they not need it?
- -Stefan
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJVQK63AAoJEG7d9BjNvlEZ6b0H/iTF1zdILPaKCeQQScTEtMbX 1SmJK2FyZa5O0ygvc/sGCjKo5KqgHIBCgBD477BJlYCpkcKQM71Sw+q2mYQIwnBN C9lbspvHa9WXEdTzQ1reeqk3jKGA2AMrBnhYLBqhxSFJxJLmqwYudyXMIWnZrH5j q15vKGYDnizu3eSGvDF2MG0r8eh5ioq5xlCwih1GTnCf9PCz05b2Au90ziGKn8Lx dzVZHtKQWOv36i/V2QLVgMQkFrAbPakXjYFekmkwPNL7w298s3GpC0sKiJTIJVLw QEm+2k7Iso1eMMcVW3KaOoE3B38j6dKaTYFzrJfx15KkUowHu1UxzjozXaWZjNQ= =JlfK -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Additional info:
Sound via RDP works when:
a) Pulseaudio is not running
*and*
b.1) rdesktop is called with: -r sound:local -f -u DOMAIN\\User -p Password Server:3389
*or*
b.2) xfreerdp is called with:
--ignore-certificate --plugin rdpsnd -d DOMAIN -f -u User
-p Password Server:3389
It doesn't matter if b.1) or b.2) is used on the command line with X and export DISPLAY=:0, or through an x2goclient with the corresponding session parameters.
- -Stefan
Am 29.04.2015 um 12:13 schrieb Stefan Baur:
package: x2gothinclient version: 1.1.0.2
Hi,
when starting x2goclient in thinclient mode, pulseaudio gets started in the background. This blocks remote audio when using the RDP-DirectConnect feature of x2goclient.
When you do this:
/etc/init.d/x2gothinclient stop X & export DISPLAY=:0 ln -s /etc/x2go/x2gothinclient_sessions ~/.x2goclient/sessions x2goclient --thinclient
sound in an RDP-DirectConnect session works. So the Pulseaudio start takes place somewhere else - x2gothinclientd maybe? - and needs to be stopped for RDP-DirectConnect, as it blocks the audio device.
How that can be accomplished, without killing sound support for regular X2Go sessions, I don't know.
Who was the one that originally asked for the RDP-DirectConnect feature? How do they handle sound, or do they not need it?
-Stefan
_______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJVQLWWAAoJEG7d9BjNvlEZBc0H/AqKJcTdCRVr69Gy7T5MdCdQ me90sq2ppqGShiPpJRFfd4J/1cnUN5rZJbJ9F7Hrvu1TEuQH1AU/hRtPWiWQqsXd pwBHqc2jg4tCYzWZADCltjGYAkwtpGc5Gz5XLJHC7A9MuXW7M4R2JmRcrsvRZXj1 dbSKzUZlC3q7Xde9xDRbEe3z2+2Tuq5V92dwZhxf7SvhPQPhxhLnBq6XUdPPINgW mM98GTzTx/krnY+2JrOwI5V3WzqJOJNp9mN0k4QBPLzXbOfnQit3GifFMpPYuVDA 1E8BoTBSRE4m/TEi452Losifbq0vLYR+SJZnBtnBKWC8jZ5i+Gp3oxtuPv/6b3Q= =DoVJ -----END PGP SIGNATURE-----
-
Stefan Baur