[upstream bug] Just Installed Endeavour os and I cannot login in sddm

General system EndeavourOS installation
1

Hi
I just installed endeavour os with kde and mate
When I start (I didn’t touch anything is a fresh install) I cannot login in the graphical environment
But if I go in a terminal (ctrl alt F3) I can login correctly

Is not a password issue I checked my password in my username field and is correct

if I lock at the logs I got this errors:

journalctl /usr/bin/lightdm
– Logs begin at Sat 2020-10-24 11:10:45 IST, end at Sat 2020-10-24 12:38:57 IST. –
Oct 24 11:34:33 nick-archzephG14 lightdm[3480]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=972) by (uid=0)
Oct 24 11:34:37 nick-archzephG14 lightdm[3546]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=damnick
Oct 24 11:34:37 nick-archzephG14 lightdm[3546]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 24 11:35:01 nick-archzephG14 lightdm[3554]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=damnick
Oct 24 11:35:01 nick-archzephG14 lightdm[3554]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 24 11:37:18 nick-archzephG14 lightdm[3555]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=damnick
Oct 24 11:37:18 nick-archzephG14 lightdm[3555]: pam_systemd_home(lightdm:auth): Not a user managed by systemd-homed: No home for user damnick known
Oct 24 11:43:35 nick-archzephG14 lightdm[3480]: pam_unix(lightdm-greeter:session): session closed for user lightdm
– Reboot –
Oct 24 12:16:52 nick-archzephG14 lightdm[3275]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=972) by (uid=0)
Oct 24 12:17:08 nick-archzephG14 lightdm[3347]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=damnick
Oct 24 12:17:08 nick-archzephG14 lightdm[3347]: pam_systemd_home(lightdm:auth): Not a user managed by systemd-homed: No home for user damnick known
Oct 24 12:17:15 nick-archzephG14 lightdm[3349]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=damnick
Oct 24 12:17:15 nick-archzephG14 lightdm[3349]: pam_systemd_home(lightdm:auth): Not a user managed by systemd-homed: No home for user damnick known
Oct 24 12:18:07 nick-archzephG14 lightdm[3275]: pam_unix(lightdm-greeter:session): session closed for user lightdm

I managed to access x logging in in a terminal and executing

xinit /usr/bin/mate-session

But every time that mate ask me for a password (for example if the screen lock) it fails and I cannot login anymore.
Any help???

Thanks
Nick

2

Just to add I just installed the system fresh no mods

If I try to execute a sudo command inside an mate terminal same result I cannot login.
Outside of X (from the main terminal ctrl alt f3) everything works I can login do sudo etc etc

3

No home for user damnick known

is it true?

ls /home/damnick is valid?

1 Like
4

Yes I have my home and there are files there

ls -lha $HOME
total 88K
drwx------ 15 damnick damnick 4.0K Oct 24 12:19 .
drwxr-xr-x 3 root root 4.0K Oct 24 11:08 …
-rw------- 1 damnick damnick 1.3K Oct 24 11:45 .bash_history
-rw-r–r-- 1 damnick damnick 21 Aug 9 17:27 .bash_logout
-rw-r–r-- 1 damnick damnick 57 Oct 24 11:08 .bash_profile
-rw-r–r-- 1 damnick damnick 4.5K Oct 24 11:08 .bashrc
drwx------ 8 damnick damnick 4.0K Oct 24 12:19 .cache
drwx------ 10 damnick damnick 4.0K Oct 24 12:38 .config
drwxr-xr-x 2 damnick damnick 4.0K Oct 24 11:11 Desktop
drwxr-xr-x 2 damnick damnick 4.0K Oct 24 11:11 Documents
drwxr-xr-x 2 damnick damnick 4.0K Oct 24 11:11 Downloads
drwx------ 2 damnick damnick 4.0K Oct 24 12:35 .gnupg
drwxr-xr-x 3 damnick damnick 4.0K Oct 24 11:46 .local
drwx------ 5 damnick damnick 4.0K Oct 24 12:19 .mozilla
drwxr-xr-x 2 damnick damnick 4.0K Oct 24 11:11 Music
drwxr-xr-x 2 damnick damnick 4.0K Oct 24 11:11 Pictures
drwxr-xr-x 2 damnick damnick 4.0K Oct 24 11:11 Public
drwxr-xr-x 2 damnick damnick 4.0K Oct 24 11:11 Templates
drwxr-xr-x 2 damnick damnick 4.0K Oct 24 11:11 Videos
-rw------- 1 damnick damnick 1.4K Oct 24 11:22 .viminfo
-rw-r–r-- 1 damnick damnick 215 Oct 24 11:46 .wget-hsts
-rw------- 1 damnick damnick 0 Oct 24 12:16 .Xauthority

