gmane.linux.terminal-server.x2go.devel

Re: NX/libcairo with nxagent-3.5.0-9: session resumption still failing (was: Re: First NX/libcairo tests succeeded (was Re: Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages))

Mike Gabriel — 2012-05-23T01:05:25

Hi,

On Mi 23 Mai 2012 01:49:08 CEST masc wrote:


Damn! Thanks for testing. I have reported your description to  
NoMachine upstream.

Mike

Re: First NX/libcairo tests succeeded (was Re: Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages)

masc — 2012-05-22T23:49:08

On debian sid setup gnome3 and apps like iceweasel start ok now, but
after resuming the session most text and some applications (like
docky) will not be rendered, so the session becomes unusable.

I had to downgrade libcairo2 from 1.12.2-2 to 1.10.2-7 again to get
resume working.

The recently updated versions of nxserver/nxnode from nomachine show
exactly the same issue on resume.
_______________________________________________
X2Go-Dev mailing list
X2Go-Dev< at >lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev

Re: First NX/libcairo tests succeeded (was Re: Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages)

John A. Sullivan III — 2012-05-22T11:31:05

<snip>
<snip>
I can confirm successful session resumption on Squeeze - John

Re: First NX/libcairo tests succeeded (was Re: Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages)

Mike Gabriel — 2012-05-22T10:51:56

Hi again,

On Di 22 Mai 2012 11:18:13 CEST Mike Gabriel wrote:


Sorry, typo... This is the correct URL for X2Go package for Debian squeeze...
deb http://packages.x2go.org/debian squeeze heuler

Mike

First NX/libcairo tests succeeded (was Re: Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages)

Mike Gabriel — 2012-05-22T09:18:13

Hi all,

On Di 22 Mai 2012 10:37:32 CEST Mike Gabriel wrote:


So my first tests succeeded. Can anyone else confirm the x2goagent from

   deb http://packages.debian.org/debian wheezy|sid heuler

works with GNOME (or iceweasel, icedove)?

Please cross-check that session resuming also works as expected, esp.  
on Debian squeeze systems:

   deb http://packages.debian.org/debian squeeze heuler

Greets,
Mike

Re: Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages

Mike Gabriel — 2012-05-22T08:37:32

Hi John,

On Di 22 Mai 2012 02:02:37 CEST John Williams wrote:


After more than one person has tested the nightly built Debian packages.

The first person is me, another person has to confirm that the  
libcairo crashes are gone and that session resuming works again with  
about the reported broken glyphs.

I have not had time to test the packages, yet, but will do now.

Mike

Re: Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages

John Williams — 2012-05-22T00:02:37

To clarify, I mean the tar archive package.

Re: Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages

John Williams — 2012-05-22T00:01:53

On Mon, May 21, 2012 at 4:12 PM, Mike Gabriel
<mike.gabriel< at >das-netzwerkteam.de> wrote:

When should the updated nx-libs redistributed source code be available?

Re: Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages

Mike Gabriel — 2012-05-21T23:12:18

Hi again,

nx-libs packages (Debian) are currently building for the nightly  
repos. Should be available by tomorrow morning (CEST).

Please join in testing (3.5.0.14 NX redistributed).

< at >Mihai: as you see, it took me less than 30 minutes to incorporate the  
latest nxagent release from NoMachine.

Greets,
Mike

On Di 22 Mai 2012 00:26:09 CEST Mike Gabriel wrote:

Fwd: Fourth Maintenance Release of the NX 3.5.0 Node and Server packages

Mike Gabriel — 2012-05-21T22:26:09

Hi all,

NoMachine seems to have fixed the libcairo issue we discussed lately.

I will take a look at their changes tomorrow.

Mike

----- Weitergeleitete Nachricht von sender-nxannounce< at >nomachine.com -----
      Datum: Mon, 21 May 2012 22:52:10 +0200
        Von: sender-nxannounce< at >nomachine.com
    Betreff: Fourth Maintenance Release of the NX 3.5.0 Node and  
