[FreeNX-kNX] SOLVED!!! CentOS6 FreeNX never starts session

[Ryan Cooley]

Sonofabitch!  I figured it out.

It was a bit of a shot in the dark (I still can't untangle those messy NX scripts), but I spun-up another VM with CentOS6 and freenx, and watched it work just fine.  Even VMWare-tools didn't cause a problem.  So I considered WTH could be different enough between the two to cause problems.  In a flash of inspiration I started looking into /etc/profile.d/ scripts, and found a suspicious character...  Sure enough, *yum -y erase bash-completion* has COMPLETELY solved this damn problem.  This one incident completely negates any benefit I've ever gotten from it, so it's gone for good.

Some more thoughts in-line below...

> -----Original Message-----
> From: freenx-knx-bounces at kde.org [mailto:freenx-knx-bounces at kde.org]
> On Behalf Of Les Mikesell
> Sent: Friday, February 15, 2013 3:38 PM
> To: User Support for FreeNX Server and kNX Client
> Subject: Re: [FreeNX-kNX] CentOS6 FreeNX never starts session

> I did that in an earlier century.  But the overhead is trivial these
> days and I'm not giving up mouse cut/paste, resizable windows and
> fonts and the ability to run wireshark and firefox in the session if
> needed.  

You can still have mouse copy/paste and resize, it's just done on your local xterm/putty/whatever instead of inside a remote X session.  For the odd GUI tool, SSH's X11 forwarding will make that automagically work.  

> Just use NX and don't look back.  Even if non-X stuff worked as well,
> you'd still have to find matching character-mode terminal emulators
> across the client platforms you use.   You can grab the running
> freenx session onto linux/windows/mac clients and barely know the
> difference.

I'd have to veto NX just because VX ConnectBot works great on Android phones (sliders, in particular), while there's no NX client for Android.  Yes, I do real, serious, heavy-lifting *work* from my phone, so I don't have to carry a laptop around with me at absolutely ALL times.

And as for terminal emulators, I know what you mean.  But in my case, I found all the GUI/commercial ones were horrible in one way or another anyhow, and ended up significantly modifying wy60 to get my employer's apps working.  The ability to use it over SSH is just a fringe benefit.

> I think this is the fix:
> http://www.nomachine.com/ar/view.php?ar_id=AR11I00608
> And it looks specific to some version of the vm tools.

Doesn't apply to me, I couldn't even get an xterm window up, never-mind GNOME.  

But at least I finally found a fix.  I do appreciate the help.