5

If I try to run sudo I got this in journalctl

[> damnick@nick-archzephG14 ~]$ journalctl -f

– Logs begin at Sat 2020-10-24 11:10:45 IST. –
Oct 24 12:50:04 nick-archzephG14 sudo[7131]: pam_unix(sudo:session): session opened for user root(uid=0) by damnick(uid=0)
Oct 24 12:50:07 nick-archzephG14 systemd[1]: Started Getty on tty4.
Oct 24 12:50:07 nick-archzephG14 kernel: audit: type=1130 audit(1603540207.797:195): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=getty@tty4 comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Oct 24 12:50:07 nick-archzephG14 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=getty@tty4 comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Oct 24 12:50:13 nick-archzephG14 sudo[7131]: pam_unix(sudo:session): session closed for user root
Oct 24 12:50:13 nick-archzephG14 audit[7131]: USER_END pid=7131 uid=0 auid=1000 ses=4 msg=‘op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct=“root” exe=“/usr/bin/sudo” hostname=nick-archzephG14 addr=? terminal=/dev/tty2 res=success’
Oct 24 12:50:13 nick-archzephG14 audit[7131]: CRED_DISP pid=7131 uid=0 auid=1000 ses=4 msg=‘op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct=“root” exe=“/usr/bin/sudo” hostname=nick-archzephG14 addr=? terminal=/dev/tty2 res=success’
Oct 24 12:50:13 nick-archzephG14 kernel: [drm] Failed to add display topology, DTM TA is not initialized.
Oct 24 12:50:13 nick-archzephG14 kernel: audit: type=1106 audit(1603540213.670:196): pid=7131 uid=0 auid=1000 ses=4 msg=‘op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct=“root” exe=“/usr/bin/sudo” hostname=nick-archzephG14 addr=? terminal=/dev/tty2 res=success’
Oct 24 12:50:13 nick-archzephG14 kernel: audit: type=1104 audit(1603540213.670:197): pid=7131 uid=0 auid=1000 ses=4 msg=‘op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct=“root” exe=“/usr/bin/sudo” hostname=nick-archzephG14 addr=? terminal=/dev/tty2 res=success’
Oct 24 12:52:08 nick-archzephG14 sudo[7248]: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=0 tty=/dev/pts/3 ruser=damnick rhost= user=damnick
Oct 24 12:52:08 nick-archzephG14 sudo[7248]: pam_systemd_home(sudo:auth): Not a user managed by systemd-homed: No home for user damnick known
Oct 24 12:52:08 nick-archzephG14 audit[7248]: USER_AUTH pid=7248 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=? acct=“damnick” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/3 res=failed’
Oct 24 12:52:08 nick-archzephG14 kernel: audit: type=1100 audit(1603540328.218:198): pid=7248 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=? acct=“damnick” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/3 res=failed’
Oct 24 12:52:12 nick-archzephG14 audit[7248]: USER_AUTH pid=7248 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=? acct=“damnick” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/3 res=failed’
Oct 24 12:52:12 nick-archzephG14 kernel: audit: type=1100 audit(1603540332.641:199): pid=7248 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=? acct=“damnick” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/3 res=failed’
Oct 24 12:52:21 nick-archzephG14 kernel: audit: type=1100 audit(1603540341.015:200): pid=7248 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=? acct=“damnick” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/3 res=failed’
Oct 24 12:52:21 nick-archzephG14 audit[7248]: USER_AUTH pid=7248 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=? acct=“damnick” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/3 res=failed’
Oct 24 12:52:22 nick-archzephG14 sudo[7248]: damnick : 3 incorrect password attempts ; TTY=pts/3 ; PWD=/home/damnick ; USER=root ; COMMAND=/bin/bash