Server packages
         An: mike.gabriel< at >das-netzwerkteam.de


Rome, Italy, May 21, 2012 - NoMachine makes available updates to NX
Node and Server software. This new maintenance release is mainly aimed
at solving some issues preventing applications using Cairo libraries
to work with NX, and includes:

- NX sessions may crash with applications such as Firefox or
   Thunderbird using Cairo library version 1.12.0.

- A degrade in performance may be noticed when running applications
   using Cairo library version 1.10.

- Changes to mouse sensitivity made in the tool gnome-mouse-properties
   may be ignored in an NX session.

- Reconnecting 3.5.0 sessions with NoMachine Player 4 may fail.



Supported NX Node and Server platforms
--------------------------------------

Solaris SPARC 8/9/10

Linux x86_64

- Red Hat Enterprise 4/5/6
- SLED 10.x/11.x, SLES 10/11, Open SUSE 10.x/11.x/12.x
- Mandriva 10.1/2005/2006/2007/2008/2009/2010/2011
- Fedora Core 3/4/5/6
- Fedora 7/8/9/10/11/12/13/14/15/16
- Xandros Desktop 4.1/Xandros Server 2.0
- Debian GNU Linux 4.0 Etch/5.0 Lenny/ 6.0 Squeeze
- Xandros Desktop 4.1/Xandros Server 2.0
- Ubuntu 5.10 Breezy Badger/6.06 Dapper Drake/6.10 Edgy Eft/7.04
   Feisty Fawn/7.10 Gutsy Gibbon/8.04 Hardy Heron/8.10 Intrepid Ibex/
   9.04 Jaunty Jackalope/9.10 Karmic Koala/10.4 Lucid Lynx/10.10
   Maverick Meerkat/11.04 Natty Narwhal/11.10 Oneiric Ocelot/12.04
   Precise Pangolin


Linux i386

- RedHat 7.2/7.3/8.0/9.0
- RedHat Enterprise Linux 3/4/5/6
- SuSE Linux 7.2/7.3/8.0/8.1/8.2/9.0, SLED 10.x/11.x, SLES 10/11,
   Open SUSE 10.x/11.x/12.x
- Mandriva Linux 9.0/9.1/9.2/10.0/10.1/2005/2006/2007/2008/2009/2010/
   2011
- Fedora Core 1/2/3/4/5/6
- Fedora 7/8/9/10/11/12/13/14/15/16
- Debian GNU Linux 3.0 Woody/3.1 Sarge/4.0 Etch/5.0 Lenny/ 6.0 Squeeze
- Xandros 3.0/Xandros Desktop 4.1/Xandros Server 2.0
- Ubuntu 5.04 Hoary Hedgehog/5.10 Breezy Badger/6.06 Dapper Drake/6.10
   Edgy Eft/7.04 Feisty Fawn/7.10 Gutsy Gibbon/8.04 Hardy Heron/8.10
   Intrepid Ibex/9.04 Jaunty Jackalope/9.10 Karmic Koala/10.4 Lucid
   Lynx/10.10 Maverick Meerkat/11.04 Natty Narwhal/11.10 Oneiric Ocelot/
   12.04 Precise Pangolin



Trouble Reports solved
----------------------

NX Core

TR01J02646 - Performance issues could arise with certain graphics
libraries such as Cairo library version 1.10

TR01J02667 - Changes to mouse sensitivity may be ignored in an NX
session

TR05J02705 - The X11 agent may ignore WarpPointer requests

TR05J02706 -  Sometimes disconnected sessions on NX server 3.5.0
cannot be recovered when using NoMachine Player 4

TR05J02703 - The X11 agent could terminate unexpectedly with
libcairo 1.12


NX Server

TR12I02644 - NX Server may fail to generate SSH keys on Centos 6.2

