Ubuntu root user and lock screen issues

dnschneid / crouton

Chromium OS Universal Chroot Environment

https://goo.gl/fd3zc?si=1

BSD 3-Clause "New" or "Revised" License

8.56k stars 1.24k forks source link

Ubuntu root user and lock screen issues #1088

Closed NoPinky closed 9 years ago

NoPinky commented 10 years ago

I installed ubuntu with unity, chrome and some other targets. It starts and kind of works fine, but I encountered those issues:

eventhough I created a user at the start, I suppose this is a sudo user and not root. But, when I startup unity and try to start chrome, it says that I should not start chrome as root. But in terminal and on the top right of the desktop it says that I'm NOT logged in as root, but the sudo user I created.
after some idle time, Ubuntu/Unity went into standby and show me the lockscreen to sign back in. But it says that I'm logged in as root and asks me for the root password, which I don't know. The usual default passwords won't work (root, toor, admin, ubuntu, ...), and also the password for the sudo user won't work.

IceQubed commented 10 years ago

I'm not sure if this is the same issue but I am having similar difficulties - I installed ubuntu trusty with unity, and when starting it with "sudo startunity", it runs fine until I try to run any sudo commands (on my user account "ben@localhost"). It says that the password is incorrect despite me being sure it is right.

tista500 commented 10 years ago

Greetings,

Is this problem related to systemd on trusty? In my Utopic with final "stand-alone" systemd 204 series acts like this:

[   27.535824] systemd-logind[10511]: New seat seat0.
[   27.540705] systemd-logind[10511]: New session c1 of user root.
[   27.584446] systemd-logind[10511]: New session c2 of user c200.
[   32.896342] systemd-logind[10511]: Removed session c1.

I suppose the first phase of chrooting was kicked as root, and then systemd deal with your local-user account as c2 (sencond-session behind the root's initial session). So finally systemd closes root's session properly after siwtching user to your local one, maybe.

On gnome 3.14 "lock-screen" (latest git release), could accept for my local users's password normally though...

Best Regards, Tista

dnschneid commented 9 years ago

You're probably running sudo startunity within the chroot, which launches it as the root user. This is bad. Only use sudo startunity outside of the chroot, or it'll muck up your home directory permissions and lock the screen against an account that doesn't have a password set.