Plasma does not start after SDDM

Northsoft · 2023-05-07 11:45:37

Hello world. After an update and attempt to install libimobiledevice-1.3.0-8 and usbmuxd-1.1.1-3, I'm stuck on the SDDM screen. I.e. I type a password, it waits a second, and resets my password field without any message.
Also I'm unable to use network (my USB WLAN adapter has forgot to update its driver, https://bbs.archlinux.org/viewtopic.php?pid=2098389), now I have to boot to W$ in order to post smth at BBS.
What can I do with only W$ connected to WLAN?
Upd: Dmesg https://pastebin.com/fGgvgagm, Jctl https://pastebin.com/mqaUUi1u

Last edited by Northsoft (2023-05-07 12:00:24)

ewaller · 2023-05-07 15:15:26

To log in, you can change to a different console using Ctrl-Alt-F2 (or F3 through [I think] F6). You can log in from the console and try to fix things. If you need a network and your only option is WLAN, you can USB tether a phone in network sharing mode. It will show up as a *wired* LAN in Linux. Just connect by running dhcpcd. Fix your network, then diagnose the issue.

Just a hunch, ensure that uname -a and pacman -Q linux report the same revision number.

Last edited by ewaller (2023-05-07 15:15:51)

Northsoft · 2023-05-07 15:22:55

ewaller wrote:

you can USB tether a phone in network sharing mode. It will show up as a *wired* LAN in Linux. Just connect by running dhcpcd. Fix your network, then diagnose the issue.

Is it possible to do it without USB tethering? It was an obvious way, but my phone is in repair

seth · 2023-05-07 15:50:45

You can redirect the outputs into files on some nonvolatile storage (usb key) and upload those from windows or anything else.
The proper command is "sudo journalctl -b" - never use "-x" ever. It's spam.

Likewise you can fetch the driver package/sources using windows and access them from the usb key.
However, what driver do you use? You seem to have a rtl8812au chip, don't you use some dkms package?

Northsoft · 2023-05-07 17:12:28

seth wrote:

The proper command is "sudo journalctl -b"

https://pastebin.com/UQhhtfNg

seth wrote:

Likewise you can fetch the driver package/sources using windows and access them from the usb key.

Looks like I'll use VirtualBox and try to find out some way to prepare AUR package to install. I hope I will not have to create a custom ISO just because of not updated package >_<

seth wrote:

However, what driver do you use? You seem to have a rtl8812au chip, don't you use some dkms package?

I use rtl88xxau-aircrack-dkms-git (AUR), and in W$ the device shows as "Realtek RTL8811AU Wireless LAN 802.11ac USB 2.0" (VID 0BDA & PID A811).

seth · 2023-05-07 19:15:56

I use rtl88xxau-aircrack-dkms-git (AUR)

Then did the dkms rebuild fail?

мая 07 18:43:49 localpc systemd[1]: Started Session 2 of User admin.
мая 07 18:43:49 localpc systemd[743]: Starting Update XDG user dir configuration...
мая 07 18:43:49 localpc systemd[743]: Finished Update XDG user dir configuration.
мая 07 18:43:49 localpc systemd[743]: Reached target Main User Target.
мая 07 18:43:49 localpc systemd[743]: Startup finished in 119ms.
мая 07 18:43:49 localpc systemd[743]: Created slice User Core Session Slice.
мая 07 18:43:49 localpc systemd[743]: Starting D-Bus User Message Bus...
мая 07 18:43:49 localpc systemd[743]: Started D-Bus User Message Bus.
мая 07 18:43:49 localpc secretserviced[751]: time="Sun, 07 May 2023 18:43:49 +0200" level=info msg="===== Secret Service Started ====="
мая 07 18:43:49 localpc secretserviced[751]: time="Sun, 07 May 2023 18:43:49 +0200" level=info msg="Secret service dbus address: /org/freedesktop/secrets"
мая 07 18:43:49 localpc sddm-helper[764]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
мая 07 18:43:49 localpc sddm-helper[741]: Starting: "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
мая 07 18:43:49 localpc sddm-helper[766]: Adding cookie to "/home/admin/.Xauthority"
мая 07 18:43:49 localpc sddm[524]: Session started
мая 07 18:43:49 localpc sddm-helper[741]: [PAM] Closing session
мая 07 18:43:49 localpc sddm-helper[741]: pam_unix(sddm:session): session closed for user admin
мая 07 18:43:49 localpc sddm-helper[741]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
мая 07 18:43:49 localpc sddm-helper[741]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
мая 07 18:43:49 localpc sddm-helper[741]: [PAM] Ended.
мая 07 18:43:49 localpc sddm[524]: Auth: sddm-helper exited with 127
мая 07 18:43:49 localpc sddm[524]: Socket server stopping...
мая 07 18:43:49 localpc sddm[524]: Socket server stopped.
мая 07 18:43:49 localpc sddm[524]: Display server stopping...
мая 07 18:43:49 localpc systemd-logind[420]: Session 2 logged out. Waiting for processes to exit.

I'd take a look at secretserviced and pam_kwallet5, can you log into eg. an openbox session?

Northsoft · 2023-05-07 19:59:15

seth wrote:

Then did the dkms rebuild fail?

