I think everything is linked with the fact I try not to use a windows manager, but I'm even not sure pulseaudio can deal with several simultenous users.
Any advices/ideas would be really appreciated. Maybe I'm misinterpreting your statement, but if you don't want to run a window manager on the server side, you should be running one locally, and you have to take care of starting pulseaudio on the client as well. Well that's rather true even if you can launch an application that supports it directly through xinit without any window manager. But in my case, I remembered an old post advising using a minimal window manager with Rpi: matchbox. Rpi is so slow with a classical desktop manager.
The reason I use x2go is :
- X compression
- should work out of the box
But I also like to understand what is in the engine. After a long reading and looking in the code yesterday I understood I was wrong regarding what is client and server for X and pulseaudio.
For pulseaudio the server is my Rpi, so that's here I need to launch start-pulseaudio-x11. As far as I understand, it will add X properties to the X communication between my client (the Rpi) and the application server.
I still don't fully understand how it works after you push ssh -X aaaa@bbbb.cccc /usr/bin/iceweasel. It looks it starts iceweasel on the application server. Iceweasel being pulseaudio compliant (it has a client inside), it gets those X properties from the Rpi and understand it has to send it's data to the pulseaudio server on the Rpi. I'm maybe wrong, but pulseaudio server seems useless on the application server as long as applications have a pulseaudio client "inside".
So, with this script launch from xinit in the Rpi, I should hear a sound on the Rpi (I say I should because I can't try it right now):
# Start pulseaudio (or check it's allready started) with X11 support start-pulseaudio-x11 # Leave machines in the local IP network connect to the Rpi pulseaudio server pactl load-module module-native-protocol-tcp auth-ip-acl=your_local_network_IP # Start an ssh X session asking to just play a sound ssh -X aaaa@bbbb.cccc paplay /usr/share/sounds/beep.wav
And for x2goclient, this should do the trick:
# Help application that need information regarding the window matchbox-window-manager & # Start pulseaudio (or check it's allready started) with X11 support start-pulseaudio-x11 # Start x2go (session launch will load necessary pulseaudio modules) x2goclient --maximize
Regards, EG