You are not logged in.
So I have been using arch on my gigabyte laptop, running an nvidia 4060 and an intel cpu, everytime after I log in, it works for about 2 minutes and then boots me back to the sddm login screen. Curious enough when I try to change to tty, the login screen dissapears and I'm back inside KDE where I left off,
I use SDDM with KDE. Nvidia Graphics and Intel cpu with iGPU.
Here are my recent boot logs
Any help is appreciated.
Offline
Apr 16 10:13:31 KHALED-BM sudo[4161]: khaled : TTY=pts/1 ; PWD=/home/khaled ; USER=root ; COMMAND=/usr/bin/journalctl -esudo journalctl -bafter the session failed, you can
sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'Edit: there's somehow a 90s session
Apr 16 10:11:42 KHALED-BM (systemd)[1029]: pam_unix(systemd-user:session): session opened for user khaled(uid=1000) by khaled(uid=0)
Apr 16 10:11:42 KHALED-BM systemd[1]: Started Session 2 of User khaled.
Apr 16 10:13:12 KHALED-BM sddm-helper[1023]: pam_unix(sddm:session): session closed for user khaledseems dbus related.
echo $DBUS_SESSION_BUS_ADDRESSLast edited by seth (2026-04-16 13:15:09)
Offline
I did an update today, and so far I've rebooted the pc a few times and the error hasn't happened yet, but I'm still observing it, for the Dbus command:
echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/busEdit: there's somehow a 90s session
Also, what does this mean
Offline
There was a session that ran for ~90s (suspiciously the default systemd service timeout)
the error hasn't happened yet, but I'm still observing it
Errr? Hein?
The dbus address is fine, unless the problem still manifests and please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
You can remove the tag and bump the thread w/ a new journal if and when this happens again.
Offline