Mike,
Thanks for your help. I think I may know why this isn't working. The Xserver is one that the webos-internals group has put together to run on top of the touchpad's OS (webos) and they haven't really included RandR support yet. This is what I found on the git for their Xserver,
"We just enable it, and report the single resolution we support. (Doesn't allow setting rotation/sizes/reflections yet)"
Do you think this is what would cause all the issues trying to get an x session to work?
I tried most of the things you suggested with the x2goclient and it segfaulted on all of them.
The only thing that I was able to get to work was opening an lxde session inside of Xnest. And even for that, it ran slow, complained about RandR missing, and eventually crashed (couldn't find in the logs why though).
I'll try and see if the webos-internals guys have plans to further implement RandR. I have other options since rdesktop seems to work, but would prefer to use x2go.
If you have any other ideas, let me know.
Thanks again,
Jimmy
-----Original Message----- From: x2go-user-bounces@lists.berlios.de [mailto:x2go-user- bounces@lists.berlios.de] On Behalf Of Mike Gabriel Sent: Tuesday, August 30, 2011 3:16 PM To: x2go-user@lists.berlios.de Subject: Re: [X2go-User] question regarding x2goclient armel builds
Hi Jimmy,
On Di 30 Aug 2011 19:59:27 CEST Jimmy Knowles wrote:
Thanks for your work on the x2go packages. I was hoping someone could help me to be able to connect using the armel builds. I have a hp touchpad with x server running and a chrooted version of debian squeeze. I've installed the packages without any problems and I'm having some problems getting a session to start successfully. When I initiate a session from the touchpad, it will connect and the desktop displays, but any window manager items seem to
What Xserver are you using on the touchpad? The Xorg that is in Debian?
crash. The panels don't display, any pop-up windows just flash and flicker. Only the desktop icons display correctly. And dmesg gives the following errors repeatedly:
[...]
What does work is if I'm resuming a session that was initiated via a windows (or amd64) x2goclient. One difference that I notice is that the windows-initiated session name ends with dp32 (I'm assuming that's the color depth?) and the touchpad/armel-initiated session ends with dp24. Any ideas on how to get it to work correctly when initiating the session on the armel device?
Windows color depth 32 equals Linux color depth 24. The upper 8bit are not really used for color resolution but for something else (I have forgotten what...). So 32bit on Win and 24bit on Linux are equivalent.
So, basically what happens is that x2goagent crashes on metacity session startup on the server-side. That is: something happens on the GNOME desktop during startup the lets metacity segfault.
Please try to narrow down the error:
o use a simple xterm session first o then use LXDE (simple desktop) as session o then try to disable all special effects on your GNOME desktop o by any chance try to connect to some other server (Ubuntu lucid, Debian squeeze preferrably) o ... and report what happens
Is the X2go server in your LAN (I am asking for connection speed)? Install Xnest on the Ubuntu natty machine and launch an Xnest session via ,,ssh -X''. Does that Xnest session (running on the Ubuntu machine, X-forwarded through SSH and displayed on your touchpad) survive? Or does it also crash???
If, by any chance, you can install a wheezy chroot on your pad... you could use the x2goclient from squeeze/armel and try if an upgrade of the local XServer does help.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...