users-admin is part of this package.
** Package changed: ubuntu => gnome-system-tools (Ubuntu)
--
maverick - 'user settings' hangs being root
https://bugs.launchpad.net/bugs/643153
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-sy
Reverting to gnome-system-tools 2.30.0-0ubuntu2 (from Lucid) does make a
difference. I also needed to install liboobs-1-4 2.30.0-0ubuntu1.
It eventually works, but outputs this warning:
(users-admin:3551): Liboobs-WARNING **: There was an unknown error
communicating asynchronously with the backen
Sorry, but we don't support logging in as the root user. This is highly
unsecure and strongly discouraged. I'm not sure what may be happening,
but it's possible something like a D-Bus policy is blocking messages
from being sent to root. You may want to have a look at
/var/log/auth.log for such erro
Milan, I was talking about running "gksu users-admin" rather than
logging into a session as root. It is not obvious why that use-case
would not be supported.
At least one other user is seeing the same:
http://ubuntuforums.org/showthread.php?t=1585421
"In addition, when I run users-admin with a no
I just created bug #667151 which may be related.
--
maverick - 'user settings' hangs being root
https://bugs.launchpad.net/bugs/643153
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
desktop-bugs mailing
No, using gksu is a deprecated method for a long time, instead programs
are now run as a normal user, and get admin rights using PolicyKit. In
Maverick, this is for example how updates-manager works.
You're not supposed to run 'gksu users-admin', and I really don't see
how you'd think of doing so.
@Milan: Dude, we all appreciate the great work you're doing.
But stating that you won't correct a bug and tag it as invalid just because you
feel people dont program your way is a bit outrageous and reactionary (even if
I agree with your "should not log as root" statement...). It is irrelevant th
If you think it's more fair, I can mark it as Triaged. But IMHO that's
as fallacious as Invalid since I know I won't fix it and nobody will now
that the gst are deprecated upstream.
(Of course, hadn't it been deprecated, the easy fix would have been to
exit when we detect user is root. ;-)
** Cha