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

Hello everyone,

I updated today and now can’t log in. Per another suggestion, I followed the instructions in stable-update-2020-08-28 post . However, when I try to boot with the kernel option “systemd.unit=rescue.target” I get the following message:

“You are in rescue mode. After logging in…”
“Cannot open access to console, the root account is locked. See sulogin(8) man page for more details.”

After I press enter to continue, the system brings me back to the log in screen, where I cannot log in with my usual password. I am completely lost on this one. Does anyone know what is going on or where to go from here to fix this?

Thanks for any help you can provide.

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 )

Stephane,

Please see the output from this code here: https ://bpa. st/CYGA .

I had to put a couple spaces in the pastebin location because I am not allowed to post urls.

there is 2 type errors
this one

Aug 28 10:26:26 my-pc sddm-greeter[790]: QObject: Cannot create children for a parent that is in a different thread.
                                               (Parent is QGuiApplication(0x7ffd2a711690), parent's thread is QThread(0x560c18690e50), current thread is QThread(0x560c18776670)`
Aug 28 10:26:26 my-pc sddm-greeter[790]: QObject: Cannot create children for a parent that is in a different thread.
                                               (Parent is QGuiApplication(0x7ffd2a711690), parent's thread is QThread(0x560c18690e50), current thread is QThread(0x560c18776670)
Aug 28 10:26:26 my-pc sddm-greeter[790]: QObject: Cannot create children for a parent that is in a different thread.
                                               (Parent is QGuiApplication(0x7ffd2a711690), parent's thread is QThread(0x560c18690e50), current thread is QThread(0x560c18776670)

and the last this one

Aug 28 10:26:34 my-pc sddm[610]: Error from greeter session: "Process crashed"
Aug 28 10:26:34 my-pc sddm[610]: Auth: sddm-helper crashed (exit code 15)
Aug 28 10:26:34 my-pc sddm[610]: Error from greeter session: "Process crashed"
Aug 28 10:26:34 my-pc sddm[610]: Auth: sddm-helper exited with 15
Aug 28 10:26:34 my-pc sddm[610]: Signal received: SIGTERM

can you return this

grep -E "pam_tally|pam_cracklib" /etc/pam.d/*

@philm can you have a look at this ?

The output from this command gives me:

“[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”

ok it come from sddm then

sudo systemctl status sddm-greeter.service
sudo systemctl status sddm.service

I am not able to provide the output of this code while chrooted and in the liveusb it is not recognized. Is this a matter of just reinstalling sddm from the liveusb then?

we dont have all in journal log
just try to boot TTY , and check what is wrong

may be write to a file fisrt step

sudo systemctl status sddm-greeter.service > error-greeter-service.txt
sudo systemctl status sddm.service > error-sddm-service.txt

then get with USB iso choot on disk

I don’t think sddm is the reason.

@Jkh4q I have totally the same issue and no luck to solve it yet.

same error no login at all ?

yes, getting login incorrect, grep tally|cracklib returning no result

even by chroot from USB iso manjaro ?
can you recheck ?

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