[FreeNX-kNX] FreeNX & NoMachine Player - Connection Issues

Nick Couchman Nick.Couchman at seakr.com
Mon Jan 21 18:16:28 UTC 2013


>>> On 2013/01/21 at 09:57, <chris at ccburton.com> wrote: 
> freenx-knx-bounces at kde.org wrote on 20/01/2013 23:46:53:
> 
> Nick 
> 
> I thought I'd have another look at nxplayer myself, as I've
> been forced to look at client software again due to that font rendering
> issue so . . .
> 
> I just installed
>         nxplayer-4.0.181-3.x86_64.rpm
> on an Openuse 12.2 workstation ans pointed it at an Opensuse12.2 FreeNX
> 
> It connects but (nxplayer) segfaults quite a bit, I think associated
> with that font issue . . . 
> 
> nxplayer.bin[]: segfault at 0 ip 00007f7fb2e77757 sp 00007f7fab45fe50 
> error 4 in libnxdispfb.so.4.0.181[7f7fb2d03000+204000]
> nxplayer.bin[] general protection ip:7fa28f9265ee sp:7fffa33488e8 error:0 
> in libc-2.15.so[7fa28f8a2000+19b000]
> 
> 
> I did get one LibrOffice free connection working for and copied the logs 
> :-
> 
> 
> 
> Here's the user log fron ~/.nx/C- . . . on the server
> 
> 
> 
[SNIP]

Interesting...I'm back at my Mac in my office today, and, while I see the same error with my Mac, it is less frequent than with my Linux system (successfully connects more often).  However, this isn't a great test, since I was operating over a VPN with the Linux client, anyway, so there are some other variables there.

Still, I am puzzled by the fact that I can successfully connect and start an xterm (every time) and then run "startxfce4" and have it work, no crashes or errors, every single time.  Maybe this somehow works around the bug/segfault in NXPlayer, and perhaps this display segfault works equally well on both Linux and OS X.  I'll have to try out NX Player on Windows along with going back to some of the older clients and the OpenNX client for Mac to see what I can get to work/break.

Also, regarding the suspend/resume behavior (which also points to a client-side issue), I concur that the suspend actually seems to work fine on the server-side, and, eventually I can reconnect, but, again, it's a sort of hit-or-miss thing that fails with the same error.

As far as the bug you reference for the _XGetRequest issue, this has been fixed in the openSuSE repositories for FreeNX/NX - I believe nxagent-3.5.0-9 works correctly and that if the NX RPM is built with that version, this bug doesn't exist.  See the following openSuSE bug:

https://bugzilla.novell.com/show_bug.cgi?id=787775

-Nick



--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.



More information about the FreeNX-kNX mailing list