*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
This is kind of old, but I just ran into it also.
I ended up finding the GID that was in error, but I also had to do
dpkg-reconfigure dbus as a reboot did not seem to correct the issue. after the
reconfig
OK, so that's just the result of a limitation in ConsoleKit. This is a
major problem, but that's more a feature request than a bug.
If you want, please open a report against the consolekit package - but I
don't think that will really help improve things, sadly. I'm closing
this bug because there
Milan, excuse me, but closing this report is ridiculous.
It is NOT at all a feature request. This is clearly a bug, a bad bug,
and it needs fixed.
A lot of research and symptoms are detailed in this report that will be
useful for those trying to fix this issue.
And the problem needs to be
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
Please read my comment carefully: did I say that wasn't a problem? Did I
say it shouldn't be fixed? The only point I made was that given the mess
we have created around the bug in this report, and given we
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
As the reporter, it seemed as if you were trying to push aside this bug.
I'm glad to hear that is not the case. Thank you.
I have no problem with it being marked as a duplicate of a true bug that
is for
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
On Sat, 03 Jul 2010 16:06:07 -, Milan Bouchet-Valat nalimi...@club.fr
wrote:
OK, so that's just the result of a limitation in ConsoleKit. This is a
major problem, but that's more a feature request than
How are the users supposed to get sudo powers if their are not in the
admin group? Anyway, with them not members of this group authenticating
via PolicyKit was clearly impossible. As I'm not familiar at all with
how ubuntu-server works, I may be good to find somebody who is, which
could explain
I logged out the user and started a new session:
I went to try accessing Users and Groups from the menu and got the same
behavior as before. Only the Password button for the current user
worked, nothing else.
$ ps
PID TTY TIME CMD
12237 pts/300:00:00 bash
12284 pts/300:00:00
So root is working, good point.
$ ps
PID TTY TIME CMD
12237 pts/3 00:00:00 bash
12994 pts/3 00:00:00 ps
$ pkcheck --action-id com.ubuntu.systemservice.setproxy
--allow-user-interaction --process 12994
Obviously this won't work, since 12994 is the PID of ps, which has died by the
time you call
$ ps
PID TTY TIME CMD
12237 pts/300:00:00 bash
19027 pts/300:00:00 ps
$ pkcheck --action-id org.freedesktop.systemtoolsbackends.set
--allow-user-interaction --process 12237
Not authorized.
$ pkcheck --action-id com.ubuntu.systemservice.setproxy
--allow-user-interaction
If ck-lists-sessions has active = False or is-local = False for your
session then
the default policykit config won't let you do most actions.
If you are sat at the machine then it indicates something wrong, if you are over
vnc/ssh/nx or something then it is expected, if undesireable, behaviour.
I am remote logged into the machine using vnc/ssh/nx and this behavior
is extremely undesirable.
Nobody would expect this type of behavior.
I have remote logged into machines for years like this and never saw
this type of behavior.
--
PolicyKit authentication always fails
# cat /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
[Configuration]
AdminIdentities=unix-group:admin
The users were not members of 'admin' group. I added them and reran the
tests. Still got the exact same results. It didn't seem to make any
difference.
$ ps
PID TTY TIME
13 matches
Mail list logo
