** Changed in: gdm
Status: New => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
To manage notifications
I've just installed 16.04LTS and confirmed this problem still exists.
And there's no org.freedesktop.SystemToolsBackends.policy in
/usr/share/polkit-1/actions.
I tried to find related policy, but I couldn't.
Is there any workaround to fix this with polkit settings like
Since noone has answered for 4 months, and since some related commits
have been made, I'm marking it fix released in LTSP.
** Changed in: ltsp (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is this still an issue in recent Ubuntu/LTSP versions?
** Changed in: ltsp (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit
** Also affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit Unlock Buttons Greyed Out when using NX / VNC /
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ltsp (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy
Derek:
The criteria is that you hit this bug on a certain package. ;-)
I think most packages should be fixed, even if a small minority should keep
using allow_active: it can only be useful when e.g. managing hardware, sound,
mounted devices, etc. In these cases, only the current user should be
Milan said in #62: Have a look at files in /usr/share/polkit-1/actions/
and try to guess what are the files you need to edit. Then it's probably
useful to file bugs so that it's fixed upstream, if applicable.
What are the criteria to know what files need to be edited? I saw
I'm unsure as well, and given the fact that my gdm bug report is still
listed as UNCONFIRMED after 4+ months, so I'm not too
motivated/encouraged at this point to perform the legwork necessary to
report this issue everywhere.
It also doesn't do a single thing to prevent future developers from
On 11.04, I was able to get around this problem by setting my NX client
to launch gnome-session --session=classic-gnome .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit
** Changed in: gdm
Status: Unknown = New
** Changed in: gdm
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit Unlock Buttons Greyed Out
I'm seeing this issue with both Maverick and now Natty with x2goserver-
one.
jhansonxi's fix doesn't work for me.
I'm using system-tools-backends 2.10.1-2ubuntu1, so maybe Milan's fix
will flow down soon?
What's the best workaround at this point?
--
You received this bug notification because
Ben: Edit
/usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy,
and replace all allow_active with allow_any. The fix isn't likely to
enter Natty at this point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Milan: Thanks. That seems to have at least partially fixed things, as
update-manager and users-admin are now properly prompting for password
and allowing access to locked items.
Unfortunately the Unlock button of gdmsetup still doesn't work, but
maybe something else is going on there? If I run it
Ben: Of course, you'll need to make the change for every action that
doesn't work. gdmsetup uses a different PolicyKit action. Have a look at
files in /usr/share/polkit-1/actions/ and try to guess what are the
files you need to edit. Then it's probably useful to file bugs so that
it's fixed
Thanks again. I was able to fix gdmsetup by making the suggested changes
to gdm.policy.
I'd happily submit a bug report if I knew where and what to report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update: Submitted a report to the GNOME bug tracker (
https://bugzilla.gnome.org/show_bug.cgi?id=649042 ) and linked this bug
to both that report and the gdm project entry here on launchpad.
** Bug watch added: GNOME Bug Tracker #649042
https://bugzilla.gnome.org/show_bug.cgi?id=649042
**
** Changed in: policykit
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
--
** Changed in: policykit
Importance: Critical = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
--
Instead of directly editing policy files (which may get overwritten on
updates), try the attached pkla file (manpage: pklocalauthority). Put
this in /etc/polkit-1/localauthority/50-local.d with root ownership.
** Attachment added: remote.freedesktop.SystemToolsBackends.pkla
This also affects X2go (package from repo at http://wiki.x2go.org
/installing_x2goserver-home_ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit Unlock Buttons Greyed
** Also affects: system-tools-backends
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit Unlock Buttons Greyed Out when using NX /
I've eventually pushed the allow_any fix to the system-tools-backends
upstream, it should be available in 2.10.2 for Natty.
Somebody should really go over all actions from
/usr/share/polkit-1/actions/ and file a new bug task for all actions
that don't consider allow_any as a valid case without a
Seeing the problem continuing on 10.10, unlock button for gnome
useradmin disabled when logging in through freenx
--
Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
https://bugs.launchpad.net/bugs/221363
You received this bug notification because you are a member of Ubuntu
Bugs,
OK, so according to upstream it's not a bug in PolicyKit, but in the
services that specify allow_active instead of allow_any. Of course,
it would be better if ConsoleKit detected remote sessions as active, but
there's no reason anyway why the system-tools-backends shouldn't be
available to
The workaround for Karmic or newer does not work on Maverick server
install with ubuntu-desktop added via tasksel. Has anybody had success
with it or found a different workaround? Should I file a new bug?
--
Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
Using polkit-gnome-authorization doesn't work for me (it only displayes the
org.freedesktop.policykit tree), neither does editing
/usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy or
/etc/PolicyKit/PolicyKit.conf
I think this might be because of policykit doesn't parse
Razvan: polkit-config-file-validate is for PolicyKit0, while Lucid is
(mosty) using the incompatible PolicyKit1. So ti's expected that config
files cannot be parsed correctly by this tool. Same for polkit-gnome-
authorization, which doesn't work with PolicyKit1, and won't show its
actions.
In the
Milan: sorry for the confusion, I did check with an apt-cache show
system-tools-backends and man polkit-config-file-validate but nothing in there
suggested whether these files are complementing, obsolete or conflicting with
policykit-1
As for the problem: it is the same as the one detailed
Unsubscribing ubuntu-sponsors, as this isn't ready for sponsorship yet,
we need some debdiffs.
https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue
--
Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
https://bugs.launchpad.net/bugs/221363
You received this bug notification
** Summary changed:
- Policy Kit Unlock Buttons Greyed Out when using NX
+ Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
--
Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
https://bugs.launchpad.net/bugs/221363
You received this bug notification because you are
Patch tested by another LTSP User: http://thread.gmane.org/gmane.linux
.terminal-server.general/27584/focus=27651
So the question is: Is it clever to disallow remote sessions to use the GUI
admin tools. What's the point? Members of the admin group can sudo -s anyway.
At least the LTSP packages
You forgot to add ssh -X to the title. Yes, it is a bad decision, in
my opinion.
--
Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
https://bugs.launchpad.net/bugs/221363
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached patch enables remote users to unlock the dialog.
Apply the patch:
sudo cp -a
/usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy
/usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy.ori
sudo patch
** Tags added: patch
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: policykit-1 (Ubuntu)
Status: New = Confirmed
** Changed in: policykit (Ubuntu)
Status: New = Confirmed
--
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 Ubuntu
** 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
** 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
** Changed in: policykit
Status: Confirmed = Invalid
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** 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
https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/238799/comments/16
Note: This should work, but be cautious as it does change the security
policy from the default. Use only if you have trustworthy remote users.
--
Policy Kit Unlock Buttons Greyed Out when using NX
Nice fix Marcelo, worked great for me!
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm using the NX Free Edition Server on Intrepid, and when I try to
install the latest freenx-session-launcher from the repository, it
errors out. The older deb package installs, but I get the black screen
when trying to create a new session.
--
Policy Kit Unlock Buttons Greyed Out when using
For SSH sessions I'd like to add that the error still persists here.
Nastyly it's happening for me on a laptop with broken display that I use
as a server (no graphical login). So I'm -- among others -- not able
to add users or change time.
While reading here I couldn't find a solution that would
Was using Marcelo's workaround until I upgraded the system in question
to Intrepid. I could not create a new session after upgrading. The
nomachine client would display a black screen and then immediately exit
after logging in. I have reverted back to the old node.cfg until an
I supposing you are using NoMachine NX Free edition.
So add the repository:
deb http://ppa.launchpad.net/freenx-team/ubuntu intrepid main
And use the freenx-session-launcher from this repository.
On Mon, Nov 3, 2008 at 8:34 PM, NTolerance [EMAIL PROTECTED] wrote:
Was using Marcelo's workaround
Closing the FreeNX task, it is fixed in FreeNX 0.7.3
** Changed in: freenx-server
Status: Triaged = Fix Released
--
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 Ubuntu
Bugs, which
** 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
Marcelo Boveto Shima wrote:
** 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.
Hi,
Please don't close the Ubuntu task, this is still a problem with
Ubuntu.
Thanks,
James
** Changed in: ubuntu
Status: Invalid = New
--
Policy Kit Unlock Buttons Greyed Out when using NX
https://bugs.launchpad.net/bugs/221363
You received this bug notification because you are a
** Changed in: policykit (Ubuntu)
Sourcepackagename: None = policykit
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
closing Ubuntu task
** Changed in: ubuntu
Status: New = Invalid
** 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
** Also affects: policykit via
https://bugs.freedesktop.org/show_bug.cgi?id=16510
Importance: Unknown
Status: Unknown
--
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 Ubuntu
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.
--
Policy Kit Unlock Buttons Greyed Out when using NX
https://bugs.launchpad.net/bugs/221363
You
** Changed in: freenx
Importance: Undecided = Medium
Status: New = Triaged
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On Sat, Jul 26, 2008 at 4:57 PM, eye.zak [EMAIL PROTECTED] 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
** Changed in: policykit
Status: Unknown = Confirmed
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I think that must be repaired in the PolicyKit, not in the
NX/FreeNX/SSH
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
But i will try it...:)
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Indeed, PolicyKit should be repaired to allow a remote sessions permission to
do something.
But FreeNX/NX must be fixed to create a valid session.
My solution corrects FreeNX/NX but just workaround PolicyKit problem.
But I must say that in some cases this solution has a SECURITY IMPLICATION.
After installing the above package and making the change to
/usr/NX/etc/node.cfg I am able to use PolicyKit remotely.
Nicely done Marcelo!
--
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
@Marcelo: Just realized you fixed FreeNX. Not nomachines NX. Wonder
if I should switch. I tried to change Nomachines nxnode config to use
your nx-session-launcher but it doesn't work, just crashes.
Are you confirming this is a problem with NX though and not policy kit
or is this a band-aid
@Marcelo: I don't have a /etc/nxserver/node.conf. Did a search and
node.conf is not found on my system at all.
Any ideas?
--
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 Ubuntu
Bugs,
Do you use any package or is built from scrap?
Try to change this line on the file /usr/bin/nxloadconfig
--
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 Ubuntu
Bugs, which is subscribed to
Try to chance the session configuration on nxclient to unix-custom instead of
unix-gnome.
In application put /usr/bin/nx-session-launcher-suid on 'run the following
command' and 'New virtual desktop' on options
Or maybe there is a configuration file on /usr/NX/etc
--
Policy Kit Unlock Buttons
Tried with both:
edit /usr/NX/etc/node.cfg and add /usr/bin/nx-session-launcher to the COMMAND
directive. NX crashes on connect.
changed my client profile to custom and added /usr/bin/nx-session-
launcher-suid as the launched application and NX doesn't crash but no
desktop is drawn. Just the
volksman wrote:
@Marcelo: Just realized you fixed FreeNX. Not nomachines NX. Wonder
if I should switch. I tried to change Nomachines nxnode config to use
your nx-session-launcher but it doesn't work, just crashes.
Are you confirming this is a problem with NX though and not policy kit
or
True enough. So the problem is really with PolicyKit and Marcelo's fix
is a band-aid for FreeNX.
--
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 Ubuntu
Bugs, which is subscribed to
I forgot to tell that ck-session launcher is compiled for i386.
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
A proof of concept, you can try it on a NX session:
[EMAIL PROTECTED]:~$ ck-list-sessions
Session1:
uid = '1000'
realname = 'Marcelo Boveto Shima,,,'
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device =
The problem with PolicyKit is that it don't alow a remote session to have
privileges.
I already filled a bug while hacking the solution at
https://bugs.freedesktop.org/show_bug.cgi?id=16510.
SSH creates a remote session. NX don't creates a session (my solution creates a
session on ConsoleKit,
I've created a package to be used with NX Free edition.
But you have to edit /usr/NX/etc/node.cfg and change:
- CommandStartGnome=/usr/bin/dbus-launch --exit-with-session gnome-session
to
- CommandStartGnome=nx-session-launcher-suid gnome-session
The package is in the building queue, once it
The packages are:
http://launchpadlibrarian.net/15610243/freenx-session-launcher_0.7.2-0ubuntu0ppa16_amd64.deb
and
http://launchpadlibrarian.net/15608046/freenx-session-launcher_0.7.2-0ubuntu0ppa16_i386.deb
--
Policy Kit Unlock Buttons Greyed Out when using NX
Forgot to mention that the dbus daemon need to reload the configs by executing:
$ /etc/init.d/dbus reload
--
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 Ubuntu
Bugs, which is subscribed
This problem also occurs when you use 'ssh -X' and try and run 'users-
admin' for example. There is no way to admin a Hardy system via ssh
using the GUI tools.
--
Policy Kit Unlock Buttons Greyed Out when using NX
https://bugs.launchpad.net/bugs/221363
You received this bug notification because
I just made a way to make it work.
The problem is that PolicyKit verify if you are on a valid/local/active
ConsoleKit session.
To correct the problem follow this steps:
- Copy nx-session-launcher and nx-session-launcher-suid to /usr/bin
- Execute $ chown nx /usr/bin/nx-session-launcher-suid
-
** Attachment added: nx-session-launcher
http://launchpadlibrarian.net/15573028/nx-session-launcher
--
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 Ubuntu
Bugs, which is subscribed to
** Attachment added: ConsoleKit-NX.conf
http://launchpadlibrarian.net/15573031/ConsoleKit-NX.conf
--
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 Ubuntu
Bugs, which is subscribed to
I am having this problem too.
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Please let me know if a fix is available.
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: freenx
Importance: Undecided
Status: New
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Please let me note that I'm interested in a solution for this problem,
too.
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Please disregard first two comments. I had originally filed this bug as
a bug with policykit not working at all before I realized that NX could
be interfering.
This has been confirmed by a number of people in the forums:
http://ubuntuforums.org/showthread.php?t=712006
** Summary changed:
-
83 matches
Mail list logo
