headers
Tamás Pusztai | 1 Nov 2010 09:33
Picon

Re: Strange problem with text colors

Dear Akemi,

  This issue is not easy to track, since it happens time to time with no (at least for me) apparent reason.  I
remember this error occurring again within five minutes after reopening the connection, but it might
take several days to have it again.  For example I seem to have a peaceful period now, I don't remember when it
happened last, it must've been a week or so.

  I start to log the occurrence of the problem, with my current (most up-to-date CentOS 5.5) system.  After my
first experiencing this problem, I'll downgrade my freenx-0.7.3-6.el5.centos.x86_64 to
freenx-0.7.3-5.el5.centos.x86_64 and look for the problem again. If it happens again, or doesn't
happen for an extended time, I'll let you know and send a bug report if appropriate.

  Tamás

> I cannot reproduce the problem on 3 systems I have tried so far.  For
> testing, I ran the command suggested by Robert:
> 
> find / -type d -exec ls -al "{}" ";"
> 
> I'm running the CentOS version on all servers:
> 
> freenx-0.7.3-6.el5.centos.x86_64
> nx-3.4.0-6.el5.centos.x86_64
> 
> My client is running the latest from Nomachine:
> 
> nxclient-3.4.0-7.x86_64
> 
> Tamás, when you eventually had a chance to go back to an earlier
> version of nx/freenx from CentOS and find that the problem is indeed
(Continue reading)

Permalink | Reply | 3 comments |
headers
Amir Vadai | 1 Nov 2010 09:36
Picon

Re: Strange problem with text colors

Thanks,

I appreciate it,
Amir



2010/11/1 Tamás Pusztai <pusztai-nx <at> szfki.hu>
Dear Akemi,

 This issue is not easy to track, since it happens time to time with no (at least for me) apparent reason.  I remember this error occurring again within five minutes after reopening the connection, but it might take several days to have it again.  For example I seem to have a peaceful period now, I don't remember when it happened last, it must've been a week or so.

 I start to log the occurrence of the problem, with my current (most up-to-date CentOS 5.5) system.  After my first experiencing this problem, I'll downgrade my freenx-0.7.3-6.el5.centos.x86_64 to freenx-0.7.3-5.el5.centos.x86_64 and look for the problem again. If it happens again, or doesn't happen for an extended time, I'll let you know and send a bug report if appropriate.

 Tamás


> I cannot reproduce the problem on 3 systems I have tried so far.  For
> testing, I ran the command suggested by Robert:
>
> find / -type d -exec ls -al "{}" ";"
>
> I'm running the CentOS version on all servers:
>
> freenx-0.7.3-6.el5.centos.x86_64
> nx-3.4.0-6.el5.centos.x86_64
>
> My client is running the latest from Nomachine:
>
> nxclient-3.4.0-7.x86_64
>
> Tamás, when you eventually had a chance to go back to an earlier
> version of nx/freenx from CentOS and find that the problem is indeed
> related to the latest version, could you please file a report at
> http://bugs.centos.org ?
>
> You can find what has changed in the CentOS version of nx/freenx in
> this summary report:
>
> http://bugs.centos.org/view.php?id=4410
>
> Akemi (toracat)

________________________________________________________________
    Were you helped on this list with your FreeNX problem?
   Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

        Don't forget to check the NX Knowledge Base:
                http://www.nomachine.com/kb/

________________________________________________________________
      FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
     https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 2 comments |
headers
Jeff Siddall | 4 Nov 2010 21:42

Re: nxnode floating point exception

On 10/28/2010 12:09 PM, chris <at> ccburton.com wrote:
> 
> Jeff Siddall <news <at> siddall.name> wrote on 28/10/2010 15:58:26:
> [SNIP]
>> Got nx 3.3.0-38.fc12.  Latest one in the repos.
> 
> The latest version of agent and the libraries is 3.4.0 something or
> other, but no-one else reported your issue afaik anyway.
> 
> [SNIP]
>>         wait $NODE_AGENT_PID
> 
> OK That's just waiting for your agent session to end . . . .
> . . .  which it does . . .
> 
>>
>> > ssh -X myserver; /usr/libexec/nx/nxnode --agent
>>
>> I assume that means run ssh and then inside the ssh run
>> /usr/libexec/nx/nxnode --agent rather than passing that whole thing to a
>> shell?  If so, I get this:
> 
> I just copied it.
> 
> Actually I think it should be more like
> 
>         ssh -X myserver "/usr/libexec/nx/nxnode --agent :1000"
> 
> and after a slight delay depending on how fast your machine and link are
> you should get a black NX window from an agent on your server . . . .