Maybe I had to use yay -Syu --devel instead of yay -Syu

seth wrote:

I'd take a look at secretserviced and pam_kwallet5, can you log into eg. an openbox session?

Maybe later, when I reinstall a WLAN driver (in some way).

seth · 2023-05-07 20:02:35

You can also just try to disable pam_kwallet5.so, https://wiki.archlinux.org/title/KDE_Wa … figure_PAM
(Commenting the lines will do. Make sure you've a root shell open when messing w/ PAM and try at least a console login before you think about closing the root shell)

Northsoft · 2023-05-07 21:32:36

I have installed a network driver, so at least now I see a network interface appearing at ip link command output. Maybe tomorrow I'll try to find out, how can I connect to WLAN using only cli.

seth wrote:

You can also just try to disable pam_kwallet5.so

That didn't help, SDDM still shows a blank black screen, and after half a second it throws me back to password prompt.

Jctl: https://pastebin.com/9G3LzTv1

seth · 2023-05-07 21:39:15

Now that the wifi works, install openbox, open a terminal (xterm, konsole - if you can) and run "/usr/bin/startplasma-x11" and check the output.
Neither ksmserver nor plasmashell nor kwin_x11 are being run and teh session simply terminates immediately after the login.

Northsoft · 2023-05-08 17:07:11

seth wrote:

Now that the wifi works, install openbox, open a terminal (xterm, konsole - if you can) and run "/usr/bin/startplasma-x11" and check the output.
Neither ksmserver nor plasmashell nor kwin_x11 are being run and teh session simply terminates immediately after the login.

Things get much more interesting. I've started a WLAN connection via nmcli, and if kwallet_pam is not commented out at /etc/pam.d/sddm, after Plasma is launched, NetworkManager tries to start a connection, and… makes the kernel to say “Oops” (https://pastebin.com/uKVYxqKx), so I'm unable to sudo/reboot/lots of other things. At the moment things go better, i.e. when kwallet_pam is commented out, I only have to type a password to open KDE Wallet. But it is interesting, is there any option to make kwallet_pam alive again.

seth · 2023-05-08 19:34:44

Did you add pam_kwallet to other pam configurations than sddm?

grep -r kwall /etc/pam.d

You do not get the Oops'es w/o pam_kwallet, even when connecting on the NIC??
Does the https://aur.archlinux.org/packages/rtl8812au-dkms-git module work?

Northsoft · 2023-05-08 20:24:04

seth wrote:

Did you add pam_kwallet to other pam configurations than sddm?
grep -r kwall /etc/pam.d

It appeared also in /etc/pam.d/sddm-autologin, no idea how should I handle it properly

seth wrote:

You do not get the Oops'es w/o pam_kwallet, even when connecting on the NIC??
Does the https://aur.archlinux.org/packages/rtl8812au-dkms-git module work?

Yes, the kernel does not say Oops even after network is connected, looks like the trouble is in kwallet_pam
https://imgur.com/a/ueKJz1l

[admin@localpc ~]$ ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=60 time=46.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=60 time=43.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=40.0 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=60 time=49.0 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 40.010/44.849/49.003/3.340 ms
[admin@localpc ~]$ sudo journalctl -b | grep -i oops
мая 08 17:53:03 archlinux kernel: tsc: PIT calibration matches HPET. 1 loops
[admin@localpc ~]$ uname -a
Linux localpc 6.3.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 01 May 2023 17:42:39 +0000 x86_64 GNU/Linux
[admin@localpc ~]$ sudo bash
[root@localpc admin]# grep -r kwall /etc/pam.d
/etc/pam.d/sddm:#-auth   optional  pam_kwallet5.so
/etc/pam.d/sddm:#-session  optional  pam_kwallet5.so auto_start
/etc/pam.d/sddm-autologin:-auth       optional    pam_kwallet5.so
/etc/pam.d/sddm-autologin:-session    optional    pam_kwallet5.so auto_start
[root@localpc admin]#

seth · 2023-05-08 20:59:54

Race condition?
What if you re-enable pam_kwallet but disable the wifi connection (for autoconnect, at least) and then connect the wifi manually after the login?

Arch Linux

#1 2023-05-07 11:45:37

Plasma does not start after SDDM

#2 2023-05-07 15:15:26

Re: Plasma does not start after SDDM

#3 2023-05-07 15:22:55

Re: Plasma does not start after SDDM

#4 2023-05-07 15:50:45

Re: Plasma does not start after SDDM

#5 2023-05-07 17:12:28

Re: Plasma does not start after SDDM

#6 2023-05-07 19:15:56

Re: Plasma does not start after SDDM

#7 2023-05-07 19:59:15

Re: Plasma does not start after SDDM

#8 2023-05-07 20:02:35

Re: Plasma does not start after SDDM

#9 2023-05-07 21:32:36

Re: Plasma does not start after SDDM

#10 2023-05-07 21:39:15

Re: Plasma does not start after SDDM

#11 2023-05-08 17:07:11

Re: Plasma does not start after SDDM

#12 2023-05-08 19:34:44

Re: Plasma does not start after SDDM

#13 2023-05-08 20:24:04

Re: Plasma does not start after SDDM

#14 2023-05-08 20:59:54

Re: Plasma does not start after SDDM

Board footer