x2go-dev

x2go-dev@lists.x2go.org

2 participants
5403 discussions

occurrence of sluggishness in X2Go
by Mike Gabriel 09 Jun '12

09 Jun '12

Hi, just for the record and to let people know about current work focus... People (esp. John) have reported occurrences of a very sluggish behaviour of various applications when run in X2Go sessions. We developers can now confirm this. Ubuntu users reported this earlier, Debian user can now also experience such a sluggishness. Reproduce on Debian: * add squeeze-backports archive to your system * install iceweasel (esr version) This will drag in a libcairo from squeeze backports that is very probably the cause for making some applications very slow within X2Go sessions. Libcairo is used in all GTK applications and is a layer between GTK and the rendering backend (X11, OpenGL, ...). With some recent version of libcairo the sluggishness got introduced... @John: so it is not Nagle, I guess... Compare: launch gnome-terminal (uses libcairo) on such a system and xterm (uses direct X11 rendering). Now create some output on standard out and then scroll back the shell history... Alex has become aware of this on Linux Day Berlin and he has put it on his list with high priority to find a solution/workaround for that. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0xB588399B mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

4 8

releasing x2goclient before pull pulseaudio changes
by Mike Gabriel 08 Jun '12

08 Jun '12

Hi Mihai, I have just released x2goclient 3.99.2.1. I wanted to do that (a) because of the Unity support recently added and (b) before I pull your pulseaudio work. The pulseaudio work: Alex is very busy for the next two weeks. He can only take a look at your work after his software project he is currently working on. I guess we will pull your work, but I cannot do that by myself without having seen your code. Please merge your changlog entries under 3.99.3.0 (which will be the next release due to the great pulseaudio changes you provide). Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0xB588399B mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

2 1

Re: [X2Go-Dev] Segfault issue with x2goserver.
by Nable 80 06 Jun '12

06 Jun '12