Initially I tried this and it didn't work so I tried from a different
machine and it worked!  I also got the client to connect so I suspended
the session and went back to my original client.  I tried ssh -X
myserver and ran xclock, and that didn't work either.  Eventually I
discovered I was getting MTU exceeded errors on the VPN connection I was
using.  Good grief.

Anyway, once that was resolved I could get a black NX window by running
nxnode.  Problem solved, or so I thought!

Unfortunately things got worse.  I could not connect with the original
NX client or the 2nd one I just had working either :(

The server log contained:

NX> 596 Error: Session restore failed. Reason was: Session: Display
failure detected at 'Thu Nov  4 16:14:13 2010'.

Hmmm...

Eventually I found:

/usr/libexec/nx/nxserver --terminate

and once the old session was terminated I was able to connect with no
problem!

Thanks for the advice.  Long road but glad it's finally working.

My only remaining question is whether suspending a session generally a
bad thing?  Any ideas why my suspended session broke future connection
attempts?

Jeff
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 3 comments |
headers
chris | 5 Nov 2010 11:24
Favicon

Re: nxnode floating point exception


Jeff Siddall <news <at> siddall.name> wrote on 04/11/2010 20:42:31:

[SNIP]
> My only remaining question is whether suspending a session generally a
> bad thing?  Any ideas why my suspended session broke future connection
> attempts?

We experience a number of issues with resuming suspended sessions,
mostly to do with reconecting from a different workstation and linked to
screen size or windows/linux.

The user expects to re-connect but gets a new session.

Sometimes a user just gets a new session when they want to
 reconnect, even from the same machine.

Sometimes a session doesn't terminate properly and some files remain
locked until we clean up old nxagent instances.

Sometimes a user hoping for a second session finds they take over
their first session and don't get the option to start a second session.

On the whole it is reliable enough in our experience, but we have
to be available just in case.

Suspended sessions are v useful for running big reports or for
people on the move . . .

CB
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 2 comments |
headers
Robert Weis | 5 Nov 2010 19:34
Face
Picon
Favicon

Re: Strange problem with text colors


Hello,

maybe - I have a solution/workaround for this problem.

I just added the option ' -norender ' to the variable
AGENT_EXTRA_OPTIONS_X  in the file /usr/NX/etc/node.conf

In my case it contains now:
AGENT_EXTRA_OPTIONS_X=" +kb +bs -noshmem -norender -xkbdir
/usr/share/X11/xkb "

The configuration file may be located in another place for your
centos-systems.
And - of course - I don't know if it really solves the problem.
At least it does not occur even when I run my silly command
 find / -type d -exec ls -al "{}" ";"
for a longer time.

BTW: It looks like the freenx-server is ignoring the
nx-client-settings like
 - Disable the render extension
 - Disable the backing-store
 and so on.
No matter what I set there, the used options for the nxagent does not
change (checked by ps). I would expect, that the options '-/+bs'
'-noshmem/-shmem' '-render/-norender' will be appended when the client
requests it. And so I inserted these options statically in the config file.
Maybe I simply don't understand this feature.

best regards

Robert

Am 01.11.2010 09:36, schrieb Amir Vadai:
> Thanks,
> 
> I appreciate it,
> Amir
> 
> 
> 
> 2010/11/1 Tamás Pusztai <pusztai-nx <at> szfki.hu <mailto:pusztai-nx <at> szfki.hu>>
> 
>     Dear Akemi,
> 
>      This issue is not easy to track, since it happens time to time with
>     no (at least for me) apparent reason.  I remember this error
>     occurring again within five minutes after reopening the connection,
>     but it might take several days to have it again.  For example I seem
>     to have a peaceful period now, I don't remember when it happened
>     last, it must've been a week or so.
> 
>      I start to log the occurrence of the problem, with my current (most
>     up-to-date CentOS 5.5) system.  After my first experiencing this
>     problem, I'll downgrade my freenx-0.7.3-6.el5.centos.x86_64 to
>     freenx-0.7.3-5.el5.centos.x86_64 and look for the problem again. If
>     it happens again, or doesn't happen for an extended time, I'll let
>     you know and send a bug report if appropriate.
> 
>      Tamás
> 
> 
>     > I cannot reproduce the problem on 3 systems I have tried so far.  For
>     > testing, I ran the command suggested by Robert:
>     >
>     > find / -type d -exec ls -al "{}" ";"
>     >
>     > I'm running the CentOS version on all servers:
>     >
>     > freenx-0.7.3-6.el5.centos.x86_64
>     > nx-3.4.0-6.el5.centos.x86_64
>     >
>     > My client is running the latest from Nomachine:
>     >
>     > nxclient-3.4.0-7.x86_64
>     >
>     > Tamás, when you eventually had a chance to go back to an earlier
>     > version of nx/freenx from CentOS and find that the problem is indeed
>     > related to the latest version, could you please file a report at
>     > http://bugs.centos.org ?
>     >
>     > You can find what has changed in the CentOS version of nx/freenx in
>     > this summary report:
>     >
>     > http://bugs.centos.org/view.php?id=4410
>     >
>     > Akemi (toracat)
> 
>     ________________________________________________________________
>         Were you helped on this list with your FreeNX problem?
>        Then please write up the solution in the FreeNX Wiki/FAQ:
> 
>     http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
> 
>             Don't forget to check the NX Knowledge Base:
>                     http://www.nomachine.com/kb/
> 
>     ________________________________________________________________
>           FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
>     <mailto:FreeNX-kNX <at> kde.org>
>          https://mail.kde.org/mailman/listinfo/freenx-knx
>     ________________________________________________________________
> 
> 
> 
> 
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
> 
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>   
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/ 
> 
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

--

-- 
Dr. Robert Weis              |  Kirchhoff-Institut fuer Physik
Im Neuenheimer Feld 227      |           tel: +49 6221 54-9130
D-69120 Heidelberg           |           fax: +49 6221 54-9112
www: http://www.kip.uni-heidelberg.de/user/weis
gpg-key: 0xA7016FF4  or finger -l j67 <at> ix.urz.uni-heidelberg.de
gpg-key: http://www.kip.uni-heidelberg.de/~weis/public-key.asc
Permalink | Reply | 0 comments |
headers
Jeff Siddall | 12 Nov 2010 03:39

Re: nxnode floating point exception

On 11/05/2010 06:24 AM, chris <at> ccburton.com wrote:
> [SNIP]
>> My only remaining question is whether suspending a session generally a
>> bad thing?  Any ideas why my suspended session broke future connection
>> attempts?
> 
> We experience a number of issues with resuming suspended sessions,
> mostly to do with reconecting from a different workstation and linked to
> screen size or windows/linux.
> 
> The user expects to re-connect but gets a new session.
> 
> Sometimes a user just gets a new session when they want to
>  reconnect, even from the same machine.
> 
> Sometimes a session doesn't terminate properly and some files remain
> locked until we clean up old nxagent instances.
> 
> Sometimes a user hoping for a second session finds they take over
> their first session and don't get the option to start a second session.
> 
> On the whole it is reliable enough in our experience, but we have
> to be available just in case.
> 
> Suspended sessions are v useful for running big reports or for
> people on the move . . .

SOLVED!

Session resume was really broken for me -- as in it _never_ worked, even
from the same machine with all the same settings.

I discovered by chance that checking the "disable encryption of all
traffic", which I used because I was running over OpenVPN already
anyway, completely breaks session resume even though you can start a
session with that box checked.

Re-enabling compression resulted in reliable resumes.

Is this a known issue?  I really don't need two levels of encryption.

Next issue is sound... :(

Jeff
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 1 comment |
headers
Jeff Siddall | 12 Nov 2010 04:33

Re: nxnode floating point exception

On 11/11/2010 09:39 PM, Jeff Siddall wrote:
> Re-enabling compression resulted in reliable resumes.

Oops... that should have read:

> Re-enabling _encryption_ resulted in reliable resumes.

Jeff
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 0 comments |
headers
Tamás Pusztai | 16 Nov 2010 15:11
Picon

Re: Strange problem..., not only the latest version is affected

Hi,

  My "feeling" that only the newest version of freenx (available for Centos 5.5) is affected by this problem
was bad.

  After a week of (not too intense) use with freenx-0.7.3-6.el5.centos.x86_64 the problem encountered
again, so I downgraded to freenx-0.7.3-5.el5.centos.x86_64, and within another week of use, I had this
problem again.

  Tamás

On Nov 1, 2010, at 9:36 AM, Amir Vadai wrote:

> Thanks,
> 
> I appreciate it,
> Amir
> 
> 
> 
> 2010/11/1 Tamás Pusztai <pusztai-nx <at> szfki.hu>
> Dear Akemi,
> 
>  This issue is not easy to track, since it happens time to time with no (at least for me) apparent reason.  I
remember this error occurring again within five minutes after reopening the connection, but it might
take several days to have it again.  For example I seem to have a peaceful period now, I don't remember when it
happened last, it must've been a week or so.
> 
>  I start to log the occurrence of the problem, with my current (most up-to-date CentOS 5.5) system.  After my
first experiencing this problem, I'll downgrade my freenx-0.7.3-6.el5.centos.x86_64 to
freenx-0.7.3-5.el5.centos.x86_64 and look for the problem again. If it happens again, or doesn't
happen for an extended time, I'll let you know and send a bug report if appropriate.
> 
>  Tamás
> 
> 
> > I cannot reproduce the problem on 3 systems I have tried so far.  For
> > testing, I ran the command suggested by Robert:
> >
> > find / -type d -exec ls -al "{}" ";"
> >
> > I'm running the CentOS version on all servers:
> >
> > freenx-0.7.3-6.el5.centos.x86_64
> > nx-3.4.0-6.el5.centos.x86_64
> >
> > My client is running the latest from Nomachine:
> >
> > nxclient-3.4.0-7.x86_64
> >
> > Tamás, when you eventually had a chance to go back to an earlier
> > version of nx/freenx from CentOS and find that the problem is indeed
> > related to the latest version, could you please file a report at
> > http://bugs.centos.org ?
> >
> > You can find what has changed in the CentOS version of nx/freenx in
> > this summary report:
> >
> > http://bugs.centos.org/view.php?id=4410
> >
> > Akemi (toracat)
> 
> ________________________________________________________________
>     Were you helped on this list with your FreeNX problem?
>    Then please write up the solution in the FreeNX Wiki/FAQ:
> 
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
> 
>         Don't forget to check the NX Knowledge Base:
>                 http://www.nomachine.com/kb/
> 
> ________________________________________________________________
>       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
>      https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
> 
> ________________________________________________________________
>     Were you helped on this list with your FreeNX problem?
>    Then please write up the solution in the FreeNX Wiki/FAQ:
> 
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
> 
>         Don't forget to check the NX Knowledge Base:
>                 http://www.nomachine.com/kb/ 
> 
> ________________________________________________________________
>       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
>      https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 0 comments |
headers
William Hatch | 17 Nov 2010 18:52

freenx & sound

I've posted in a couple different forums, with no luck getting a good answer.

My situation is:  Fresh install of Ubuntu 10.04, successful install of
freenx-server, thin client computer lab with the option to connect via
nomachine client, no sound on the client.

Sound works on the server, but no sound card is detected when I log
into a thin client.

I am aware of the issue with Ubuntu abandoning the Enlightenment Sound
Daemon in favor of Pulseaudio.

How do I get sound from my thin clients? Thanks.

--

-- 
Will Hatch
Educational Technology Specialist
Vergennes Union Elementary School
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 1 comment |
headers
Jo-Erlend Schinstad | 23 Nov 2010 10:13
Picon

Re: freenx & sound

If audio is important, then FreeNX (or Nomachine NX for that matter)
is not for you. You might want to have a look at X2Go. It is based on
the same NX base, but it uses PulseAudio which gives you two-way audio
(as well as all your local interfaces, etc) which is useful for VoIP
and other things. It's really very nice.

http://www.x2go.org

Hope it helps.

Jo-Erlend Schinstad
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 0 comments |

Gmane