I have been running Manjaro KDE on a raspberry pi 4 for a couple months, updating about once a week. I updated yesterday and after rebooting, the system is not coming all the way up. I’ll get a cursor for about a second and then it drops back to the boot text, with the last message either
finished tlp system startup/shutdown
or
started network manager script dispatcher service
ctl-alt-f2 doesn’t do anything, but ctl-alt-del does reboot it, so the system isn’t completely frozen. In fact, if I do a ctl-alt-f2 and then blindly type in root, password, and then reboot, it reboots, so its as if the screen has frozen? Thinking it might be a graphics driver issue, I commented out #vc4-fkms-v3d in config.txt, and now I can at least see the switch to tty2 and what I’m typing, but I’m new to arch, and at a loss as to what to do next.
Using a micoSD card. I tried booting raspbian from another card and it came up fine, so its not a hardware failure. I did a full-upgrade on raspbian thinking it might be a firmware issue, but that didn’t change anything on the manjaro side.
Yes I’m running plasma. Here is my “journalctl | grep sddm” output from the latest boot, with the last screen message of “started network manager script dispatcher service”:
Nov 20 13:42:55 RasPi4B sddm[382]: Signal received: SIGTERM
Nov 20 13:42:55 RasPi4B sddm[382]: Display server stopping...
Nov 20 13:42:55 RasPi4B sddm[382]: Display server stopped.
Nov 20 13:42:55 RasPi4B sddm[382]: Running display stop script "/usr/share/sddm/scripts/Xstop"
Nov 20 13:42:55 RasPi4B systemd[1]: sddm.service: Succeeded.
Nov 20 13:42:57 RasPi4B sddm[383]: Initializing...
Nov 20 13:42:57 RasPi4B sddm[383]: Starting...
Nov 20 13:42:57 RasPi4B sddm[383]: Logind interface found
Nov 20 13:42:57 RasPi4B sddm[383]: Adding new display on vt 1 ...
Nov 20 13:42:57 RasPi4B sddm[383]: Loading theme configuration from ""
Nov 20 13:42:57 RasPi4B sddm[383]: Display server starting...
Nov 20 13:42:57 RasPi4B sddm[383]: Adding cookie to "/var/run/sddm/{f01d848a-7db3-402c-8892-834c1ceb8302}"
Nov 20 13:42:57 RasPi4B sddm[383]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{f01d848a-7db3-402c-8892-834c1ceb8302} -background none -noreset -displayfd 18 -seat seat0 vt1
Nov 20 13:42:58 RasPi4B sddm[383]: Setting default cursor
Nov 20 13:42:58 RasPi4B sddm[383]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
Nov 20 13:42:58 RasPi4B sddm[383]: Display server started.
Nov 20 13:42:58 RasPi4B sddm[383]: Reading from "/usr/share/xsessions/plasma.desktop"
Nov 20 13:42:58 RasPi4B sddm[383]: Reading from "/usr/share/xsessions/plasma.desktop"
Nov 20 13:42:58 RasPi4B sddm[383]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11"
Nov 20 13:42:58 RasPi4B sddm-helper[496]: [PAM] Starting...
Nov 20 13:42:58 RasPi4B sddm-helper[496]: [PAM] Authenticating...
Nov 20 13:42:58 RasPi4B sddm-helper[496]: pam_kwallet5(sddm-autologin:auth): (null): pam_sm_authenticate
Nov 20 13:42:58 RasPi4B sddm-helper[496]: [PAM] Preparing to converse...
Nov 20 13:42:58 RasPi4B sddm-helper[496]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: Couldn't get password (it is empty)
Nov 20 13:42:58 RasPi4B sddm-helper[496]: [PAM] Conversation with 1 messages
Nov 20 13:42:59 RasPi4B sddm-helper[496]: [PAM] returning.
Nov 20 13:42:59 RasPi4B dbus-daemon[363]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.11' (uid=0 pid=496 comm="/usr/lib/sddm/sddm-helper --socket /tmp/sddm-authf")
Nov 20 13:42:59 RasPi4B sddm-helper[496]: pam_systemd_home(sddm-autologin:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Nov 20 13:42:59 RasPi4B sddm[383]: Authenticated successfully
Nov 20 13:42:59 RasPi4B sddm-helper[496]: pam_kwallet5(sddm-autologin:setcred): pam_kwallet5: pam_sm_setcred
Nov 20 13:42:59 RasPi4B sddm-helper[496]: pam_unix(sddm-autologin:session): session opened for user gbai(uid=1000) by (uid=0)
Nov 20 13:42:59 RasPi4B sddm-helper[496]: [PAM] Preparing to converse...
Nov 20 13:42:59 RasPi4B sddm-helper[496]: [PAM] Conversation with 1 messages
Nov 20 13:42:59 RasPi4B sddm[383]: Authentication information: "Welcome to Manjaro-ARM\n~~Website: https://manjaro.org\n~~Forum: https://forum.manjaro.org/c/arm\n~~Matrix: #manjaro-arm-public:matrix.org"
Nov 20 13:42:59 RasPi4B sddm-helper[496]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session
Nov 20 13:42:59 RasPi4B sddm-helper[572]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Nov 20 13:42:59 RasPi4B sddm-helper[496]: Starting: "/usr/share/sddm/scripts/wayland-session /usr/bin/startplasma-x11"
Nov 20 13:42:59 RasPi4B sddm-helper[575]: Jumping to VT 2
Nov 20 13:42:59 RasPi4B sddm-helper[575]: VT mode didn't need to be fixed
Nov 20 13:42:59 RasPi4B sddm[383]: Session started
Nov 20 13:43:00 RasPi4B sddm-helper[496]: [PAM] Closing session
Nov 20 13:43:00 RasPi4B sddm-helper[496]: pam_unix(sddm-autologin:session): session closed for user gbai
Nov 20 13:43:00 RasPi4B sddm-helper[496]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_close_session
Nov 20 13:43:00 RasPi4B sddm-helper[496]: pam_kwallet5(sddm-autologin:setcred): pam_kwallet5: pam_sm_setcred
Nov 20 13:43:00 RasPi4B sddm-helper[496]: [PAM] Ended.
Nov 20 13:43:00 RasPi4B sddm[383]: Auth: sddm-helper exited with 1
If the issue is not solved in the current ongoing diagnosis. This looks like the same issue in this thread with the pbp with malformed packages with the latest testing update.
I also have autologin enabled. I had been having issues with kwallet, and I recently deleted ~/.local/share/kdewalletd/kdewallet.kwl to reset it. Thinking this is messing up autologin too, I commented out the autologin section of /etc/sddm.conf.d/kde_settings.conf and I was able to login!
I noticed that the section “Session=” in kde_settings.conf had been blank, and after logging in manually and reenabling autologin with KDE settings that section now reads “Session=plasma”. FurN1, maybe try just adding that, (assuming you didn’t also reset kwallet)?
Decent information! I tried commenting out User=<my username> and added Session=plasma in /etc/sddm.conf.d/kde_settings.conf, and now I can log in desktop by enter password in the login screen.
Then I tried commenting out Session=plasma, and I can login to desktop as well. Looks like Session=plasma is not necessary?
Edit:
So after login-in desktop, I re-enabled autologin with KDE settings as you mentioned. Now the /etc/sddm.conf.d/kde_settings.conf changed, from this at the very beginning:
And now if I reboot Raspberry Pi, it does autologin and I can see the desktop without any problem. Maybe this re-generating the kde_settings.conf file did the magic? Maybe this is a change in KDE Plasma from its 5.19 version to 5.20.