*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
** Changed in: policykit
Status: Confirmed = Invalid
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
** This bug has been marked a duplicate of bug 221363
Policy Kit Unlock Buttons Greyed Out when using NX
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received
I had this issue as well while trying to use System - Administration
- Services with a user/member of the 'admin' group, using VNC and LTSP
clients.
Please see comment #14 at
http://ubuntuforums.org/showthread.php?p=8001955#post8001955 for my
workaround.
This seems to be a default Ubuntu polkit
It is our opinion that the importance assigned for this bug should be higher.
This problem prevents efficient remote administration of systems and servers
though a graphical interface and indicates risks for weaknesses in the
authorization mechanisms in Ubuntu.
This is pretty serious since we
Additionally to setting the Must Be In Active Session option to
None, I also had to set the Implicit Authentication for anyone to
Admin Authentication before this would work.
I'm using Jaunty 64bit Server with LTSP. Now I can access users-admin
via and ssh -X session and also from a thin client
Contrariwise to what Alessandro Rinaldi wrote on 2008-10-20, the work-around
proposed by gord-s on 2008-09-18 does work for me via LTSP5 on ubuntu 8.04.
Indeed, logged in via LTSP, I perform the ssh -X again into the LTSP server and
grant rights to myself. After that, it all works well as
This is a follow-up to my above post.
Only after reading Karl Rosenbaum's post from 2008-12-06, I recalled that
indeed I had replaced the Must Be In Active Session option by None as well.
With that option, it works well as described in my previous post.
St. Mueller
--
no policykit access on
Holden,
Thank you!
I created the following rule and now it is working as expected:
-
SUBSYSTEM==usb, ATTR{idVendor}==04a9, ATTR{idProduct}==2220,
SYMLINK+=%k, GROUP=scanner
-
As you can see, instead of giving a 777 permissions, I changed scanner's
group, thus only
Holden Hao,
**
Other note:
Access to local devices on the server such as a scanner exhibit similar
behavior. Users can use the scanner if directly logged in to the server.
However, from their remote x-sessions, Xsane can not detect the scanner. This
is true even if implicit policy kit access
Did you post this info in another bug? I tried to find it but in vane.
The issue with the scanner is very important for me and the lack of
solution forces me to stay on Ubuntu 7.10, now that even 9.04 is on its
way. I created another bug about this. So far no solution.
I cheated. I simply
The Must Be In Active Session option didn't work for me, but if I
chose None instead it works as described by gord-s.
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Perhaps worth noting is that I have seen the same problem for locally
connected terminals with MultiseatX on 8.04. Seems that policykit only
works for a local console on a single terminal system.
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received this
This workaround doesn't work for me on both LTSP and ssh -x accesses...
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
this worked-around/solved it for me:
I log in as myself over an ssh -X session, then do sudo
polkit-gnome-authorization. On the screen that opens (via the forwarded X
session), I then allow myself to admin things _remotely_, rather than at a
physical session at the server.
The setting to
This problem affects us as well, we are using Ubuntu 8.04.1 64 bit, with
LTSP 5, and can no longer perform administrative tasks via the GUI. I
can use the command line, but this change makes life very inconvenient,
especially since our servers are headless...
--
no policykit access on ltsp thin
** Description changed:
Not sure if this should be pinned to policykit or the ltsp project.
The unlock button does not work in control panels such as users
settings on thin clients. Is it possible to implement this? Is this a
bug or a feature? Some of my staff are administrators and
Hi Holden,
Please file a new bug as you appear to have a different
problem. You have a valid consolekit session, it's just
marked as inactive and remote, so the policy won't accept
it. We need to work out why that is.
Thanks,
James
--
no policykit access on ltsp thin client
I just wanted to add that this affects remote X-logins as well. When I
am logged in through GDM from a different computer the unlock button in
the users administration GUI is also grayed out.
Here are some data:
Ubuntu Hardy Heron
--installed from server 64
--apt installed ubuntu-desktop
Hi,
I've found a possible reason for this behaviour, so I have filed an
upstream bug, and I will wait for the author's reaction.
It's possible that this isn't the cause of the bug for you, but it
is a good place to start.
Thanks,
James
** Bug watch added: freedesktop.org Bugzilla #16340
** Changed in: policykit
Status: Unknown = Confirmed
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi David,
Thanks for the extra information. Do you know which of the sessions
listed in the ck-list-sessions output is the one that you ran the second
command on?
I expect the problem has something to do with the output of the second
command though. I don't know from where the error comes, but
There were users logged in on 2 thin clients at that time and nobody on the
server. For some reason the first command listed 2 sessions per logged-in
user. Both commands were run by uid 1000, so session 4 or 5.
I should also mention that the network in question uses the
LDM_DIRECTX=True option in
# ck-list-sessions
Session4:
uid = '1000'
realname = 'David ,,,'
seat = 'Seat4'
session-type = ''
active = TRUE
x11-display = 'localhost:12.0'
x11-display-device = ''
display-device = '/dev/pts/1'
remote-host-name =
Hi,
I believe that there may be a few separate issues going on here,
though they may have the same root cause. Namely, we have people
using
1. ltsp
2. Vnc
3. NX
where ltsp apparently uses ssh.
Fixing this may require fixes in three places and if so I would like to
split this bug report
Hi,
Sorry, there was a copy and paste error in my last comment,
the NX bug is bug 238800.
Thanks,
James
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am having this problem too, but it also manifests itself in other ways
when connected via thin client (NX) such as being unable to mount my
iPod to use in Amarok - which works perfectly if connected locally to
the computer.
--
no policykit access on ltsp thin client
same here, fresh 8.04 install through NX server. Headless machine, so
editing directly on server not an option.
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
same here, fresh 8.04 install through NX server. Headless machine, so
editing directly on server not an option.
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same thing here!
And it's really annoying to login to the server each time I need to do
something! :-)
--
no policykit access on ltsp thin client
https://bugs.launchpad.net/bugs/219473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*Bump* -- Same here. I've tried, from the console, clicking 'Allow
remote system administrator login' in gdmsetup-Security tab but this
makes no difference.
With FC6 I exclusively used a separate computer to administer the
server, via NX as well as logging in from a thin terminal. Both of these
This also occurs when using NoMachine (another VNC-like remote desktop
app). This bugs make administering headless boxes very difficult. I'm
using Ubuntu 8.04 LTS desktop. Just installed latest patches and
rebooted.
--
no policykit access on ltsp thin client
I've seen this problem when I install Xvnc (vnc4server) and attach to
the host. Local display (via terminal screen) allows me to unlock users
groups, or 'system services'. When I vnc I cannot unlock as the
button is greyed out. This is a pain and doesn't exist in Ubuntu, only
my first
32 matches
Mail list logo