TR12I02641 - NX server message about enough X resources contains
a typo

TR10I02615 - Running the 'nxserver --userdel' command may change
group for backend files


NX Node

TR01J02666  - ClientLogLimit in node.cfg is ignored



Download the NX Node and Server packages
----------------------------------------

You can download the latest node and server suitable for your
Operating System from the NoMachine Web site at the following URL:

http://www.nomachine.com/download/



Update
------

Instructions for Linux are intended to be run from command line and
use the sudo utility. If you don't have the sudo utility installed,
log on as superuser ('root') and run the commands without sudo.
Otherwise you can use the graphical package manager provided by your
Linux distribution. Instructions for RPM , DEB and tar.gz packages
refer to the 32 bit package (i386) and can be easily extended to the
64bit package (x86_64 or amd64).

It is highly recommended you disable access to new NX sessions and
terminate all running sessions before proceeding with the update of
node and server. To disable access to new NX sessions and terminate
all the running sessions, open an xterm or similar and run commands
below:

$ sudo /usr/NX/bin/nxserver --stop
$ sudo /usr/NX/bin/nxserver --shutdown

After the update procedure is completed, restart NX server by running:

$ sudo /usr/NX/bin/nxserver --start


RPM version for Linux

- Download the RPMs
- Change your working directory to the location where you saved the
   packages and update the node and server installation by running from
   a console:
   $ sudo rpm -Uvh nxnode-3.5.0-xy.i386.rpm
   $ sudo rpm -Uvh nxserver-3.5.0-xy.i386.rpm


DEB version for Linux

- Download the DEBs
- Change your working directory to the location where you saved the
   packages and update the node and server installation by running from
   a console:
   $ sudo dpkg -i nxnode_3.5.0-xy_i386.deb
   $ sudo dpkg -i nxserver_3.5.0-xy_i386.deb


TAR.GZ version for Linux

- Download the TAR.GZs in the /usr directory
- Change your working directory to the /usr directory, and uncompress
   the packages by running from a console:
   $ cd /usr
   $ sudo tar zxvf nxnode-3.5.0-xy.i386.tar.gz
   $ sudo tar zxvf nxserver-3.5.0-xy.i386.tar.gz
- Run the setup scripts for updating the NX Node and Server software:
   $ sudo /usr/NX/bin/nxnode --update
   $ sudo /usr/NX/bin/nxserver --update


SPARC.GZ version for Solaris

- Download the SPARC.GZs
- Change your working directory to the location where you saved the
   packages, uninstall the previous versions of the software and install
   the new packages by running from a console:
   # pkgrm NXserver
   # pkgrm NXnode
   # gunzip nxnode-3.5.0-xy.sparc.gz
   # gunzip nxserver-3.5.0-xy.sparc.gz
   # pkgadd -d nxnode-3.5.0-xy.sparc
   # pkgadd -d nxserver-3.5.0-xy.sparc


The complete set of installation instructions is available at:

http://www.nomachine.com/installation.php

You can find here more detailed instructions on how to configure and
administer NX Node and NX Server:

http://www.nomachine.com/documents/admin-guide.php


NoMachine NX OSS components
---------------------------

Together with the commercial NX products, this new maintenance release
sports updates to the following OSS component:

nxagent-3.5.0-8


The following components were not updated since the previous 3.5.0
releases:

nx-X11-3.5.0-2
nxuexec-3.5.0-3
nxcomp-3.5.0-2
nxcompext-3.5.0-1
nxcompshad-3.5.0-2
nxspool-3.5.0-1
nxsensor-3.5.0-1

Sources of all the OSS NX components can be downloaded here:

http://www.nomachine.com/sources/

Please refer to the ChangeLog of each specific package for more
information about all changes introduced since the previous 3.5.0
versions.


The NX Development Team

You have received this email because you are currently registered to
receive NX Software Updates either as NX News or NX Announce.
If you do not wish to receive future NoMachine newsletters, please go to
the website to unsubscribe: http://www.nomachine.com/mailinglist.php.