Hi. At first, thank you for extremely quick answer. If this issue is known, then it may be good to add 'Conflicts: libcairo (>= 1.12)' to debian/control file of main version of x2goagent. It could save some hair of new users from becoming gray. I've tried both of your pieces of advice. On 32bit server i've downgraded libcairo to 1.8 (it would be better to have 1.10 but it's available in repo no more) and also had to downgrade everything that depends on it. After that both nxserver and x2goserver work good. If i have time i'll also try newer nxserver (i really enjoy their lightweight Win32 client), although i've heard that freenx lacks support and tends to become abandoned. On 64bit server i've updated x2go server apps to wheezy/heuler versions and it also works now. lxterminal and chromium seems to be slow (although, chromium via `ssh -X' never worked fast; lxterminal scrolls slowly but it's not dramatically slow) and icedove doesn't seem to be slow at all. Although, issue about problems with resuming is actual: both lxterminal and icedove lose all text labels and cannot show any text (see attached screenshot of menu ) until i close them and open again (minimize + restore or resize doesn't help). One more thing, about exporting client dirs to x2go session: it works only when i set (in x2goclient session settings) local encoding to windows-1251, but my OS and FS supports and uses unicode, does anybody work on fixing such support in x2goclient? Also even when I set local encoding to cp1251, on server side I see that dots from the beginning of filenames (yes, I have folders with names like .ssh, files .bashrc, etc) are stripped. That doesn't seem to be correct behavior. Thanks again for your answer, also I hope that I can help in improving x2go project too.

1 0

[PATCHv2] [NX] Add patch: 052_nxcomp_macos10-nxauth-location.full+lite.patch, change nxauth search location on Mac OS X to $NX_SYSTEM/nxauth to facilitate application bundle building.
by Mihai Moldovan 04 Jun '12

04 Jun '12

Signed-off-by: Mihai Moldovan <ionic(a)ionic.de> --- debian/changelog | 3 ++ ..._nxcomp_macos10-nxauth-location.full+lite.patch | 38 ++++++++++++++++++++ debian/patches/series | 1 + 3 files changed, 42 insertions(+) create mode 100644 debian/patches/052_nxcomp_macos10-nxauth-location.full+lite.patch

2 1

PulseAudio
by Mihai Moldovan 02 Jun '12

02 Jun '12

Hi all, just as a quick status message: I'm currently working on integrating PulseAudio into the OS X client and it looks good so far. PA will be started as soon as the client launches and killed on terminate... well, actually is. A quick test on 10.5 and 10.6 boxes show that the OS X version of PA works reasonably fine (at least it starts up and can play a sample WAVE file, so I call it a success.) Will try implementing PA session stuff tomorrow and do a few tests with it. We'll see, fingers crossed... Best regards, Mihai

7 11

Segfault issue with x2goserver.
by Nable 80 31 May '12

31 May '12

Good daytime for everyone. Since 2010 I've been using nxserver (freenx-0.7.3 + nxserver-3.4.0, installed into /opt/NX ) on my Debian6 32-bit server ( currently kernel 2.6.32-45, here is my /etc/apt/sources.list: http://pastebin.ca/2156639 ). I didn't use is for about 2-3 months and today I found that when I try to connect to my server, it draws some initial graphics and then connection interrupts. In dmesg i see: [4573539.498493] nxagent[5736]: segfault at 0 ip 080e3f03 sp bf9e6900 error 4 in nxagent[8048000+438000] [4573581.591042] nxagent[6371]: segfault at 0 ip 080e3f03 sp bf9a1d90 error 4 in nxagent[8048000+438000] ... (same EIP each time) I've thought that some update of X11 libs lead it to broke and remembered that some some time ago in Debian repos appeared some NX libs, so i've looked what depends on them. So, i've found x2goserver. I've installed it ( as it described here: http://wiki.x2go.org/doku.php/wiki:x2go-repository-debian ), installed x2goclient on my Win32 notebook but when i try to connect, i see the same thing: X client application (i use openbox+lxpanel there) do some requests, in ~/.xsession-errors i can see smth like: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 1070 requests (1070 known processed) with 0 events remaining. and then no data comes to client. In dmesg i see: [4578741.547603] x2goagent[18222]: segfault at 0 ip 080e87b1 sp bfe1afd0 error 4 in nxagent[8048000+460000] [4578947.507016] x2goagent[20046]: segfault at 0 ip 080e87b1 sp bfbf80c0 error 4 in nxagent[8048000+460000] ... (same EIP each time) I've used objdump and found that there program tries to read byte from pointer (and doesn't check that it's not NULL) but there are no debugging symbols, so i even don't catch what function is it. Then i've tried installing x2goserver to my new Debian6 64bit server (it's almost pure Debian installation) but when i try to connect to it, the only application that works is fluxbox, if I try to start anything like lxterminal, x2goagent fails at the code that looks very similar to 32bit variant: [794878.270330] x2goagent[29210]: segfault at 0 ip 00000000004a9bb0 sp 00007fff41ee6f60 error 4 in nxagent[400000+4f7000] [795053.995418] x2goagent[30256]: segfault at 0 ip 00000000004a9bb0 sp 00007fff8ae42160 error 4 in nxagent[400000+4f7000] If anyone cares, i'll try to send as much additional info as I can, just tell what are you interested in. I can even try to debug it but i still haven't understood how to build x2go utils from sources.

2 1

x2gosetkeyboard -- automatic detection of the client-side keyboard setup
by Mike Gabriel 29 May '12

29 May '12

Hi all, over the weekend I have worked a lot on the keyboard setup within X2Go sessions. The server now offers three modes for configuring the session's keyboard settings: 1. no change via client -> configure your keyboard setup through desktop tools, e.g. gnome-keyboard-properties 2. set model and layout through x2goclient -> use -type parameter of nxagent/x2goagent to set the keyboard model/type -> x2goclient + pyhoca-gui run setxkbmap -layout <layout> after session startup -> pyhoca-gui additionally runs setxkbmap -variant <variant> after session startup (new session profile: ,,variant''). ---> RECOMMENDED for x2goclient 3. NEW: autodetect the client-side keyboard layout through NX -> set the keyboard model/type to ,,auto'' (instead of pc104/us etc.) -> nxagent will create a file ~/.x2go/<session>/keyboard with all client-side keyboard settings -> x2goruncommand and x2goresume-session will call a new script: called x2gosetkeyboard -> x2gosetkeyboard will reset the keyboard settings and set all settings as found in the keyboard file To test this (third) new feature, you only have to install the x2goserver packages from either of the nightly repositories. NX already has this feature since 2:3.5.0.12 (actually earlier, but the named version is currently in our main repositories). With x2goclient you have to set the keyboard type/model to auto and leave the layout field empty. With PyHoca-GUI (from the nightly builds) you have to set the keyboard type/model to auto and leave the fields layout and variant empty. Both applications will have proper GUI elements to configure this more handily in the near future. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0xB588399B mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Updated Mac OS X packages
by Mihai Moldovan 27 May '12

27 May '12

Hi, I finally got around to sync and update the Mac OS X packages. Here we go. ----- Mac OS X 10.5 and higher (x86, x86_64, ppc): www.ionic.de/x2goclient-git-adefcb0cd2-1.dmg For security reasons, please turn on X11 authentication and network connections in the X servers preferences: X11 -> Preferences -> Security -> [X] Authenticate connections (always enable this) X11 -> Preferences -> Security -> [ ] Allow network connections from network clients (best idea is to disable it, unless you know what it does and really need it) Please make sure to check your settings. Unlike with previous releases, you shouldn't see any authentication problems due to the added nxauth binary. ----- Mac OS X 10.4 (x86, ppc): www.ionic.de/x2goclient-git-adefcb0cd2-tiger-1.dmg Please remember that you will have to close X11 server applications by yourself, whenever you are done, and that every new session starts a new X11 server instance. Also, as previously mentioned, you're on your own with this client. ----- That's all, thanks. Best regards, Mihai

1 0

[PATCH] [NX] Add patch: 052_nxcomp_macos10-nxauth-location.full+lite, change nxauth search location on Mac OS X to $NX_SYSTEM/nxauth to facilitate application bundle building.
by Mihai Moldovan 26 May '12

26 May '12

Change the nxauth location from $NX_SYSTEM/bin/nxauth to $NX_SYSTEM/nxauth on Mac OS X. This way, nxauth can be shipped in the same directory, as, i.e., nxproxy in an application bundle. Signed-off-by: Mihai Moldovan <ionic(a)ionic.de> --- debian/changelog | 3 ++ .../052_nxcomp_macos10-nxauth-location.full+lite | 38 ++++++++++++++++++++ debian/patches/series | 1 + 3 files changed, 42 insertions(+) create mode 100644 debian/patches/052_nxcomp_macos10-nxauth-location.full+lite

2 3

Mac OS X 10.4 Tiger
by Mihai Moldovan 26 May '12

26 May '12

Hi, with the latest changes, x2goclient will also run on Mac OS X 10.4. However, it will not be officially supported. While x2go is generally "use at own risk", this one is "use at own risk and don't expect it to work properly." Mac OS 10.4 is really old and unsupported even by Apple Inc. - not even with security updates. The X11 server version bundled with 10.4 is also old and known to cause color problems. The X11 server is not meant to be updated by users in an easy and convenient way, or at all. X11 server releases for 10.5 can't be installed on 10.4. Generally, starting an X11 application on 10.5 and higher will automatically launch the X11 server, if installed. This is due to structural changes in X11 integration implemented by Apple. On user login, an environmental variable called "$DISPLAY" is set and points to a UNIX socket monitored by the system daemon launchd. Whenever something tries to connect to this socket, the X11 binary is started. This is not true for 10.4. On those systems, $DISPLAY is not automatically set and thus not available from the initial environment. Starting X11 manually will spawn an xterm instance with this env. var. set. From this terminal application, other X11 applications could be launched just fine. However, non-child-processes still won't be able to communicate with the X11 server. Also, there is no easy way to know if an X11 server is already running, and if it is, on which socket it's listening. My first idea was to implement some kind of autodetection/probing for X11 sockets and connect to them in order to determine whether they work or not. This said, at the same time valid security concerns were raised. Connecting to unknown sockets is potentially dangerous, and as the place those sockets are placed in is world-writable, anyone could put a prepared socket in there. For obvious reasons, I dismissed this idea. Instead, I am now probing for a free display number and launching a separate X11 server instance whenever it is needed. Existing instances/sockets won't be re-used. This works fine, but obviously means that for every session a separate X11 server is launched and the user has to clean up those instances by hand (luckily each instance is shown as a normal application, so terminating those processes is not a problem at all.) This seemed like the safest, fastest and easiest way to go. Another way would be searching the currently running processes for X11 and examining the open files to find the socket, but this is way more complicated and not really worth the effort. Aside from that, the X11 server is listening for TCP connections by default and there is no way/option to turn this behavior off, unlike in 10.5 and higher. While the X protocol does have some security model based on the authcookies, I'm really not too happy with exposing my X11 server to the whole network. At the very least, evil users could crash the server. Evil geniuses may even obtain root access in some way or another, especially with such an old and unmaintained version. I've only been rudimentary testing remote sessions, but as far as I see, opening a new session, resuming and terminating works, at least with xterm as the remote application. I can't really test this more thoroughly, as my test system seems somewhat borked in X11 mode and is pressing "escape" after every key press. This is also happening in local xterm sessions for me, but I haven't found any information to this kind of misbehavior. Not being able to test this stuff is just another good reason to not support it officially. This said, I guess I will publish new versions for 10.4 from time to time, for those users who are bound to it and brave enough to use it. But again, if it opens up anything visible, this is far more than you should even expect. Best regards, Mihai

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev