Hello list, greetings! I have the following setup runing: A docker-container providing a rudimental desktop (fluxbox on debian) A Win7PC which gets the desktop using x2Go.
All is working as expected but the pulseaudio server on the win7-client doesn't start automatically. If I use an external pulseaudio.exe with an lightly modified default.pa the pulseaudio-sever starts. After that "trick" I have to edit .pulse-client.conf in my docker-container for sending audio to my win7-pulseserver and it will work. The drawback is: I cannot use the ssh-tunnel from x2go for the audio ... it is not established cause of the missing port of the not startet "internal" pulseserver.
Is there a chance to give an modified default.pa to the "internal" pulseaudio-server of the x2go-client or even better: is it possible to use an "external" pulseaudio.exe with the x2go-client?
The next "problem" for an automated workaround (starting pulseaudio with script prior to the x2go-client) is, that the x2go-client seems to use port 4714 for untunneled connections. Does someone now the parameter for changing the pulseaudio-serverport from 4713 to 4714 for the pulse-audio-windows-version 1.1? This is the most "dirty" hack ... but should do the work in this case. The other way round is of course although possible: change the port the x2go-client expects his "internal" server. This way the .pulse-client.conf in the docker-desktop would be build correct for this szenario.
Maye someone point me the direction? Uhhh ... its long ago I have written text in english Have a nice day!! _______________________________________________ x2go-user mailing list [email protected] http://lists.x2go.org/listinfo/x2go-user
