cactux
September 18, 2025, 3:50pm
1
I have updated a number of packages today and the boot process stops short at:
Reached Target Graphical Interface
Starting Run Command After 5 Seconds When Graphical target is reached
Finished Run Command After 5 Seconds When Graphical target is reached
This is the first time I have encountered this issue. I was able to boot to TTY and set the pacman.conf back to 25-09-17 Archlinux Archive.
I downgraded all the updated packages. The system came back up.
I performed the update again
Now I am stuck with the 25-09-17 state of the affair.
Here is the list of the packages that got updated and downgraded, twice.
It doesn’t seem the systemd is to blame and some other thing can surely be excluded from the list of the suspects. But I can’t determine which one/ones I have to persecute.
Any and all help is greatly appreciated.
[2025-09-18T17:27:49+0200] [ALPM] downgraded alsa-card-profiles (1:1.4.8-2 -> 1:1.4.8-1)
[2025-09-18T17:27:49+0200] [ALPM] downgraded amd-ucode (20250917-1 -> 20250808-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded openssl (3.5.3-1 -> 3.5.2-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded systemd-libs (258-1 -> 257.9-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded dkms (3.2.2-1 -> 3.2.1-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded libpipewire (1:1.4.8-2 -> 1:1.4.8-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded pipewire (1:1.4.8-2 -> 1:1.4.8-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded pipewire-audio (1:1.4.8-2 -> 1:1.4.8-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded mesa (1:25.2.3-1 -> 1:25.2.2-2)
[2025-09-18T17:27:50+0200] [ALPM] downgraded gst-plugin-pipewire (1:1.4.8-2 -> 1:1.4.8-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded libnm (1.54.1-1 -> 1.54.0-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded libtiff (4.7.1-1 -> 4.7.0-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded linux-firmware-whence (20250917-1 -> 20250808-1)
[2025-09-18T17:27:50+0200] [ALPM] downgraded linux-firmware-amdgpu (20250917-1 -> 20250808-1)
[2025-09-18T17:27:51+0200] [ALPM] downgraded linux-firmware-intel (20250917-1 -> 20250808-1)
[2025-09-18T17:27:51+0200] [ALPM] downgraded linux-firmware-other (20250917-1 -> 20250808-1)
[2025-09-18T17:27:52+0200] [ALPM] downgraded ntp (4.2.8.p18-4 -> 4.2.8.p18-3)
[2025-09-18T17:27:52+0200] [ALPM] downgraded openssh (10.0p1-5 -> 10.0p1-4)
[2025-09-18T17:27:52+0200] [ALPM] downgraded pavucontrol (1:6.2-1 -> 1:6.1-1)
[2025-09-18T17:27:52+0200] [ALPM] downgraded pipewire-alsa (1:1.4.8-2 -> 1:1.4.8-1)
[2025-09-18T17:27:52+0200] [ALPM] downgraded pipewire-jack (1:1.4.8-2 -> 1:1.4.8-1)
[2025-09-18T17:27:52+0200] [ALPM] downgraded pipewire-pulse (1:1.4.8-2 -> 1:1.4.8-1)
[2025-09-18T17:27:53+0200] [ALPM] downgraded python-fonttools (4.60.0-1 -> 4.59.2-1)
[2025-09-18T17:27:53+0200] [ALPM] downgraded python-pynacl (1.6.0-1 -> 1.5.0-3)
[2025-09-18T17:27:53+0200] [ALPM] downgraded python-urwid (3.0.3-1 -> 3.0.2-1)
[2025-09-18T17:27:54+0200] [ALPM] downgraded signal-desktop (7.71.0-1 -> 7.70.0-1)
[2025-09-18T17:27:54+0200] [ALPM] downgraded systemd-sysvcompat (258-1 -> 257.9-1)
dalto
September 18, 2025, 3:54pm
2
cactux:
systemd-sysvcompat
Why are you getting an update to this without an associated bump to systemd 258? Do you already have systemd 258? If you don’t, it might be a partially updated mirror.
2 Likes
cactux
September 18, 2025, 4:01pm
3
Thanks @dalto ! I totally missed that one.
I’ll revert back pacman.conf and try refreshing the mirrorlist and post the list of the packages.
cactux
September 18, 2025, 4:09pm
4
I post the list here below but don’t you think something else may have caused the issue, since even there seems to be a mismatch between the systemd packages, the system booted back up after the downgrade.
Anyways, here is the list I get after refreshing the mirrors with:
rate-mirrors --protocol https arch --max-delay=3000 --completion=1 | sudo tee /etc/pacman.d/mirrorlist
Package (31) Old Version New Version Net Change
extra/alsa-card-profiles 1:1.4.8-1 1:1.4.8-2 0.00 MiB
core/amd-ucode 20250808-1 20250917-1 0.00 MiB
extra/dkms 3.2.1-1 3.2.2-1 0.00 MiB
extra/gst-plugin-pipewire 1:1.4.8-1 1:1.4.8-2 0.00 MiB
extra/libnm 1.54.0-1 1.54.1-1 0.00 MiB
extra/libpipewire 1:1.4.8-1 1:1.4.8-2 0.00 MiB
extra/libtiff 4.7.0-1 4.7.1-1 -0.52 MiB
core/linux-firmware-amdgpu 20250808-1 20250917-1 -0.51 MiB
core/linux-firmware-intel 20250808-1 20250917-1 2.85 MiB
core/linux-firmware-other 20250808-1 20250917-1 0.43 MiB
core/linux-firmware-whence 20250808-1 20250917-1 0.02 MiB
extra/mesa 1:25.2.2-2 1:25.2.3-1 0.00 MiB
core/mkinitcpio 39.2-3 39.2-5 0.00 MiB
extra/nano-syntax-highlighting 2025.07.01.r0.g256995b-1 2025.07.01.r0.g256995b-2 0.01 MiB
extra/networkmanager 1.54.0-1 1.54.1-1 0.01 MiB
extra/ntp 4.2.8.p18-3 4.2.8.p18-4 0.00 MiB
core/openssh 10.0p1-4 10.0p1-5 0.00 MiB
core/openssl 3.5.2-1 3.5.3-1 0.00 MiB
extra/pavucontrol 1:6.1-1 1:6.2-1 0.14 MiB
extra/pipewire 1:1.4.8-1 1:1.4.8-2 0.00 MiB
extra/pipewire-alsa 1:1.4.8-1 1:1.4.8-2 0.00 MiB
extra/pipewire-audio 1:1.4.8-1 1:1.4.8-2 0.00 MiB
extra/pipewire-jack 1:1.4.8-1 1:1.4.8-2 0.00 MiB
extra/pipewire-pulse 1:1.4.8-1 1:1.4.8-2 0.00 MiB
extra/python-fonttools 4.59.2-1 4.60.0-1 0.11 MiB
extra/python-pynacl 1.5.0-3 1.6.0-1 0.13 MiB
extra/python-urwid 3.0.2-1 3.0.3-1 0.00 MiB
extra/signal-desktop 7.70.0-1 7.71.0-1 0.10 MiB
core/systemd 257.9-1 258-1 1.34 MiB
core/systemd-libs 257.9-1 258-1 0.11 MiB
core/systemd-sysvcompat 257.9-1 258-1 0.00 MiB
swh
September 18, 2025, 4:22pm
5
These are my last 20 updates from today. Pipewire was updated yesterday.
╰─❯ grep -i upgraded /var/log/pacman.log | tail -20
[2025-09-18T18:14:36+0200] [ALPM] upgraded amd-ucode (20250808-1 -> 20250917-1)
[2025-09-18T18:14:36+0200] [ALPM] upgraded systemd-libs (257.9-1 -> 258-1)
[2025-09-18T18:14:36+0200] [ALPM] upgraded lib32-systemd (257.9-1 -> 258-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded libtiff (4.7.0-1 -> 4.7.1-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-whence (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-amdgpu (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-atheros (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-broadcom (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-cirrus (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-intel (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-mediatek (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-nvidia (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-other (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-radeon (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware-realtek (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded linux-firmware (20250808-1 -> 20250917-1)
[2025-09-18T18:14:37+0200] [ALPM] upgraded systemd (257.9-1 -> 258-1)
[2025-09-18T18:14:38+0200] [ALPM] upgraded systemd-resolvconf (257.9-1 -> 258-1)
[2025-09-18T18:14:38+0200] [ALPM] upgraded systemd-sysvcompat (257.9-1 -> 258-1)
[2025-09-18T18:14:39+0200] [ALPM] upgraded vtk (9.5.1-1 -> 9.5.2-1)
No issues here after rebooting. Only updates from AUR do not work
1 Like
cactux
September 18, 2025, 4:35pm
6
Thanks @swh for looking into this! I may venture to updating now again with fresh mirrors. Hopefully it will work out this time.
3 Likes
cactux
September 18, 2025, 5:44pm
8
@dalto @swh
Unfortunately the update took me to the same point of the breakage in the boot process.
Once again I booted into the TTY and downgraded everything back to 2025-09-17.
The system came back up after reboot.
Next time I updated everything but hold back systemd packages. The update was successful.
So it seems that systemd is breaking it for me. Or at least it breaks the graphical interface because I can boot just fine into TTY. Does that make any sense?
Package (3) Old Version New Version Net Change
core/systemd 257.9-1 258-1 1.34 MiB
core/systemd-libs 257.9-1 258-1 0.11 MiB
core/systemd-sysvcompat 257.9-1 258-1 0.00 MiB
Total Installed Size: 38.46 MiB
Net Upgrade Size: 1.45 MiB
:: Proceed with installation? [Y/n]
I said NO this time
PS. if you need some system info, please tell me and I’ll provide whatever you need to get to the bottom of this strange issue.
Maybe your problem isn’t the systemd update itself, but the initramfs update that should run right after? On my system, dracut ran automatically after the update and everything worked fine for all my kernels. I see you’re using mkinitcpio — could the issue be coming from that?
cactux
September 18, 2025, 6:35pm
10
I am not sure. mkinitcpio runs automatically after the update as well. It seems to produce bootable initramfs after I downgrade systemd. I don’t know what to make of it.
I’m having the issue as well, mkinitcpio was updated as well yesterday.
I’ll try downgrading it to see what happens.
1 Like
cactux
September 18, 2025, 6:47pm
12
There seems to be other people with similar issue as well:
opened 01:00PM - 18 Sep 25 UTC
bug
Hey,
Today after updating some packages and doing a reboot, the issue appeared,… where before it was working fine.
I tried reinstalling the kernel and also installed the lts version, both have the issue.
The only thing that worked was the Linux (fallback) boot option.
```
79162 [2025-09-18T09:18:38-0300] [ALPM] transaction started
79163 [2025-09-18T09:18:38-0300] [ALPM] upgraded alsa-card-profiles (1:1.4.8-1.1 -> 1:1.4.8-2.1)
79164 [2025-09-18T09:18:38-0300] [ALPM] upgraded systemd-libs (257.9-1 -> 258-1)
79165 [2025-09-18T09:18:38-0300] [ALPM] upgraded ccache (4.11.3-2.1 -> 4.12-1.1)
79166 [2025-09-18T09:18:38-0300] [ALPM] upgraded mesa (1:25.2.2-4 -> 1:25.2.3-2)
79167 [2025-09-18T09:18:39-0300] [ALPM] installed electron38 (38.1.2-1)
79168 [2025-09-18T09:18:39-0300] [ALPM] upgraded electron (1:37-1 -> 1:38-1)
79169 [2025-09-18T09:18:39-0300] [ALPM] upgraded electron36 (36.9.0-1.1 -> 36.9.1-1)
79170 [2025-09-18T09:18:40-0300] [ALPM] upgraded electron37 (37.5.0-1.1 -> 37.5.1-1)
79171 [2025-09-18T09:18:40-0300] [ALPM] upgraded libpipewire (1:1.4.8-1.1 -> 1:1.4.8-2.1)
79172 [2025-09-18T09:18:40-0300] [ALPM] upgraded pipewire (1:1.4.8-1.1 -> 1:1.4.8-2.1)
79173 [2025-09-18T09:18:40-0300] [ALPM] upgraded pipewire-audio (1:1.4.8-1.1 -> 1:1.4.8-2.1)
79174 [2025-09-18T09:18:40-0300] [ALPM] upgraded gst-plugin-pipewire (1:1.4.8-1.1 -> 1:1.4.8-2.1)
79175 [2025-09-18T09:18:40-0300] [ALPM] upgraded kubectl (1.33.4-1 -> 1.34.1-1)
79176 [2025-09-18T09:18:40-0300] [ALPM] upgraded lib32-systemd (257.9-1 -> 258-1)
79177 [2025-09-18T09:18:40-0300] [ALPM] upgraded libnm (1.54.0-1 -> 1.54.1-1)
79178 [2025-09-18T09:18:40-0300] [ALPM] upgraded lib32-libnm (1.54.0-1 -> 1.54.1-1)
79179 [2025-09-18T09:18:40-0300] [ALPM] upgraded lib32-libpipewire (1:1.4.8-1 -> 1:1.4.8-2)
79180 [2025-09-18T09:18:40-0300] [ALPM] upgraded lib32-mesa (1:25.2.2-3 -> 1:25.2.3-2)
79181 [2025-09-18T09:18:40-0300] [ALPM] upgraded lib32-pipewire (1:1.4.8-1 -> 1:1.4.8-2)
79182 [2025-09-18T09:18:40-0300] [ALPM] warning: /etc/systemd/user.conf installed as /etc/systemd/user.conf.pacnew
79183 [2025-09-18T09:18:40-0300] [ALPM] upgraded systemd (257.9-1 -> 258-1)
79184 [2025-09-18T09:18:40-0300] [ALPM-SCRIPTLET] Creating group 'clock' with GID 943.
79185 [2025-09-18T09:18:43-0300] [ALPM-SCRIPTLET] :: This is a systemd feature update. You may want to have a look at
79186 [2025-09-18T09:18:43-0300] [ALPM-SCRIPTLET] NEWS for what changed, or if you observe unexpected behavior:
79187 [2025-09-18T09:18:43-0300] [ALPM-SCRIPTLET] /usr/share/doc/systemd/NEWS
79188 [2025-09-18T09:18:43-0300] [ALPM] upgraded mkinitcpio (39.2-4 -> 39.2-6)
79189 [2025-09-18T09:18:43-0300] [ALPM] upgraded mypy (1.17.1-1 -> 1.18.1-1)
79190 [2025-09-18T09:18:43-0300] [ALPM] upgraded networkmanager (1.54.0-1 -> 1.54.1-1)
79191 [2025-09-18T09:18:43-0300] [ALPM] upgraded pipewire-alsa (1:1.4.8-1.1 -> 1:1.4.8-2.1)
79192 [2025-09-18T09:18:43-0300] [ALPM] upgraded pipewire-pulse (1:1.4.8-1.1 -> 1:1.4.8-2.1)
79193 [2025-09-18T09:18:43-0300] [ALPM] upgraded pipewire-v4l2 (1:1.4.8-1.1 -> 1:1.4.8-2.1)
79194 [2025-09-18T09:18:43-0300] [ALPM] upgraded python-fonttools (4.59.2-1.1 -> 4.60.0-1.1)
79195 [2025-09-18T09:18:43-0300] [ALPM] upgraded python-pynacl (1.5.0-3.1 -> 1.6.0-1.1)
79196 [2025-09-18T09:18:43-0300] [ALPM] upgraded python-pyopenssl (25.2.0-1 -> 25.3.0-1)
79197 [2025-09-18T09:18:43-0300] [ALPM] upgraded systemd-resolvconf (257.9-1 -> 258-1)
79198 [2025-09-18T09:18:43-0300] [ALPM] upgraded systemd-sysvcompat (257.9-1 -> 258-1)
79199 [2025-09-18T09:18:44-0300] [ALPM] upgraded ttc-iosevka (33.2.9-1 -> 33.3.0-1)
79200 [2025-09-18T09:18:44-0300] [ALPM] upgraded vulkan-virtio (1:25.2.2-4 -> 1:25.2.3-2)
79201 [2025-09-18T09:18:44-0300] [ALPM] transaction completed
```
Is there any package that could be the cause?
Interestingly, the cause, according to one of the posters is apparmor.d-git.
I have that package as well!
I am going to remove it and see if it all works out.
1 Like
That’s interesting. The fact that it only boots after downgrading systemd makes it look more like a compatibility issue between the newer systemd and the initramfs generated on your setup.
1 Like
cactux
September 18, 2025, 6:52pm
14
Removed the package. Updated the systemd stuff! Going to reboot!
It’s not mkinitcpio and I can confirm it’s apparmor.d-git. I removed it and was able to reboot and get to a graphical login again after that.
3 Likes
cactux
September 18, 2025, 7:03pm
17
@Cphusion @albersc2
One problem solved: apparmor.d-git
Another one appeared. My Flatpak apps won’t start
$ flatpak run io.gitlab.librewolf-community
bwrap: setting up uid map: Permission denied
error: Failed to sync with dbus proxy
1 Like
Try downgrading systemd again maybe that had an effect on flatpak as well?
cactux
September 18, 2025, 7:07pm
19
Seems to be related to the apparmor situation from the little I have been looking at:
opened 04:03PM - 12 Aug 24 UTC
closed 04:27PM - 12 Aug 24 UTC
bug
untriaged
platforms:Linux
app-kind:GUI
### Current behavior
When launching from terminal, DevToys doesn't start.
… ```bash
$ ./DevToys.Linux --disable-sanboxing
bwrap: setting up uid map: Permission denied
** (DevToys:2648460): ERROR **: 11:57:18.453: Failed to fully launch dbus-proxy: El proceso hijo terminĂł con el cĂłdigo 1
Abortado (`core' generado)
```
Relevant `journalctl` log:
```bash
$ journalctl -f
(...)
ago 12 12:11:14 lenovo-y540 rtkit-daemon[1784]: Supervising 11 threads of 8 processes of 1 users.
ago 12 12:11:35 lenovo-y540 kernel: audit: type=1400 audit(1723479095.677:169): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=2710574 comm="bwrap" requested="userns_create" target="unprivileged_userns"
ago 12 12:11:35 lenovo-y540 kernel: audit: type=1400 audit(1723479095.678:170): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=2710577 comm="bwrap" capability=8 capname="setpcap"
ago 12 12:11:35 lenovo-y540 kernel: audit: type=1400 audit(1723479095.678:171): apparmor="DENIED" operation="open" class="file" info="Failed name lookup - disconnected path" error=-13 profile="unprivileged_userns" name="proc/2710577/uid_map" pid=2710577 comm="bwrap" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
(...)
```
### How to reproduce it (as minimally and precisely as possible)
1. Download DevToys 2 from the releases page
2. Run `DevToys.linux` from terminal
### Expected behavior
DevToys should run
### Screenshots
_No response_
### Workaround
Downgrade to Ubuntu 22.04
### Affected platforms
Linux
### Affected DevToys kind
DevToys (app with GUI)
### DevToys Version
2.0.5.0
### Relevant Assets/Logs
_No response_
What a mess!
2 Likes
cactux
September 18, 2025, 7:27pm
20
@Cphusion @albersc2 @swh @dalto
Things seems finally to be running fine again.
The problematic package was apparmor.d-git as per the Github thread posted above.
Removing it solved the issue of non bootable initramfs.
However, it created another issue with launching the Flatpak apps.
At the end, I disabled apprmor.service, recreated the initramfs, booted back into the system and my Libre-flatpak-wolf is as Libre as before.
What a day, and what a waste of time, actually. And my head is killing me. So, so long guys! And Thanks!
3 Likes
