*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
Michael:
I found the same problem with a machine on which Karmic had been clean-
installed and I, too, like to have a login for root. On another
machine, where I had set up a root login previously in
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
David: what's your problem exactly? You can set up a password for root
in Karmic too, it's just that PolicyKit won't allow you to enter the
root password to authenticate. I fail to see how upgrading from
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
While I agree that the correct policy would be to (after a clear
warning) allow password-less accounts...
'Documentation' in this case should be a CLEAR error message triggered
by this combination of events:
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
That would be a PolicyKit bug. Feel free to provide a patch if you think
that feature is worth the pain - or go and discuss that on their mailing
list. I don't think anybody else will spend time on that as we
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
Where would we document this? Do you think we should add a bug red
warning on every authentication dialog explaining what we don't want
users to do?! The right way is to allow password-less accounts to be
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
The user logged in at the time was NOT root. As I described, I had
created a root password (I like su better than sudo -s, and local root
login is nicer for servicing a system than the potential alternative
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
I should clarify, this is an issue I encountered trying to unlock the
privileged mode of system administration tasks. As an example,
adding/modifying users/groups with the tool found in the system menu.
It
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
I like su better than sudo -s,
Without more precise reasons for that, please understand we can't take that
request into account There are no downsides of using 'sudo -s' versus su.
and local root login is
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
Having this behavior isn't in it's self a bug. Not /documenting/ the
behavior properly in dialogs related to system administration tools /is/
a bug. Additionally when root ==HAS A PASSWORD== it is a valid
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33849674/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/33849675/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/33849676/ProcStatus.txt
--
Unable to
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
As you half-guessed, most of what you report here is intentional. Namely:
1) we don't want people to log in as root using GDM - logging through the
console could make sense, but never using a GUI, where many
11 matches
Mail list logo
