Hi community,
I'm trying to achieve this: build a Firefox/Iceweasel application server (Debian Wheezy) with several simultaneous clients using Raspberry Pi (Raspbian) using x2go, everything being in a LAN. Of course each user needs to hears just its own application sound. I don't want to send a full desktop manager as I just want them to use Firefox/Iceweasel.
As of now, I don't have too much trouble to start Firefox/Iceweasel from clients. Only troubles I get are :
- the size of the Firefox window doesn't manage to get the local screensize despite I tick "Fullscreen" in x2go, so I must use --heigth and --width command line parameter
- menu at the top doesn't work ether
- no sound at all
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.
Best regards, EG
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 07.10.2014 um 15:32 schrieb Edouard Gaulué:
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.
All I can add is that in general, pulseaudio sound between a Windows client and an x86-based Debian Wheezy works fine, even with published applications and multiple users. So it is most likely an issue with your particular setup.
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.
You could do any of the following, IMO:
- Run a remote desktop environment and set the rights on the *.desktop files in a way that the users you want to let in via X2Go can only access Firefox and the Logoff menu item.
- Run a local desktop environment/window manager, possibly with some manual configuration for pulseaudio.
- run https://github.com/alandmoore/KiLauncher on the server and specify the allowed apps there.
Note that as long as users can define their own sessions, there's nothing that stops them from specifying another application unless you removed access rights on the particular executable on the server. So don't think of published applications as a security feature, they are not.
- -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.0.22 (MingW32)
iQEcBAEBAgAGBQJUNDSjAAoJEG7d9BjNvlEZaEIH/1JpjyfNLk2X2sCM4gtZzUJX jJOoZQKnXhA09H9SKPPZRy1N1wcAc4tFeHQpzIgAGrT94znGqkIPeHwLsEeCvVNk FvSgJFXjkcGldDWBUvCtrOh4hgbZaqeCNz6SGjUu1awg16fOZt06Bz2QktTYbMPb k5LYsAp/Afb9ch99lWh+a+ip+O8KuHB4p99h2irKxeY/uqSZqvZ5N7X8lA+qgC8/ +DWff9eVOdxMzKN6tuhsVyMI/SSBObDbYiGfL6VlCILA1n3p/YXbWJItjiR8O2LK eqn1kjf4aXuIl7BK3A2Q9uOY1N0xzQSNTVMH7mJ7rDFxmSzV43WWk3MxW/unKYs= =HhwH -----END PGP SIGNATURE-----
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
-
Edouard Gaulué -
Stefan Baur