You are not logged in.
I suspect the culprit to be wlroots, which changed from `wlroots` to `wlroots0.18` when I updated. I'm using Sway.
The boot process shows lots of these lines at the end:
[ OK ] Started Session 1 of User ...
[ OK ] Started Session 2 of User ...
[ OK ] Started Session 3 of User ...
...
[ OK ] Started Session 19 of User ...At the moment I'm back to my system using a previous btrfs snapshot.
Last edited by tridra (2025-06-03 01:37:33)
Offline
Or mesa?
https://bbs.archlinux.org/viewtopic.php?id=305727&p=2
I assume you can boot the multi-user.target, disable the autologin/session start, check the journal for patterns of the mesa issue (nouveau, software rasterizer or zink) and see whether you maybe get an error message when trying to start sway manually from there.
Offline
I'll try that.
However mesa was not part of this update, only these packages got an update:
egl-x11-1.0.2-1
ipython-9.3.0-1
jq-1.8.0-1
luajit-2.1.1748459687-1
noto-fonts-1:2025.06.01-1
python-icalendar-6.3.1-1
python-inflate64-1.0.3-1
python-setuptools-1:80.9.0-1
python-zeroconf-0.147.0-2
qt6-base-6.9.0-2
river-0.3.9-1
sway-1:1.10.1-3
wlroots0.18-0.18.2-1
yazi-25.5.31-1
zziplib-0.13.80-1I also have an RTX 3060 using nvidia-open drivers if that's relevant.
Offline
I updated again without doing anything else. Same thing happened, I was trying to access some other TTYs and after a while the system showed me GDM.
The issue seems to be Sway. River works, which excludes the possibility of wlroots being the issue I think.
Offline
My issue was with mesa version 1:25.1.1-2, downgrading to version 1:25.0.4-1 has solved the issue.
By running sway direct in tty2, something like `sway & disown; sleep 15; pkill -9 sway` I was able to see a mesa error.
Last edited by rodstu (2025-06-02 02:53:23)
Offline
The mesa bug will not strike when using the nvidia(-open) driver.
Does sway leave behind a https://wiki.archlinux.org/title/Core_d … _core_dump or errors on the console when trying to start it manually?
Offline
Well, now I'm even more confused than before, I was able to start sway from TTY and it's running fine from what I can tell. I've no idea how to troubleshoot this. GDM is buggy though, it doesn't show me any DE/WM to choose from, I can't even log in from it.
There are no coredumps for sway or wlroots.
Last edited by tridra (2025-06-02 23:44:46)
Offline
Figured out what was the issue. For some reason this update overwrote `/usr/share/wayland-sessions/sway.desktop`, removing `--unsupported-gpu` which is needed for Nvidia GPUs.
Offline
For some reason? That's expected and normal, files in /usr almost always get overwritten when the package that owns them gets updated. NoExract in pacman.conf should take care of that.
Offline
It didn't get overridden by previous updates, I certainly didn't expect it.
Offline
And was sway in those previous updates?
https://gitlab.archlinux.org/archlinux/ … d/PKGBUILD is the previous PKGBUILD and doesn't have the session in the backup array and since I'm too lazy to look, I'm just postulating that it never was.
So the only way previous updates didn't change that file is because previous updates didn't include sway
Offline
Yes, you're right, the stable channel hasn't received updates in a while. I thought it had because I remember reading some news about it but it likely was about a release candidate of the newer version.
Offline