Hi all,
I'm trying to (re)migrate our thin clients (Intel Atom 1.6 GHz) from plain X11/XDMCP to x2go again using the latestet Debian Packages (Squeeze).
First of all I wonder about the recommended compression mode and level. With link type LAN and compression nopack I experience heavy CPU usage on the (thin) client side (20% Xorg and 30% x2goclient) while reading mails and even more latency than I experienced with plain X11 before.
Furthermore sound forwarding does not work even though it is active in the session setup.
pulseaudio configuration and cookie has been set:
$ export |grep PULSE declare -x PULSE_CLIENTCONFIG="/home/michael/.x2go/C-michael-53-1320436144_stDGNOME_dp16/.pulse-client.conf" $ cat $PULSE_CLIENTCONFIG default-server=localhost:30002 cookie-file=.x2go/C-michael-53-1320436144_stDGNOME_dp16/.pulse-cookie
x2go seems to bind to some ports, 30002, too:
# netstat -tupen |grep 1004 tcp 0 8 127.0.0.1:38073 127.0.0.1:30001 ESTABLISHED 1004 3080993 18624/sshd: michael tcp 0 0 127.0.0.1:38338 127.0.0.1:30002 ESTABLISHED 1004 3083062 19032/gnome-volume- tcp 0 0 127.0.0.1:30001 127.0.0.1:38073 ESTABLISHED 1004 3080994 18815/x2goagent tcp 0 0 127.0.0.1:30002 127.0.0.1:38338 ESTABLISHED 1004 3083063 18887/sshd: michael
But this is what paplay tells when invoked from a terminal inside the x2go session:
$ paplay -v /usr/share/sounds/KDE_Startup_new.wav Opening a playback stream with sample specification 's16le 2ch 22050Hz' and channel map 'front-left,front-right'. Connection established. Stream error: No such entity
Thanks in advance
Michael
-- EDV-Serviceteam Annika & Michael Hierweck GbR Egerstraße 53, 44225 Dortmund (Germany) http://www.edv-serviceteam.net
On Fri, 2011-11-04 at 21:24 +0100, Michael Hierweck wrote:
Hi all,
I'm trying to (re)migrate our thin clients (Intel Atom 1.6 GHz) from plain X11/XDMCP to x2go again using the latestet Debian Packages (Squeeze).
First of all I wonder about the recommended compression mode and level. With link type LAN and compression nopack I experience heavy CPU usage on the (thin) client side (20% Xorg and 30% x2goclient) while reading mails and even more latency than I experienced with plain X11 before.
Furthermore sound forwarding does not work even though it is active in the session setup.
pulseaudio configuration and cookie has been set:
$ export |grep PULSE declare -x PULSE_CLIENTCONFIG="/home/michael/.x2go/C-michael-53-1320436144_stDGNOME_dp16/.pulse-client.conf" $ cat $PULSE_CLIENTCONFIG default-server=localhost:30002 cookie-file=.x2go/C-michael-53-1320436144_stDGNOME_dp16/.pulse-cookie
x2go seems to bind to some ports, 30002, too:
# netstat -tupen |grep 1004 tcp 0 8 127.0.0.1:38073 127.0.0.1:30001 ESTABLISHED 1004 3080993 18624/sshd: michael tcp 0 0 127.0.0.1:38338 127.0.0.1:30002 ESTABLISHED 1004 3083062 19032/gnome-volume- tcp 0 0 127.0.0.1:30001 127.0.0.1:38073 ESTABLISHED 1004 3080994 18815/x2goagent tcp 0 0 127.0.0.1:30002 127.0.0.1:38338 ESTABLISHED 1004 3083063 18887/sshd: michael
But this is what paplay tells when invoked from a terminal inside the x2go session:
$ paplay -v /usr/share/sounds/KDE_Startup_new.wav Opening a playback stream with sample specification 's16le 2ch 22050Hz' and channel map 'front-left,front-right'. Connection established. Stream error: No such entity
Thanks in advance
Michael
Hello, Michael. We have found 16m-png-jpeg to give the best combination of clarity and performance in our environment.
The 30000 series ports are from ssh port redirection which X2Go uses to bring back the sound, printing, and local mounts. Hope that helps - John
Hi John,
On 04.11.2011 22:56, John A. Sullivan III wrote:
Hello, Michael. We have found 16m-png-jpeg to give the best combination of clarity and performance in our environment.
sadly any png or jpeg compression leads to wrong colors for transparent images in Firefox/Iceweasel. For example the Google logo gets acyan background. I switched to rle compression which reduced latency but it's still worse than plain X11.
The 30000 series ports are from ssh port redirection which X2Go uses to bring back the sound, printing, and local mounts. Hope that helps -
All pulseaudio sinks seem to be missing when using x2go. I attached tthe output of "pactl list" from within a x2go session.
Michael
-- EDV-Serviceteam Annika & Michael Hierweck GbR Egerstraße 53, 44225 Dortmund (Germany) http://www.edv-serviceteam.net
Hi all,
I was able solve the problem related to sound.
The user "x2goclient" needs to be a member of the "audio" group on the thin client.
Michael
-- EDV-Serviceteam Annika & Michael Hierweck GbR Egerstraße 53, 44225 Dortmund (Germany) http://www.edv-serviceteam.net
----- Original Message ----- From: "Michael Hierweck" <team@edv-serviceteam.net> To: x2go-user@lists.berlios.de Sent: Saturday, November 5, 2011 5:11:49 AM Subject: Re: [X2go-User] x2gothinclient: compression and sound
Hi John,
On 04.11.2011 22:56, John A. Sullivan III wrote:
Hello, Michael. We have found 16m-png-jpeg to give the best combination of clarity and performance in our environment.
sadly any png or jpeg compression leads to wrong colors for transparent images in Firefox/Iceweasel. For example the Google logo gets acyan background. I switched to rle compression which reduced latency but it's still worse than plain X11.
The 30000 series ports are from ssh port redirection which X2Go uses to bring back the sound, printing, and local mounts. Hope that helps -
All pulseaudio sinks seem to be missing when using x2go. I attached tthe output of "pactl list" from within a x2go session.
Michael <snip> That's interesting. I have noticed a problem in specific circumstances and have not been able to track it down. I had a limited case where I installed Pyhoca (a fine product - I don't mean to knock it here as this was probably coincidental) and, after going back to the Qt client, all graphics were corrupted. Somehow, it "fixed" itself.
However, with complete consistency, if I open an RDP session to a Windows desktop and then run X2Go client from the RDP desktop, the graphics are always corrupt. If I use png instead of jpeg, then the jpegs show fine and vice versa. The only way to get a usable screen is to turn off compression. I've not had the time to track down the problem and did not know if it was specific to my environment. Hence my interest that you are experiencing something similar - John
-
John A. Sullivan III -
Michael Hierweck