*** This bug is a duplicate of bug 210897 ***
https://bugs.launchpad.net/bugs/210897
I have experienced this bug both on 8.04 Hardy and still on 9.04 Jaunty.
Administrator cannot unlock System->Administration->Users & Groups while login
in from a remote desktop such as XDMCP or NX.
We are e
*** This bug is a duplicate of bug 210897 ***
https://bugs.launchpad.net/bugs/210897
** This bug has been marked a duplicate of bug 210897
sudo *something which uses poliykit?* doesn't work
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You receive
Confirming. I can reproduce this on Hardy and there are duplicates.
** Changed in: policykit (Ubuntu)
Status: New => Confirmed
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a member of Ubuntu
Bug
This is on Hardy Heron, from an LTSP terminal. I ran sudo users-admin
and received the message:
** (users-admin:15898): CRITICAL **: Unable to lookup session
information for process '15898'
In a separate terminal, I looked up in the information:
[EMAIL PROTECTED]:~$ sudo cat /proc/15898/environ
Hi,
Apparently this is a problem with consolekit being
able to look-up the XDG_SESSION_COOKIE.
Could someone who has the problem and gets the message
'Unable to lookup session information for process' please run
"users-admin" from a terminal, and then "cat /proc//environ"
where "" is the number p
On Wed, 2008-07-09 at 15:18 +, LuisMondesi wrote:
> This bug hit me with a fresh installation of Ubuntu Hardy and 2 things
> were noticeable:
>
> 1. USB volumes did not automount (that includes iPods and stuff)
> 2. all the *-admin utilities would not allow me to authenticate. The button
> wa
This bug hit me with a fresh installation of Ubuntu Hardy and 2 things
were noticeable:
1. USB volumes did not automount (that includes iPods and stuff)
2. all the *-admin utilities would not allow me to authenticate. The button was
just gray-out.
To fix this I did:
1. start in single-user-mode
OK I re-enabled gdm using 'System --> Administration --> Services' and
now it starts up automatically when my system boots up. This gives me a
workaround so that my admin utilities now allow me to authenticate with
the 'Unlock' button. However, I would still like to know how to fix the
bug without
On Wed, 2008-07-02 at 16:53 +, irotas wrote:
> Yeah if I run 'sudo /etc/init.d/gdm start' from the console, everything
> works OK with PolicyKit/ConsoleKit.
>
> Now I'm trying to remember how I disabled gdm in the first place so I
> can have it start up automatically when I boot up the compute
Yeah if I run 'sudo /etc/init.d/gdm start' from the console, everything
works OK with PolicyKit/ConsoleKit.
Now I'm trying to remember how I disabled gdm in the first place so I
can have it start up automatically when I boot up the computer.
Alternatively, maybe there's a way to do it with .xinit
that's likely the reason why that's not working, nothing is setting the
session correctly
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Hi Sebastien,
I actually don't use any login manager. I start X simply using 'startx'.
-$ cat ~/.xinitrc
gkrellm &
exec dbus-launch --exit-with-session gnome-session
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification becaus
Hi Michael,
Your problem seems to be the same as bug 219473.
Thanks,
James
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Here's my output of the same:
[EMAIL PROTECTED]:~# polkit-auth --show-obtainable
[WARN 26160] kit-hash.c:206:kit_hash_insert(): key != NULL
Not built with -rdynamic so unable to print a backtrace
[WARN 26160] kit-hash.c:294:kit_hash_lookup(): key != NULL
Not built with -rdynamic so unable to pri
do you use non local applications? that could be bug #183673 or similar
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
there is something broken about your installation and that's not due to
gnome-system-monitor, the comments show that you have no active
consolekit session, what login manager do you use?
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug
I ran network-admin with dbus-monitor running. I'm not sure if this
offers any useful information, but here's the output:
signal sender=org.freedesktop.DBus -> dest=(null destination)
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=NameOwnerChanged
string ":1.119"
string
Sorry for the delay - I've been on travel for several weeks and just now
am getting back to troubleshooting this.
Per Sebastien Bacher's suggestion:
$ polkit-auth --show-obtainable
-$ ck-list-sessions
-$ cat /etc/PolicyKit/PolicyKit.conf
http://hal.freedesktop.org/releases/PolicyKit/1.0/c
no debian policykit. it was installed with hardy. it was just an upgrade
from up-to-date gutsy to hardy. but there's lots of weird stuff with the
upgrade, which (like with the upgrade to gutsy from feisty before)
doesn't update many config settings, the menu bar, etc. and there seems
no way to get
did you install a debian policykit version or something? it's weird that
your configuration doesn't list the admin group where it should
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a member of Ubuntu
Bu
On Mon, 2008-06-09 at 09:09 +, rishab wrote:
> sebastien bacher wrote:
>
> > could you run "polkit-auth --show-obtainable" and "ck-list-sessions"
> and copy the logs to the bug?
>
> ok, i ran it with the default /etc/PolicyKit/PolicyKit.conf file...
> [header comments.]
>
>
>
>
>
sebastien bacher wrote:
> could you run "polkit-auth --show-obtainable" and "ck-list-sessions"
and copy the logs to the bug?
ok, i ran it with the default /etc/PolicyKit/PolicyKit.conf file...
[header comments.]
$ polkit-auth --show-obtainable
org.gnome.clockapp
could you run "polkit-auth --show-obtainable" and "ck-list-sessions" and
copy the logs to the bug?
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*bump*
i'm puzzled why this bug still has an "undecided" status.
i've tried a number of upgrades from gutsy to heron, and heron basically
is unusable for many things because of this. the defaults for policykit
seem to be totally wrong when upgrading from gutsy. so no wifi, no time
setting, no aut
Is there really no fix for this problem? For a month now I can't use any
of the Ubuntu admin utilities. This is very frustrating! :(
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a member of Ubuntu
Bugs,
I've come accross the same bug with freenx. I guess somehow gtk or gnome
initialization fails. E.g. time-admin gives the following error message
when started from a freenx desktop within a shell:
** (time-admin:6522): CRITICAL **: Unable to lookup session information
for process '6522'
The error
*bump*
This bug also occurs when using LTSP as an administrator logged in from
a thin client and not directly at the console.
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a member of Ubuntu
Bugs, which
Unfortunately the /etc/hosts modification had no effect. :(
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
I've found that this happens only when I connect to the Ubuntu machine
using NX (with the "Desktop" setting set to Unix -> GNOME). If I log in
locally or use the "Shadow" option of NX that connects to an existing
console session, the unlock button works fine.
Through NX I get the same "Unable to
Somebody says
127.0.0.1 localhost
127.0.1.1
works well. (https://bugs.launchpad.net/bugs/194496).
So it would be:
127.0.0.1 localhost jake
127.0.1.1 jake
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you ar
If it doesn't work try to change it e.g. to
127.0.0.1 localhost
127.0.1.1 jake jake
or
127.0.0.1 localhost
127.0.1.1 jake localhost
or sth. similar.
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bug notification because you are a mem
... although to be safe I'd rather declare a domain as showed
previously, e.g.
127.0.0.1 localhost
127.0.1.1 aaa.bbb.com jake
Playing with the hosts file is not for the faint-hearted ...
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
You received this bu
Thanks for the comment. Here's my /etc/hosts:
-$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 jake
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff0
Have you checked /etc/hosts. With hardy, the initial entry was something
like:
127.0.0.1 localhost
127.0.1.1 aaa.bbb.com
when it should be
127.0.0.1 localhost
127.0.1.1 aaa.bbb.com
This solved it for me.
--
'Unlock' button in admin utilities greyed out
https://bugs.launchpad.net/bugs/231246
** Attachment added: "Starting network-admin from terminal"
http://launchpadlibrarian.net/14566626/network-admin.png
** Also affects: policykit (Ubuntu)
Importance: Undecided
Status: New
** Also affects: policykit-gnome (Ubuntu)
Importance: Undecided
Status: New
--
'Unlo
If it matters:
-$ apt-cache policy policykit-gnome
policykit-gnome:
Installed: 0.7-2ubuntu1
Candidate: 0.7-2ubuntu1
Version table:
*** 0.7-2ubuntu1 0
500 http://us.archive.ubuntu.com hardy/main Packages
100 /var/lib/dpkg/status
--
'Unlock' button in admin utilities greyed o
36 matches
Mail list logo