----- Ende der weitergeleiteten Nachricht -----

Re: X2Go-Future

Arnold Krille — 2012-05-21T18:52:22

As I said, with my very poor internet-connection it is much better then VNC to 
log into work. But on lan it feels slower. I did measure it with some X-tests 
and the results where the same for local, xdmcp and x2go.


When users "feel" that something is slow, its not always the throughput. Your 
explaination actually makes much more sense. It probably is the latency. That 
would also explain why it doesn't improve when I change compression levels.


So what to do with that? Is there a way to disable ssh for local lan 
connections?

Have fun,

Arnold_______________________________________________
X2Go-Dev mailing list
X2Go-Dev< at >lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev

Re: Windows X2Go client and Windows 8

Moritz Struebe — 2012-05-21T13:59:00

I do agree. If it actually crashes, there is (also) a bug in Windows or,
more likely, some driver (Due to memory protection, etc. it should not
be possible for any application to crash the OS). While Windows crashes
it's probably not worth investigating. Afterwards you might want to poke
the VcXsrv-guys :).

Cheers
Morty

Re: Windows X2Go client and Windows 8

Mike Gabriel — 2012-05-21T13:32:27

Hi Stefan,

On Mo 21 Mai 2012 14:47:00 CEST Stefan Baur wrote:


Yeah!!! Someone at Microsoft, I guess... It is their OS that crashed.  
Not X2Go (VcXsrv).

lol *g*
Mike

Windows X2Go client and Windows 8

Stefan Baur — 2012-05-21T12:47:00

Hi Devs,

just FYI: I tried to run 3.99.2.1-rc3 on Windows 8 (32-Bit) and it gets 
to the point where the connection is established and it tries to start 
the X server on the client, then it completely crashes Windows 8 (forced 
reboot).

Attempting to run vcxsrv.exe on its own doesn't seem to do anything: 
There's no black X desktop showing up, but Win8 doesn't crash either.

With Windows 8 schedluled for release in October 2012, I guess *someone* 
should take a look at this soon.

-Stefan

Re: X2Go-Future

Stefan Baur — 2012-05-21T12:06:19

Am 21.05.2012 13:53, schrieb John A. Sullivan III:

I don't know if it's feasible for you to do so, but it might be possible 
to open a second SSH port on your server and have another script connect 
to that port. Even on Windows, PuTTY has a command line tool that allows 
for that. If you're using an ssh agent (PuTTY has pageant.exe for that, 
which works nicely with X2Go) then the user doesn't even have to type 
the password twice.

-Stefan

Clipboard feature?

Stefan Baur — 2012-05-21T11:59:51

Hi Devs,

not long ago, someone (Alex?) posted a message that X2Go doesn't strive 
to be NoMachine NX and prefers to work as a glue between several freely 
available and already existing components (like, using ssh tunneling and 
FUSE for file sharing between server and client).

One feature that NoMachine NX (and FreeNX) has is to limit the use of 
the clipboard:
You can set it to work both ways, server -> client, client -> server, or 
not at all.

How could that be mimicked if such a feature is not part of X2Go?

-Stefan

Re: X2Go-Future

John A. Sullivan III — 2012-05-21T11:53:53

<snip>
<snip>
I cannot confirm that it is slower than VNC on a LAN but I can confirm
that I have seen a dramatic increase in latency since the move to
libssh.  It still really feels like Nagle is enabled.  I've not 100%
ruled out that it is not something in my environment like packet loss on
our connections but it doesn't feel like it.  It feels exactly like
packet coalescing as it is just the last bit of input that is badly
delay - badly as in a second or so so  very noticeable with serious
production impact as it leads to dangerous mistakes while editing
documents.  I wonder if libssh does not have the ability to disable it.

