freenx-team team mailing list archive

[Marcelo Boveto Shima <marceloshima@xxxxxxxxx>]

On Sat, Jul 26, 2008 at 4:57 PM, eye.zak <eye.zak@xxxxxxxxx> wrote:

> Check how Authorizations uses policy kit, you should be able to
> authenticate with NX. (Authorizations came from policykit).  Maybe
> users-admin and network-admin need to do things differently.
>

This error has already has been triaged and an workaround is available.

If you are using NX from NOMACHINE:
 - Install package from #24
 - Follow instruction from #23

if you are using FreeNX:
 - Install package from #24
 - Edit /etc/nxserver/node.conf and change
'#COMMAND_START_GNOME=gnome-session'
     to 'COMMAND_START_GNOME=/usr/bin/nx-session-launcher-suid
gnome-session'

Thanks

-- 
Policy Kit Unlock Buttons Greyed Out when using NX
https://bugs.launchpad.net/bugs/221363
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: Triaged
Status in PolicyKit: Unknown
Status in Ubuntu: New

Bug description:
I installed 8.04 LTS server on a system.  Then installed ubuntu-desktop using apt.  Installed Nomachine's NX server and connected to it.  

The unlock buttons on Users and Groups or Network are greyed out and un-accessible.  Tried running from a term 'sudo users-admin' with the same results.  

Works fine with VNC and NX "Shadow" session however this is not really acceptable as it means a session has to be running on console first.

I have tried to enable every option in Authorizations to allow the remote session to have privileges to no avail.

output of dpkg relevant packages:

ii  gnome-system-t 2.22.0-0ubuntu Cross-platform configuration utilities for G
ii  liboobs-1-4    2.22.0-0ubuntu GObject based interface to system-tools-back
ii  policykit      0.7-2ubuntu7   framework for managing administrative polici
ii  system-tools-b 2.6.0-0ubuntu7 System Tools to manage computer configuratio