[Stable 28-08-2020] Issues with logging in - KDE - sddm

I see this a little earlier:

PAM adding faulty module: /usr/lib/security/pam_tally2.so

can you boot on USB iso manjaro
open a terminal and a browser on this topic
and returns

sudo manjaro-chroot -a ( type 1 if only one line - 0 appears )
grep -E "pam_tally|pam_cracklib" /etc/pam.d/*
journalctl -b -1 -p4
exit ( quit chroot )
$ grep -E "pam_tally|pam_cracklib" /etc/pam.d/*
/etc/pam.d/passwd:#password     required        pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
/etc/pam.d/system-login:auth       required   pam_tally2.so        deny=3 unlock_time=600 onerr=succeed file=/var/log/tallylog
/etc/pam.d/system-login:account    required   pam_tally2.so
Aug 28 18:07:35 Computer sddm[959]: Auth: sddm-helper exited with 1
Aug 28 18:07:35 Computer sddm-helper[1379]: [PAM] Ended.
Aug 28 18:07:35 Computer sddm-greeter[995]: Message received from daemon: LoginFailed
Aug 28 18:07:35 Computer sddm[959]: Authentication error: "Module is unknown"
Aug 28 18:07:35 Computer sddm-helper[1379]: [PAM] returning.
Aug 28 18:07:35 Computer sddm-helper[1379]: [PAM] authenticate: Module is unknown
Aug 28 18:07:33 Computer kernel: audit: type=1100 audit(1598630853.322:69): pid=1379 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="franz" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=failed'
Aug 28 18:07:33 Computer sddm-helper[1379]: gkr-pam: stashed password to try later in open session
Aug 28 18:07:33 Computer audit[1379]: USER_AUTH pid=1379 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="franz" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=failed'
Aug 28 18:07:33 Computer sddm-helper[1379]: gkr-pam: unable to locate daemon control file
Aug 28 18:07:33 Computer sddm-helper[1379]: [PAM] Conversation with 1 messages
Aug 28 18:07:33 Computer sddm-helper[1379]: [PAM] Preparing to converse...
Aug 28 18:07:33 Computer sddm-helper[1379]: [PAM] Authenticating...
Aug 28 18:07:33 Computer sddm-helper[1379]: [PAM] Starting...
Aug 28 18:07:33 Computer sddm-helper[1379]: PAM adding faulty module: /usr/lib/security/pam_tally2.so
Aug 28 18:07:33 Computer sddm-helper[1379]: PAM unable to dlopen(/usr/lib/security/pam_tally2.so): /usr/lib/security/pam_tally2.so: cannot open shared object file: No such file or directory

Here is my:

[manjaro /]# grep -E "pam_tally|pam_cracklib" /etc/pam.d/*
/etc/pam.d/passwd:#password     required        pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
/etc/pam.d/system-login.back:auth       required   pam_tally2.so        onerr=succeed file=/var/log/tallylog
/etc/pam.d/system-login.back:auth required pam_tally2.so deny=3 unlock_time=60 onerr=succeed file=/var/log/tallylog
/etc/pam.d/system-login.back:account    required   pam_tally2.so 

And logs

-- Logs begin at Thu 2020-07-30 20:28:29 EEST, end at Fri 2020-08-28 19:24:44 EEST. --
Aug 28 17:32:01 home-laptop kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Aug 28 17:32:01 home-laptop kernel:  #5 #6 #7
Aug 28 17:32:01 home-laptop kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Aug 28 17:32:01 home-laptop kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Aug 28 17:32:01 home-laptop kernel: usb: port power management may be unreliable
Aug 28 17:32:02 home-laptop kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Aug 28 17:32:02 home-laptop kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Aug 28 17:32:02 home-laptop kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Aug 28 17:32:02 home-laptop kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Aug 28 17:32:02 home-laptop kernel: ucsi_acpi USBC000:00: Failed to reset PPM! Trying again..
Aug 28 17:32:02 home-laptop kernel: i2c_hid i2c-ELAN2301:00: i2c-ELAN2301:00 supply vdd not found, using dummy regulator
Aug 28 17:32:02 home-laptop kernel: i2c_hid i2c-ELAN2301:00: i2c-ELAN2301:00 supply vddl not found, using dummy regulator
Aug 28 17:32:02 home-laptop kernel: ucsi_acpi USBC000:00: Failed to reset PPM! Trying again..
Aug 28 17:32:02 home-laptop systemd-udevd[286]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
Aug 28 17:32:02 home-laptop kernel: [Firmware Bug]: ACPI(PXSX) defines _DOD but not _DOS
Aug 28 17:32:02 home-laptop kernel: urandom_read: 6 callbacks suppressed
Aug 28 17:32:02 home-laptop kernel: thermal thermal_zone3: failed to read out thermal zone (-61)
Aug 28 17:32:02 home-laptop systemd-udevd[280]: could not read from '/sys/module/pcc_cpufreq/initstate': No such device
Aug 28 17:32:03 home-laptop systemd-udevd[272]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
Aug 28 17:32:03 home-laptop kernel: bbswitch: loading out-of-tree module taints kernel.
Aug 28 17:32:03 home-laptop kernel: ACPI Warning: \_SB.PCI0.RP01.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20190816/nsarguments-59)
Aug 28 17:32:03 home-laptop kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized!
Aug 28 17:32:03 home-laptop kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 3 was not initialized!
Aug 28 17:32:03 home-laptop kernel: uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized!
Aug 28 17:32:03 home-laptop kernel: uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized!
Aug 28 17:32:04 home-laptop kernel: iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
Aug 28 17:32:04 home-laptop kernel: sd 2:0:0:0: [sda] No Caching mode page found
Aug 28 17:32:04 home-laptop kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 28 17:32:04 home-laptop kernel: iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
Aug 28 17:32:04 home-laptop NetworkManager[723]: <warn>  [1598625124.7435] sup-iface[79a783852699da90,0,wlp2s0]: call-p2p-cancel: failed with P2P cancel failed
Aug 28 17:32:04 home-laptop kernel: kauditd_printk_skb: 22 callbacks suppressed
Aug 28 17:32:05 home-laptop sddm-greeter[785]: QObject: Cannot create children for a parent that is in a different thread.
                                           (Parent is QGuiApplication(0x7ffcdb7c8e20), parent's thread is QThread(0x55f88f6f8d90), current thread is QThread(0x55f88f82d9f0)
Aug 28 17:32:05 home-laptop sddm-greeter[785]: QObject: Cannot create children for a parent that is in a different thread.
                                           (Parent is QGuiApplication(0x7ffcdb7c8e20), parent's thread is QThread(0x55f88f6f8d90), current thread is QThread(0x55f88f82d9f0)
Aug 28 17:32:05 home-laptop sddm-greeter[785]: QObject: Cannot create children for a parent that is in a different thread.
                                           (Parent is QGuiApplication(0x7ffcdb7c8e20), parent's thread is QThread(0x55f88f6f8d90), current thread is QThread(0x55f88f82d9f0)
Aug 28 17:32:05 home-laptop sddm-greeter[785]: QObject: Cannot create children for a parent that is in a different thread.
                                           (Parent is QGuiApplication(0x7ffcdb7c8e20), parent's thread is QThread(0x55f88f6f8d90), current thread is QThread(0x55f88f82d9f0)
Aug 28 17:32:05 home-laptop sddm-greeter[785]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: file:///usr/share/sddm/themes/breath/Main.qml:408:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 28 17:32:07 home-laptop sddm-greeter[785]: <input>:406:376: Could not add child element to parent element because the types are incorrect.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: <input>:407:126: Could not add child element to parent element because the types are incorrect.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: <input>:408:126: Could not add child element to parent element because the types are incorrect.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: <input>:408:385: Could not add child element to parent element because the types are incorrect.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: <input>:409:125: Could not add child element to parent element because the types are incorrect.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: <input>:410:124: Could not add child element to parent element because the types are incorrect.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: <input>:411:125: Could not add child element to parent element because the types are incorrect.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: <input>:411:371: Could not add child element to parent element because the types are incorrect.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: <input>:411:619: Could not add child element to parent element because the types are incorrect.
Aug 28 17:32:07 home-laptop sddm-greeter[785]: file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 28 17:32:07 home-laptop sddm-greeter[785]: file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 28 17:32:07 home-laptop sddm-greeter[785]: file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 28 17:32:07 home-laptop sddm-greeter[785]: file:///usr/share/sddm/themes/breath/components/VirtualKeyboard.qml:22:1: Type InputPanel unavailable
Aug 28 17:32:07 home-laptop sddm-greeter[785]: qrc:/QtQuick/VirtualKeyboard/content/InputPanel.qml:127:5: Type Keyboard unavailable
Aug 28 17:32:07 home-laptop sddm-greeter[785]: qrc:/QtQuick/VirtualKeyboard/content/components/Keyboard.qml:38:1: module "QtQuick.VirtualKeyboard.Plugins" is not installed
Aug 28 17:32:07 home-laptop sddm-greeter[785]: file:///usr/share/sddm/themes/breath/Login.qml:84:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 28 17:32:07 home-laptop sddm-greeter[785]: file:///usr/lib/qt/qml/org/kde/plasma/components/Button.qml:52: ReferenceError: PlasmaCore is not defined
Aug 28 17:32:08 home-laptop sddm-greeter[785]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.18'
Aug 28 17:32:10 home-laptop kernel: kauditd_printk_skb: 5 callbacks suppressed
Aug 28 17:32:13 home-laptop sddm-helper[1047]: [PAM] authenticate: Permission denied
Aug 28 17:32:13 home-laptop sddm[735]: Authentication error: "Permission denied"
Aug 28 17:32:13 home-laptop sddm[735]: Auth: sddm-helper exited with 1
Aug 28 17:32:16 home-laptop sddm[735]: Error from greeter session: "Process crashed"
Aug 28 17:32:16 home-laptop sddm[735]: Auth: sddm-helper crashed (exit code 15)
Aug 28 17:32:16 home-laptop sddm[735]: Error from greeter session: "Process crashed"
Aug 28 17:32:16 home-laptop sddm[735]: Auth: sddm-helper exited with 15
Aug 28 17:32:16 home-laptop sddm[735]: Signal received: SIGTERM
Aug 28 17:32:16 home-laptop kernel: kauditd_printk_skb: 35 callbacks suppressed
Aug 28 17:32:17 home-laptop bumblebeed[626]: Received Terminated signal.
Aug 28 17:32:17 home-laptop kernel: watchdog: watchdog0: watchdog did not stop!

According to pacman.log, during update was only one pacnew file

[2020-08-28T15:24:29+0300] [ALPM] warning: /etc/pam.d/system-login installed as /etc/pam.d/system-login.pacnew
[2020-08-28T15:24:29+0300] [ALPM] upgraded pambase (20190105.1-2 -> 20200721.1-2)
[2020-08-28T15:24:29+0300] [ALPM] upgraded pam (1.3.1-2 -> 1.4.0-3)

Could someone share with me good (correct) system-login file please.

This is the thing …

1 Like

You already have one: /etc/pam.d/system-login.pacnew

modify

/etc/pam.d/system-login
auth pam_faillock.so ( before pam_tally2.so )

/etc/pam.d/system-logi:
account pam_faillock.so (before pam_tally2.so)

and add
session required pam_env.so user_readenv=1

and reboot

1 Like

Doesn’t work for me. Looks like same behavior, from sddm gives “login failed” from tty gives “login incorrect”

maybe system-auth file also needs some edit?

Actually this does work! I misspelled pam_faillock.so. Thank you very much; I’m finally back on my Desktop.

can you please share system-login, system-auth, systemd-user files

I don’t get why you ask for these.
All those files belong to packages and are available on your machine either as .pacnew-file or (if unchanged) as the actual file.

/etc/pam.d/system-login (as is from pambase package):

click
#%PAM-1.0

auth       required   pam_shells.so
auth       requisite  pam_nologin.so
auth       include    system-auth

account    required   pam_access.so
account    required   pam_nologin.so
account    include    system-auth

password   include    system-auth

session    optional   pam_loginuid.so
session    optional   pam_keyinit.so       force revoke
session    include    system-auth
session    optional   pam_motd.so          motd=/etc/motd
session    optional   pam_mail.so          dir=/var/spool/mail standard quiet
-session   optional   pam_systemd.so
session    required   pam_env.so           user_readenv=1

/etc/pam.d/system-auth (as is from pambase package):

click
#%PAM-1.0

auth       required                    pam_faillock.so      preauth
# Optionally use requisite above if you do not want to prompt for the password
# on locked accounts.
auth       [success=2 default=ignore]  pam_unix.so          try_first_pass nullok
-auth      [success=1 default=ignore]  pam_systemd_home.so
auth       [default=die]               pam_faillock.so      authfail
auth       optional                    pam_permit.so
auth       required                    pam_env.so
auth       required                    pam_faillock.so      authsucc
# If you drop the above call to pam_faillock.so the lock will be done also
# on non-consecutive authentication failures.

-account   [success=1 default=ignore]  pam_systemd_home.so
account    required                    pam_unix.so
account    optional                    pam_permit.so
account    required                    pam_time.so

-password  [success=1 default=ignore]  pam_systemd_home.so
password   required                    pam_unix.so          try_first_pass nullok shadow
password   optional                    pam_permit.so

session    required                    pam_limits.so
session    required                    pam_unix.so
session    optional                    pam_permit.so

/etc/pam.d/systemd-user (as is from systemd package):

click
# Used by systemd --user instances.

account  include system-login
session  required pam_loginuid.so
session  include system-login
1 Like

I’m asking because I’ve been trying to solve issue during last 4 hours. And there was a chance that I mixed up those files.

But the answer is no, files are the same besides pam_faillock.so section in system-login

I had the same issue. I could not login using any account (root or non-root) on XFCE or text console.

Here are all the steps I had to do (which are based on discussion in this thread):

  1. In Grub menu enter into edit mode.
  2. find line starting with “linux” and append init=/bin/bash to boot in single user root mode.
  3. open /etc/pam.d/system-login file and make sure your file matches content posted by “freggel.doe” in this thread. I had to remove 2 lines containing pam_tally2.so. Unfortunately I failed to preserve bad file.
  4. save and reboot
2 Likes

Thanks everyone for the input, but unfortunately these suggestions did not work for me. I made sure that all of the 3 files freggel.doe posted were identical in my machine, but it still claimed my password was incorrect at the login screen. I guess I am just going to reinstall the OS, as something else must be screwed up here.

Okay. I really don’t know what to tell you guys on this one.

So I decided to try a long shot and chrooted into my internal SSD from my liveusb and changed my account password and root password using “sudo passwd [Account Name]” since it was saying my password was wrong. I am in now and everything seems fine.

I dont know why both @freggel.doe and @Sergei
are simply deleting the lines … I am pretty sure (though it may depend on your system) that pam_tally2 should be replaced … not just the line removed.

For pam_tally2:

Deprecate pam_tally and pam_tally2 in favour of pam_faillock.

For pam_cracklib, if you are using it (I was not) then it should be replaced as well:

Deprecate pam_cracklib, there are two better alternatives to this
obsolete module: pam_passwdqc from passwdqc project and pam_pwquality
from libpwquality project.

1 Like

I did not delete anything - these lines never were present.
The files are exactly as delivered by the current packages.
Perhaps other installations had those lines present due to being older installations?

I also am having issues with logging back in after my system goes to sleep. I did not mean to update today, because I do not have the technical knowledge on Linux.

I am currently using Manjaro on a 2012 iMac booting off an SD card because the hard drive crashed.

I edited /etc/pam.d/system-login, which I found through the search and added the missing lines with “auth required pam_faillock.so” “auth required pam_tally2.so” was not located in my version of the file. The “user_readenv=1” was located at the end of the line for me.

After restart the issue still exists. Is there an easy way to fix this through the GUI. Can I easily downgrade without going through the command line?