As a side note, I'm also really missing the setting of the ToS bits
since moving to libssh.  We currently have no way to distinguish X2Go
interactive traffic (key strokes and screens) from bulk traffic (file
transfers and print jobs).

Thanks - John

Re: X2Go-Future

Moritz Strübe — 2012-05-20T20:25:22

Am 20.05.2012 14:37, Mike Gabriel schrieb:

The thing to remember here is, that this isn't such an issue, as the
client side X-server should be up to date and the server side X-server
runns with the same privileges as your average application. Therefore -
for normal use cases -  there no real advantage in attacking the server,
as your rights can not really be extended. Reducing these rights might
be an interesting approach to make x2go a bit safer with minimal effort,
though.

Cheers
Morty

Re: X2Go-Future

Mike Gabriel — 2012-05-20T12:37:02

Hi Arnold,

On Sa 19 Mai 2012 21:55:28 CEST Arnold Krille wrote:


There has been a long discussion about the current NX 3.5 code base.  
NX 3.5 is based on Xorg 6.9 (I think). Pretty old kind of an Xorg and  
probably lacking quite a few security patches reported against Xorg  
upstream. This is the main problem of NX. And: it will still be there  
with NX 4.0, as NoMachine has not freshed up the Xorg base NX got  
forked from (AFAIK, people may correct me here).

The above said is the reason why NX 3.5 (esp. the nxagent/x2goagent)  
will not find its way into Debian currently.

X2Go can work with any X agent available but nothing scales as good as  
NX. As we do not believe in capturing technologies like VNC or  
RemoteFX/RDP when we aim at performance we still stick to NX as GUI  
rendering techology. X2Go itself in code is very flexible. If anything  
better than NX will appear on the market, we will utilize it.


Then there must be something wrong with your setup. X2Go works on UMTS  
(even GPRS) networks as well as on local area network. Not sure what  
you are experiencing, but I cannot confirm what you report.


I am not so sure if NX 4.0 has really improved the NX technology  
itself. From what I heard the improvements are rather on the session  
protocol, multi-media integration etc.


Use NX 3.5 for now. We have an alternative approach we currently  
discuss but currently we lack man power for even playing with code  
snippets.


Knowledge: yes, man power: no. What is needed for NX is a  
re-integration into Xorg HEAD development. If there was a funding that  
would cover 1-2 persons over a couple of months then this could be  
feasible, but still: a huge project.


No, there is no real communication between X2Go and NoMachine. Apart  
from bug reporting and answering to our reports.


VNC is not an X protocol. Neither does it meet our needs and  
requirements for a smooth remote X desktop.

Thanks for your open questions, my answers are just mine. Other  
developers may have different answers.

Greets,
Mike

Re: [nx-libs] Reason for using quilt

Mike Gabriel — 2012-05-20T12:21:23

Hi Mihai,

On Sa 19 Mai 2012 19:51:07 CEST Mihai Moldovan wrote:


Currently, we do not consider us as upstream for NX, only as a  
redistributor. So, keeping track of NX upstream is one reason for  
combining git+quilt.


We had that before (for x2goagent and libxcomp* when they were still  
separate code trees) and it was very difficult to keep track of _our_  
changes and _NoMachine_ changes. With quilt this is now very very easy.

We also had the case that many patches needed an update after  
NoMachine bumped an NX upstream release. So what happens then is that  
you have NoMachine upstream, then commit X2Go changes to your branch,  
merge from upstream again and then patch your own patches if a  
follow-up upstream release breaks your changes. It becomes very hard  
then to keep track of your changes, esp. with so many patches as we  
currently have for NX. Note that they also stack on top of each other...

The current approach is the easiest and the cleanest approach we have  
ever had for maintaining NX / X2Go agent. But that's my personal view  
only.

Greets,
Mike

Re: x2goclient 3.99.2.0 introduces excessive clientlogging

masc — 2012-05-20T06:24:03

Great, thanks for the quick response!

Marco