freenx-team team mailing list archive

[Jakob Unterwurzacher <jakobunt@xxxxxxxxx>]

** Description changed:

  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
  
- == Workaround == 
- If you are using NX from NOMACHINE:
-  - Install package from comment #24
-  - Follow instruction from comment #23
-  - Reload dbus conf by executing $sudo /etc/init.d/dbus reload
+ == Workaround ==
+ From https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/238799/comments/16 (the packages from comment 24 are broken links now):
  
- if you are using FreeNX:
-  - Install package from comment #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'
-  - Reload dbus conf by executing $sudo /etc/init.d/dbus reload
+ For system configuration, change all implicit authorizations under org
+ -> freedesktop -> systemtoolsbackends -> Manage System Configuration
+ (org.freedesktop.systemtoolsbackends.set) to "Admin Authentication."
  
- if you are using ssh -X:
-  - Install package from comment #24
-  - Reload dbus conf by executing $sudo /etc/init.d/dbus reload
-  - Execute the command by '/usr/bin/nx-session-launcher-suid SOME_PROGRAM'
+ For user management, change all implicit authorizations under org ->
+ freedesktop -> systemtoolsbackends -> self -> Change User Configuration
+ (org.freedesktop.systemtoolsbackends.self.set) to "Authentication."
+ 
+ Reset gdm by rebooting or running "sudo /etc/init.d/gdm restart" from a
+ terminal window, and you should be able to unlock the user settings
+ control panel and other similarly useful things through your tunneled
+ VNC session.

-- 
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: Fix Released
Status in PolicyKit: Confirmed
Status in “policykit” package 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

== Workaround ==
>From https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/238799/comments/16 (the packages from comment 24 are broken links now):

For system configuration, change all implicit authorizations under org -> freedesktop -> systemtoolsbackends -> Manage System Configuration (org.freedesktop.systemtoolsbackends.set) to "Admin Authentication."

For user management, change all implicit authorizations under org -> freedesktop -> systemtoolsbackends -> self -> Change User Configuration (org.freedesktop.systemtoolsbackends.self.set) to "Authentication."

Reset gdm by rebooting or running "sudo /etc/init.d/gdm restart" from a terminal window, and you should be able to unlock the user settings control panel and other similarly useful things through your tunneled VNC session.