freenx-team team mailing list archive

[fermulator <fermulator@xxxxxxxxxxxx>]

Well.  Very interesting comments Jeremy.  Thanks for shining some light
on the situation.

I'm going to ask a "more forward" question.  From what package does
rgb.txt come from?  (or what package COULD it come from?)

The point I'm driving here is this:  Instead of modifying NX to try to
handle it's own rgb.txt, wouldn't it be better to simply make NX REQUIRE
(or at least recommend) the package which would bring the distro's
installation of X11 along with the proper rgb.txt file?

Just trying to think of cleanliness.  Your procedure/proposal is good,
but it's not perfect (yet?).

Use Case: User installs NX, and NX sees no rgb.txt file exists, so it
creates one with the proposed "nx tag".  But then the user decides to
remove the NX package, and doesn't shutdown properly.  The shutdown
initscript would never have been run (and never would be again) leaving
behind that dirty rgb.txt file, no?  (unless of course the removal of
free-nx cleans up the rgb.txt if appropriate..)

-- 
FreeNX implementation of "X Server" is missing something
https://bugs.launchpad.net/bugs/393701
You received this bug notification because you are a member of FreeNX
Team, which is the registrant for FreeNX Server.

Status in FreeNX open source NX Server: New

Bug description:
So apparently the FreeNX implementation of X server is missing something.

Please review: http://www.amsn-project.net/forums/viewtopic.php?p=38790

I have the exact same issue as described in those forums.  The application, amsn, works fine with logged in to the console (physically at keyboard), but when connected through NX ... amsn crashes as described in that thread.