James, I honestly don't know the inner workings of NX or how it sets up a session. Basically, I open the NX client, and in my settings I tell it to log me in with a gnome session. Other options are kde, xdm, cde, or custom, where I can tell it to use the system default or run a custom command. So when I log in, it will do one of 2 things:
1) Detect that I still have a session open from earlier and reconnect me to it. 2) Open a brand new session, loading gnome as if I have just logged in. VNC, as I understand it, operates more like path 1, where someone has already logged in and it just connects to that session. NX actually creates a new session with whatever window manager I want and I get a brand new everything (unless I reconnect to an existing NX session). However, if I log into the machine with its own kb and mouse, NX will NOT connect to that existing session like VNC will. (unless I am mistaken, but I'm pretty sure that's how it works.) Does that help clear it up for you? If you want, you can download all of their linux installers for free to try it yourself. -Tyler -- policykit not available over NX sessions https://bugs.launchpad.net/bugs/238800 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
