https://bugs.kde.org/show_bug.cgi?id=511297
dinghy <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DOWNSTREAM |--- --- Comment #6 from dinghy <[email protected]> --- My last comment was wrong, since this issue is still present in Plasma-Login-Manager! I just did a `journalctrl --since -2min` and got those relevant logs: Mär 09 00:11:35 USER ModemManager[2223]: <msg> [ttyS1/probe] probe step: AT close port Mär 09 00:11:35 USER ModemManager[2223]: <msg> [ttyS1/probe] probe step: done Mär 09 00:11:35 USER ModemManager[2223]: <msg> [ttyS1/probe] probe step: start Mär 09 00:11:35 USER ModemManager[2223]: <msg> [ttyS1/probe] probe step: QCDM Mär 09 00:11:35 USER ModemManager[2223]: <msg> [ttyS1/probe] probe step: done Mär 09 00:11:35 USER ModemManager[2223]: <msg> [device /sys/devices/pci0000:00/0000:00:16.3] creating modem with plugin 'generic' and '1' ports (17aa:8086:9d3d) Mär 09 00:11:35 USER ModemManager[2223]: <wrn> [plugin/generic] could not grab port ttyS1: Cannot add port 'tty/ttyS1', unhandled port type Mär 09 00:11:35 USER ModemManager[2223]: <wrn> [modem8] teardown not called before dispose Mär 09 00:11:35 USER ModemManager[2223]: <wrn> [base-manager] couldn't create modem for device '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port Mär 09 00:11:35 USER ModemManager[2223]: <msg> [cdc-wdm0/mbim] Skipping QMI support check in MBIM device Mär 09 00:11:35 USER ModemManager[2223]: <msg> [cdc-wdm0/probe] probe step: done Mär 09 00:11:35 USER ModemManager[2223]: <msg> [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-6] creating modem with plugin 'sierra' and '2' ports (1199:9079) Mär 09 00:11:35 USER ModemManager[2223]: <msg> [base-manager] modem for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6' successfully created Mär 09 00:11:35 USER ModemManager[2223]: <msg> [base-manager] running setup for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6'... Mär 09 00:11:35 USER unix_chkpwd[15698]: password check failed for user (USER) Mär 09 00:11:35 USER kscreenlocker_greet[14675]: pam_unix(kde:auth): authentication failure; logname=USER uid=1000 euid=1000 tty= ruser= rhost= user=USER Mär 09 00:11:35 USER kscreenlocker_greet[14675]: pam_kwallet5(kde:auth): pam_kwallet5: pam_sm_authenticate Mär 09 00:11:35 USER unix_chkpwd[15700]: password check failed for user (USER) Mär 09 00:11:35 USER ModemManager[2223]: <msg> [modem9/cdc-wdm0/mbim] MBIM device is QMI capable Mär 09 00:11:38 USER chromium[2733]: [2733:2763:0309/001138.301308:ERROR:google_apis/gcm/engine/connection_factory_impl.cc:434] Failed to connect to MCS endpoint with error -7 Mär 09 00:11:39 USER kscreenlocker_greet[14675]: pam_warn(kde-smartcard:auth): function=[pam_sm_authenticate] flags=0 service=[kde-smartcard] terminal=[<unknown>] user=[USER] ruser=[<unknown>] rhost=[<unknown>] Mär 09 00:11:39 USER kscreenlocker_greet[14675]: pam_warn(kde-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[kde-fingerprint] terminal=[<unknown>] user=[USER] ruser=[<unknown>] rhost=[<unknown>] Mär 09 00:11:41 USER systemd-timesyncd[809]: Contacted time server 185.252.140.126:123 (1.nixos.pool.ntp.org). Mär 09 00:11:49 USER wireplumber[2187]: wp-event-dispatcher: <WpAsyncEventHook:0x55e316501120> failed: <WpSiStandardLink:0x55e316840fd0> link failed: some node was destroyed before the link was created Mär 09 00:11:51 USER ModemManager[2223]: <msg> [modem9] state changed (unknown -> locked) Mär 09 00:11:51 USER ModemManager[2223]: <wrn> [modem9] modem couldn't be initialized: Couldn't check unlock status: SIM not inserted Mär 09 00:11:51 USER ModemManager[2223]: <msg> [modem9] state changed (locked -> failed) Mär 09 00:11:52 USER ModemManager[2223]: <wrn> [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-6] error initializing: Modem in failed state: sim-missing I think it tries to first check with a password and not via u2f as it says: Mär 09 00:11:35 USER unix_chkpwd[15698]: password check failed for user (USER) That would be my guess, but I don't know exactly... -- You are receiving this mail because: You are watching all bug changes.
