** 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.
33 matches
Mail list logo
