(Solved) I can't login as root !!

[skidoo]

What does this mean? I cannot make any sense of it.

unsure whether zagreb999 is bled's moniker at puppy forum (similar, terse, strained English writing style), but I reckon the point was: "if ya wanna login as root, here's a nice//recommended puppy for ya to check out"

.
We don't know whether the OP is just (now) attempting to login as root in order to troubleshoot/fix an existing problem, or has been habitually logging into desktop session as root user (and clicking "stuff" exposed by the various MX Tools, which have been designed//tested for sudo usage, eh)

[fanisatt]

Thanks for all your replies to the moment.
It is not "only" a root login problem ! Only one user can login to his account !!!
It's the account I use mostly .
I remember that , I could login as root or as another user before the update from mx 17 to mx 18.
Perhaps , something happened here....

[Buck Fankers]

It is not "only" a root login problem ! Only one user can login to his account !!!
It's the account I use mostly .

Probably not related, but I had a similar problem in another distro. I could only log in with my testing account I created once. The reason for a problem was, I tried to remove ZHS (or is it ZSH?) to start using Bash again and I messed up something. Fix for me was restoring to the previous state with clonezilla. Probably not useful in this case, but though to mention this for just in case.

[male]

Thanks for all your replies to the moment.
It is not "only" a root login problem ! Only one user can login to his account !!!
It's the account I use mostly .
I remember that , I could login as root or as another user before the update from mx 17 to mx 18.
Perhaps , something happened here....

Can you please show the output of the terminal command:

Code: Select all

cat /etc/passwd

Thanks!

[fanisatt]

@male
(fanisatt is my account - working good , malakas is the second user account - can't login there)
Thanks !

This is the output :
root0:0:root:/root:/bin/bash
daemon1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin2:2:bin:/bin:/usr/sbin/nologin
sys3:3:sys:/dev:/usr/sbin/nologin
sync4:65534:sync:/bin:/bin/sync
games5:60:games:/usr/games:/usr/sbin/nologin
man6:12/var/cache/man:/usr/sbin/nologin
lp7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail8:8:mail:/var/mail:/usr/sbin/nologin
news9:9:news:/var/spool/news:/usr/sbin/nologin
uucp10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy13:13:proxy:/bin:/usr/sbin/nologin
www-data33:33:www-data:/var/www:/usr/sbin/nologin
backup34:34:backup:/var/backups:/usr/sbin/nologin
list38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc39:39:ircd:/var/run/ircd:/usr/sbin/nologin
gnats41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin
nobody65534:65534:nobody:/nonexistent:/usr/sbin/nologin
systemd-timesync100:102:systemd Time Synchronization,,,:/run/systemd:/bin/false
systemd-network101:103:systemd Network Management,,,:/run/systemd/netif:/bin/false
systemd-resolve102:104:systemd Resolver,,,:/run/systemd/resolve:/bin/false
systemd-bus-proxy103:105:systemd Bus Proxy,,,:/run/systemd:/bin/false
_apt104:65534::/nonexistent:/bin/false
usbmux105:46:usbmux daemon,,,:/var/lib/usbmux:/bin/false
ntp106:110::/home/ntp:/bin/false
messagebus107:112::/var/run/dbus:/bin/false
statd108:65534::/var/lib/nfs:/bin/false
nm-openconnect109:117:NetworkManager OpenConnect plugin,,,:/var/lib/NetworkManager:/bin/false
nm-openvpn110:118:NetworkManager OpenVPN,,,:/var/lib/openvpn/chroot:/bin/false
avahi111:120:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false
colord112:121:colord colour management daemon,,,:/var/lib/colord:/bin/false
saned113:123::/var/lib/saned:/bin/false
pulse114:124:PulseAudio daemon,,,:/var/run/pulse:/bin/false
lightdm115:126:Light Display Manager:/var/lib/lightdm:/bin/false
hplip116:7:HPLIP system user,,,:/var/run/hplip:/bin/false
fanisatt1000:1000:fanisatt,,,:/home/fanisatt:/bin/bash
debian-deluged117:127::/var/lib/deluged:/bin/false
festival118:29::/home/festival:/bin/false
ftp119:129:ftp daemon,,,:/srv/ftp:/bin/false
sshd120:65534::/run/sshd:/usr/sbin/nologin
malakas1001:1001:malakas,,,:/home/malakas:/bin/bash

[fanisatt]

@Buck Fankers
Thanks for your reply !!

[Adrian]

You can use [code][/code] tags to make sure that the text you paste show up correctly... that being said, I don't see anything wrong with that.

[baldyeti]

Could you perhaps just check that root's home directory still exists:

Code: Select all

ls -lad /root/

[dolphin_oracle]

Could you perhaps just check that root's home directory still exists:

Code: Select all

ls -lad /root/

not to mention the new user's home folder. depending on how you made the user, a new user directory might not exist. which would prevent X from starting, but you could probably still login from the console I would think. you can do the same command on /home

Code: Select all

ls -lad /home

[fanisatt]

Thank you all for your interest.
The root directory was ok and the other user's directory was ok too , I could see the files with thunar (as root) but the accounts were locked !!!
I don't care anymore (to the moment...) because I have already installed MX-18 . Anyway I think that some things about this issue have to be examined more carefully by the MX team.
There are a lot of nice tools here but .... the root and one user's accounts were locked by the system, rather unreasonably and no tool could solve this unjustifiable situation.
Best Regards.
(Solved)