6

In particular

kernel: audit: type=1106 audit(1603540213.670:196): pid=7131 uid=0 auid=1000 ses=4 msg=‘op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct=“root” exe="/usr/bin/sudo" hostname=nick-archzephG14 addr=? terminal=/dev/tty2 res=success’

kernel: audit: type=1104 audit(1603540213.670:197): pid=7131 uid=0 auid=1000 ses=4 msg=‘op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct=“root” exe="/usr/bin/sudo" hostname=nick-archzephG14 addr=? terminal=/dev/tty2 res=success’

sudo[7248]: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=0 tty=/dev/pts/3 ruser=damnick rhost= user=damnick
sudo[7248]: pam_systemd_home(sudo:auth): Not a user managed by systemd-homed: No home for user damnick known
audit[7248]: USER_AUTH pid=7248 uid=1000 auid=1000 ses=2 msg='op=PAM:authentication grantors=? acct=“damnick” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=failed’

I’m on kernel 5.9.1-arch1-1

7

Your title refers to cannot login in sddm.
The errors listed in the OP keep referring to lightdm.

Which Desktop Manager are you actually trying to use?

Pudge

8

Is the same I tried sddm and lighdm same error.
I think the problem is in pam configuration

9

may try create a new user, if you want to keep that username first remove the old user and then recreate.

10 
userdel damnick
mv /home/damnick /home/old
useradd -m -G wheel -s /bin/bash damnick
passwd damnick
11

Ok
I did some test and apparently if I use a ‘#’ in the password field I can login from the termina but not from x sessions

I changed the password to contain only letter/numbers and it works now

12

If your trying to log in with sddm disable lightdm, eg:

sudo systemctl disable lightdm

or vise versa

sudo systemctl disable sddm

Having both enabled will conflict with each other.

1 Like
13

Thanks antechdesigns I already did that -> but stil the password with # doesn’t work…
I changed it for now

14

should not be that, but if it is working it is good to go :wink:
But can be kind of an issue with keymap settings

1 Like
15

must be an issue with keyboard layout… or something related… I just test this I can use # inside passwords and any other signs

16

Speaking about keyboard layout problems…
In July, using the July release of EOS, I had to install the OS again in one of my laptops, I remember everything looking fine after the install, until another user had to use his password to update the system using the terminal (konsole), he wasn’t able to make his password work, but using the password to unlock KDE plasma, and sddm, he had no trouble at all. After a while I thought that most likely the problem would be found in the keyboard layout configurations and voilà!, after checking all the layout configuration files I was able to find (which I think were two or three) that the layout configurations were a mess, none had the configuration I thought I had selected while installing, yet, my personal passwords worked, the password to un-encrypt the system worked too, so once I found the problem I had to reconfigure every single layout configuration and once I did that there were no more problems. I didn’t report the problem because I considered the possibility that maybe I had actually made a foolish mistake during the installation but, because a few days later, someone turned off the laptop while updating the kernel (not me), I decided to reinstall EOS again, instead of repairing the system, and once I reinstalled again, making sure I chose the right layout before installing because I was still suspecting the problem was with the July release, and once reinstalled, there was no way to access the system because apparently the keyboard layout for GRUB wasn’t the one I had chosen for the encrypted system, I didn’t make sure that was the problem trying a different keyboard layout (I think it can be changed in the “console-like” screen to insert your password in GRUB) because I decided to try the May release and see if there was any problems with the layouts, and, after using that release to reinstall, there were no problems at all, all the layouts were as they were supposed to be, yet, once I discovered that, I decided not to report the issue, because I looked if someone else have had that same problem and there was no one saying they have had such problem (or at least I didn’t find any posts related to the issue), so I thought that maybe I was the only one with that problem and didn’t report anything, but apparently the problem is there and it is still in the September release.
At this point I don’t think I can help by reporting the issue, as my systems are working just fine, but I guess letting you know that that happen may help in some way. The laptop that had that issue was an Asus X551M.
If you want me to report this, I can do it…

17

this is a known BUG for a very long time, it is not possible to set another then default keymap for that early state of boot where you unlock grub on encrypted partition.
you can only avoid this by using unencrypted /boot partition