"systemd-boot: Assertion failed, halting" after system update

4o9fish7t3 · 2026-03-27 03:08:57

I was trying to update firefox on my laptop, but there were issues with libgcc and libstdc++ having conflicting files. I tried a couple of things I found on this forum (I can't remember what, and my system won't boot so I can't check), and eventually it installed the update, but then firefox wouldn't run, with an error about "/usr/lib/libc.so.6 version ... not found". so then I tried a system update with `pacman -Syu`, and that failed with a bunch of messages. When I tried rebooting my system, I now see:

../systemd/src/boot/log.c:30@efi_assert: systemd-boot: Assertion 'BS->AllocatePages(type, memory_type, n_pages, &addr) == EFI_SUCCESS' failed at ../systemd/src/boot/util.h:95@xmalloc_pages, halting

why did updating my system brick my device? was there some other way of just getting firefox to update and run? what am I supposed to do now, is there a way to repair or get it booting again, or should I just re-install?

would appreciate any help or advice on what to do next.
Thanks,
4o9fish7t3

Last edited by 4o9fish7t3 (2026-03-27 03:09:54)

5hridhyan · 2026-03-27 06:46:53

Ah! if you have a backup I recommend re-installing, if not, lets try recovering it, and its obvious, chroot your system, and try to update from there, and after it updates, re-install bootloader, re-generate initramfs, and you should be good to go

refer these
https://wiki.archlinux.org/title/Chroot
https://wiki.archlinux.org/title/Pacman … ng_install also "overwriting" should be the LAST resort, if & only if pacman fails to update
https://wiki.archlinux.org/title/Systemd-boot#

Also updating didn't "brick" your device, "partial upgrade" did a "software-bork"
Good Luck

Edit:
added links.

Last edited by 5hridhyan (2026-03-27 07:00:01)

4o9fish7t3 · 2026-03-27 19:10:55

I managed to boot into SystemRescue 12.03 and use it to mount the disk of my broken system.

I ran the example from the wiki link for "pacman/Tips and tricks#Recovering broken install from existing install"

pacman -S $(pacman -Qq --dbpath /brokenArch/var/lib/pacman) --root /brokenArch --dbpath /brokenArch/var/lib/pacman

and it printed `warning: [package-version] is up to date -- reinstalling` for each package.

next, I ran `arch-chroot /brokenArch` then `bootctl install` from the wiki link for systemd-boot, and got this error:

bootctl: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory

everything appears broken, even running `pacman -Qq` prints

pacman: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

before when I ran pacman from SystemRescue to re-install all packages on the broken system, I noticed:

warning: libgcc-15.2.1+r604+g0b99615a8aef-1 is up to date -- reinstalling
warning: libstdc++-15.2.1+r604+g0b99615a8aef-1 is up to date -- reinstalling

I didn't know what else to try, so I just took a guess and tried re-installing the problematic shared library packages again:

pacman -S libgcc --root /brokenArch --dbpath /brokenArch/var/lib/pacman
pacman -S libstdc++ --root /brokenArch --dbpath /brokenArch/var/lib/pacman

and now it magically works? is this a normal feature of pacman that I don't understand? do I need to individually run `pacman -S [package name]` for each installed package a second time to make sure they're correctly re-installed?

this seems really weird to me.

...

moving on, I ran `bootctl install`. I don't think there were any errors, but I'm not familiar with this command.

then, I had to look up how to "re-generate initramfs", found a wiki article for `mkinitcpio`, and ran `mkinitcpio -p linux`

this had a ton of errors, mostly "module not found", along with warnings: "No modules added to the image. This is probably not what you want.", "errors were encountered during the build. The image may not be complete."

right now, the "systemd-boot Assertion" error is gone, but LUKS can not decrypt my drive when I try to boot it. it prints:

Cannot initialize device-mapper. Is dm_mod kernel module loaded?
Cannot use device root, name is invalid or still in use.

I'm out of ideas again, so I try running `bootctl install` again followed by `bootctl update` maybe?

but I'm still getting Cannot initialize device-mapper.

I tried making a copy of `/etc/mkinitcpio.conf`, and adding "sd-encrypt" to HOOKS, and running `mkinitcpio -p linux --config /etc/mkinitcpio-copy.conf`, but it just keeps running the original build hooks and ignoring any changes I make to the new config file... so I'm not really sure what's going on with that.

maybe there's still a broken pacman package that I need to reinstall? but I do not know which one.

is there another mkinitcpio config file I'm not aware of? since it was ignore any changes I made to the copy.

which hook would include the missing dm_mod kernel module?

Last edited by 4o9fish7t3 (2026-03-27 19:17:59)

4o9fish7t3 · 2026-03-28 00:53:36

I found a post on reddit from 2 years ago, someone mentioned checking the output of `pacman -Q linux`. I wasn't aware there was even a package named "linux". so I ran `pacman -S linux`, it appears to have run mkinitcpio after it reinstalled linux-6.19.9.arch1-1

https://www.reddit.com/r/archlinux/comm … y_modules/

my system is now "fixed", and I am able to boot into my previously broken system, although I'm still not sure why it broke in the first place, or how to avoid this from happening again in the future...

I don't understand pacman at all. the command on the wiki `pacman -S $(pacman -Qq)` doesn't appear to actually work; it doesn't appear it was re-installing packages until I specified each broken package individually:

pacman -S libgcc
pacman -S libstdc++
pacman -S linux

does the wiki article need to be updated, or is this some sort of bug?

what is the best way to upgrade my system without the risk of things breaking like they did? should I trust `pacman -Syu`, or maybe there's another way I'm not aware of? maybe a script that runs `pacman -Uy [package name]` individually for each package?

...

now it appears there's something wrong with the NetworkManager service; KDE's "Networks" GUI says the "NetworkManager service is not running"; however, `ip address` reports I am connected to my wifi network. I guess I'll open a new topic if I can't figure out how to fix it tomorrow.

thanks for your help, 5hridhyan!

5hridhyan · 2026-03-28 04:28:07

First of all, respect, you actually managed to fix it
The wiki isn’t wrong, but your runtime was broken, so pacman -S $(pacman -Qq) didn't work in that state because pacman itself couldn’t run properly with missing libgcc/libstdc++? anyways by reinstalling those first, you restored enough of the system for everything else to function again...

also, your mkinitcpio might have failed because a partial upgrade desynced your running kernel from the modules in /usr/lib/modules? anyways reinstalling the linux package ensured the kernel image and modules matched again, allowing LUKS to find the dm_mod driver...

to avoid this never try to update a single package alone(altough I never faced such disaster just bcz of it, avoid updating "single"/individual packages, like never sync package databases without upgrading everything); on Arch, pacman -Syu is the only supported way to keep dependencies in sync... I also resommend tools like https://wiki.archlinux.org/title/Timeshift or https://wiki.archlinux.org/title/Snapper for backup, anyways once go through this https://wiki.archlinux.org/title/System_backup

Edit:
Since you fixed the core libraries, it probably just needs a kick, try restarting the NetworkManager. If it's still weird, re-install it now that you're booted, && feel free to open a new thread if it didn't fix

Last edited by 5hridhyan (2026-03-28 04:45:59)

4o9fish7t3 · 2026-03-28 13:33:17

5hridhyan wrote:

your runtime was broken, so pacman -S $(pacman -Qq) didn't work in that state because pacman itself couldn’t run properly with missing libgcc/libstdc++?

not quite; I was running `pacman -S $(pacman -Qq --dbpath /brokenArch/var/lib/pacman) --root /brokenArch --dbpath /brokenArch/var/lib/pacman`, that was called from the SystemRescue live os, not from the broken system. my understanding was that command was re-installing all packages, but that assumption was false, because I was required to call:

pacman -S libgcc --root /brokenArch --dbpath /brokenArch/var/lib/pacman
pacman -S libstdc++ --root /brokenArch --dbpath /brokenArch/var/lib/pacman

in order for the errors about the missing shared libraries to be fixed (when I run `pacman` and `bootctl` within the arch-chroot of the broken system).

after I was in the `arch-chroot`, while trying to get `mkinitcpio` working, I tried `pacman -S $(pacman -Qq)` multiple times; like last time, that command was falsely reporting that it was re-installing all packages, and running `mkinitcpio` kept failing until I specifically ran `pacman -S linux`

5hridhyan wrote:

avoid updating "single"/individual packages, like never sync package databases without upgrading everything

so this advice seems to be counter to what I've experienced; I was only able to fix these issues because pacman was falsely claiming it was re-installing everything, I had to call it with exactly one package name for it to actually re-install it. unless I'm misunderstanding, which is entirely possible.

seth · 2026-03-28 14:54:48

I was trying to update firefox on my laptop, but there were issues with libgcc and libstdc++

This sounds a hell lot like you were conducting a partial update and ran into the gcc-libs split.
https://wiki.archlinux.org/title/System … nsupported

What is the status quo here?
System runs, "sudo pacman -Syu" works w/o problems?

sudo LC_ALL=C pacman -Qkk |& grep -v ', 0 altered files' | grep -v backup

will provide an oversight of the overall package integrity, some deviations are normal, so don't scarejump

4o9fish7t3 · 2026-03-28 15:17:08

hmmm, well then I'm confused why the wiki recommends running `pacman -S $(pacman -Qq --dbpath /brokenArch/var/lib/pacman) --root /brokenArch --dbpath /brokenArch/var/lib/pacman` for "Recovering broken install from existing install" if that command won't actually fix any broken packages...

so was my mistake that I attempted to upgrade my firefox package when I should have run `pacman -Syu` instead? the documentation is kinda hard for me to wrap my head around. the manual page for pacman(8) says:

-U, --upgrade
Upgrade or add package(s) to the system and install the required dependencies from sync repositories. ...

but now I'm seeing on the wiki in multiple places that `pacman -Syu` should pretty much always be used, when a package needs to be upgraded? this is quite confusing to me. maybe the meaning of these flags has changed over time? or I'm just really unfamiliar with the terminology?

...

I plan looking into the NetworkManager issue more later today. it's quite odd;

`ip address` says I am connected to my wifi network, and firefox can load web pages, even when NetworkManager isn't running. I did `sudo pacman -S networkmanager`, and I have to manually start the service with `systemctl start NetworkManager.service` after I login. then, running `nmcli` several times shows that wlan0 cycles between "disconnected" and "configuring".

when I have time I'll try looking up how to access the logs for NetworkManager and see what I can find from there.

Scimmia · 2026-03-28 15:19:28

https://wiki.archlinux.org/title/System … nsupported

-U is used for specific package files, not just installing by package name.

Last edited by Scimmia (2026-03-28 15:23:05)

seth · 2026-03-28 15:49:24

if that command won't actually fix any broken packages...

It ideally would - the question merely was whether there're remaining problems nevertheless.

4o9fish7t3 · 2026-03-28 16:39:41

apologies seth, it looks like your reply came in as I was replying to 5hridhyan. thank you for the clarification Scimmia, I guess I will have to read about how pacman works a bit more, since a lot of my assumptions about it need clarifying.

I am able to confirm that my original issue is "solved"! I can boot into my previously broken system, and `pacman -Syu` reports no errors. the only remaining problem is with NetworkManager, which I will open a new topic if I get stuck with troubleshooting and fixing. Thank you for your help, everyone!

I will be sure to use `pacman -Syu` in the future. although I wish pacman was a bit more "idiot-proof" in regard to breaking the system by doing a partial system upgrade, I understand responsibility ultimately lies on me the (idiot ) user.

`pacman -Qkk` doesn't report any errors; some warnings. although I am noticing the output is a bit mangled; for example:

...
libutempter: 20 total files, 1 altered file
poppler: 170 total files, 0 altewarning: shadow: /usr/bin/groupmems (GID mismatch)
warning: shadow: /usr/bin/groupmems (Permissions mismatch)
red files
shadow: 576 total files, 1 altered file
...

(isn't that a printf/stdout threading bug or something?)

seth wrote:

It ideally would

unfortunately it does not; like 5hridhyan suggested, when multiple packages are specified, appears to print "re-installing", but doesn't actually do so. regardless, I did manage to fix my issue (although I'm not completely sure how, since I have no idea what I'm doing, to be honest.)

I'll try to keep in mind that `pacman -Qkk` filter command for the future, thanks seth.

tekstryder · 2026-03-28 16:54:40

4o9fish7t3 wrote:

I am noticing the output is a bit mangled; for example:

Remove the ampersand.

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files' | grep -v backup

Also, what's the full output?

4o9fish7t3 · 2026-03-28 17:33:28

full output of the new command:

[user@system ~]$ sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files' | grep -v backup
warning: filesystem: /root (Permissions mismatch)
warning: ghc-libs: /usr/lib/ghc-9.6.6/lib/package.conf.d/package.cache (Modification time mismatch)
warning: ghc-libs: /usr/lib/ghc-9.6.6/lib/package.conf.d/package.cache (Size mismatch)
warning: ghc-libs: /usr/lib/ghc-9.6.6/lib/package.conf.d/package.cache (SHA256 checksum mismatch)
warning: intel-ucode: /boot/intel-ucode.img (Permissions mismatch)
warning: intel-ucode: /boot/intel-ucode.img (Modification time mismatch)
warning: libutempter: /usr/lib/utempter/utempter (GID mismatch)
warning: libutempter: /usr/lib/utempter/utempter (Permissions mismatch)
warning: shadow: /usr/bin/groupmems (GID mismatch)
warning: shadow: /usr/bin/groupmems (Permissions mismatch)
warning: systemd: /var/log/journal (GID mismatch)
filesystem: 127 total files, 1 altered file
ghc-libs: 1563 total files, 1 altered file
intel-ucode: 161 total files, 1 altered file
libutempter: 20 total files, 1 altered file
shadow: 576 total files, 1 altered file
systemd: 1826 total files, 1 altered file

nothing about NetworkManager, but I haven't had the motivation to dive into it yet.

(I'm curious as to how removing the ampersand fixed the output; I was looking at the bash manual, section "3.2.3 Pipelines", but I'm afraid I don't understand how using `|` instead of `|&` fixed it...)

seth · 2026-03-28 20:17:53

@tekstryder, I never tracked this down but the mangled output usually doesn't hinge on the stderr output

@4o9fish7t3, |& is a bashism for "2>&1 |"
The output looks unsuspicious \o/

systemctl status NetworkManager.service
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

4o9fish7t3 · 2026-03-29 14:39:22

I had to run `systemctl enable NetworkManager.service` so NetworkManager would start a boot. (but I was still able to access the internet without it running).

[user@system ~]$ systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Sun 2026-03-29 08:42:08 CDT; 39min ago
 Invocation: e23417f4dbc142e3bc5c3f7b3c50ba13
       Docs: man:NetworkManager(8)
   Main PID: 1050 (NetworkManager)
      Tasks: 4 (limit: 9167)
     Memory: 21.8M (peak: 22.3M)
        CPU: 4.086s
     CGroup: /system.slice/NetworkManager.service
             └─1050 /usr/bin/NetworkManager --no-daemon

Mar 29 09:22:00 system NetworkManager[1050]: <info>  [1774794120.4036] device (wlan0): supplicant interface state: inactive -> interface_disabled
Mar 29 09:22:00 system NetworkManager[1050]: <info>  [1774794120.4037] device (p2p-dev-wlan0): supplicant management interface state: inactive -> interface_disabled
Mar 29 09:22:00 system NetworkManager[1050]: <info>  [1774794120.4053] device (wlan0): supplicant interface state: interface_disabled -> inactive
Mar 29 09:22:00 system NetworkManager[1050]: <info>  [1774794120.4054] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive
Mar 29 09:22:03 system NetworkManager[1050]: <info>  [1774794123.0047] device (wlan0): supplicant interface state: inactive -> associated
Mar 29 09:22:03 system NetworkManager[1050]: <info>  [1774794123.0047] device (p2p-dev-wlan0): supplicant management interface state: inactive -> associated
Mar 29 09:22:03 system NetworkManager[1050]: <info>  [1774794123.0101] device (wlan0): supplicant interface state: associated -> disconnected
Mar 29 09:22:03 system NetworkManager[1050]: <info>  [1774794123.0101] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Mar 29 09:22:03 system NetworkManager[1050]: <info>  [1774794123.1102] device (wlan0): supplicant interface state: disconnected -> inactive
Mar 29 09:22:03 system NetworkManager[1050]: <info>  [1774794123.1103] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive

[user@system ~]$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
dbus-org.freedesktop.network1.service    | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
iwd.service                              | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
snapper-cleanup.timer                    | timers.target.wants
snapper-timeline.timer                   | timers.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-networkd-wait-online.service     | network-online.target.wants
systemd-network-generator.service        | sysinit.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants

[user@system ~]$ nmcli
lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

wlan0: disconnected
        "Intel Wireless-AC 3168NGW"
        2 connections available
        wifi (iwlwifi), AE:0E:02:C4:34:D8, hw, mtu 1500

p2p-dev-wlan0: disconnected
        "p2p-dev-wlan0"
        wifi-p2p, hw

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
[user@system ~]$ ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ae:0e:02:c4:34:d8 brd ff:ff:ff:ff:ff:ff permaddr XX:XX:XX:XX:XX:XX
    inet 192.168.1.121/24 metric 600 brd 192.168.1.255 scope global dynamic wlan0
       valid_lft 6923sec preferred_lft 6923sec

I tried messing around with connecting and disconnecting from networks while journalctl was following and printing

[user@system ~]$ journalctl -u NetworkManager -f
Mar 29 08:49:00 system NetworkManager[1050]: <info>  [1774792140.8650] device (wlan0): supplicant interface state: inactive -> disconnected
Mar 29 08:49:00 system NetworkManager[1050]: <info>  [1774792140.8651] device (p2p-dev-wlan0): supplicant management interface state: inactive -> disconnected
Mar 29 08:49:00 system NetworkManager[1050]: <info>  [1774792140.8689] device (wlan0): supplicant interface state: disconnected -> inactive
Mar 29 08:49:00 system NetworkManager[1050]: <info>  [1774792140.8690] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Mar 29 08:49:02 system NetworkManager[1050]: <info>  [1774792142.0651] device (wlan0): supplicant interface state: inactive -> associated
Mar 29 08:49:02 system NetworkManager[1050]: <info>  [1774792142.0652] device (p2p-dev-wlan0): supplicant management interface state: inactive -> associated
Mar 29 08:49:02 system NetworkManager[1050]: <info>  [1774792142.0710] device (wlan0): supplicant interface state: associated -> disconnected
Mar 29 08:49:02 system NetworkManager[1050]: <info>  [1774792142.0711] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Mar 29 08:49:02 system NetworkManager[1050]: <info>  [1774792142.1703] device (wlan0): supplicant interface state: disconnected -> inactive
Mar 29 08:49:02 system NetworkManager[1050]: <info>  [1774792142.1705] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
-- I try to connect to my router's first SSID (5 GHz) via KDE Networks GUI; popup box says the password is wrong, but I have triple checked that the cleartext is correct; --
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.1802] device (wlan0): Activation: starting connection 'MY-SSID-1' (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.1803] audit: op="connection-add-activate" uuid="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" name="MY-SSID-1" pid=1507 uid=1000 result="success"
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.1806] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.1808] manager: NetworkManager state is now CONNECTING
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2245] device (wlan0): set-hw-addr: reset MAC address to XX:XX:XX:XX:XX:XX (preserve)
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2300] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2302] device (wlan0): Activation: (wifi) access point 'MY-SSID-1' has security, but secrets are required.
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2303] device (wlan0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2304] sup-iface[d6e5653e0d9092ff,0,wlan0]: wps: type pbc start...
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2308] device (wlan0): supplicant interface state: inactive -> disconnected
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2308] device (p2p-dev-wlan0): supplicant management interface state: inactive -> disconnected
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2310] device (wlan0): supplicant interface state: disconnected -> inactive
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2311] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2335] device (wlan0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2339] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2343] device (wlan0): Activation: (wifi) connection 'MY-SSID-1' has security, and secrets exist.  No new secrets needed.
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2344] Config: added 'ssid' value 'MY-SSID-1'
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2344] Config: added 'scan_ssid' value '1'
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2344] Config: added 'bgscan' value 'simple:30:-70:86400'
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2344] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 SAE'
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2344] Config: added 'auth_alg' value 'OPEN'
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2345] Config: added 'psk' value '<hidden>'
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2349] device (wlan0): supplicant interface state: inactive -> scanning
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2349] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2957] device (wlan0): supplicant interface state: scanning -> disconnected
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.2958] device (p2p-dev-wlan0): supplicant management interface state: scanning -> disconnected
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.3215] device (wlan0): supplicant interface state: disconnected -> associated
Mar 29 08:52:58 system NetworkManager[1050]: <info>  [1774792378.3215] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> associated
Mar 29 08:53:08 system NetworkManager[1050]: <info>  [1774792388.3235] device (wlan0): supplicant interface state: associated -> disconnected
Mar 29 08:53:08 system NetworkManager[1050]: <info>  [1774792388.3236] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Mar 29 08:53:08 system NetworkManager[1050]: <info>  [1774792388.4232] device (wlan0): supplicant interface state: disconnected -> scanning
Mar 29 08:53:08 system NetworkManager[1050]: <info>  [1774792388.4233] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Mar 29 08:53:19 system NetworkManager[1050]: <info>  [1774792399.4803] device (wlan0): supplicant interface state: scanning -> disconnected
Mar 29 08:53:19 system NetworkManager[1050]: <info>  [1774792399.4803] device (p2p-dev-wlan0): supplicant management interface state: scanning -> disconnected
Mar 29 08:53:23 system NetworkManager[1050]: <warn>  [1774792403.7149] device (wlan0): Activation: (wifi) association took too long
Mar 29 08:53:23 system NetworkManager[1050]: <info>  [1774792403.7150] device (wlan0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Mar 29 08:53:23 system NetworkManager[1050]: <warn>  [1774792403.7160] device (wlan0): Activation: (wifi) asking for new secrets
Mar 29 08:53:29 system NetworkManager[1050]: <info>  [1774792409.4814] device (wlan0): supplicant interface state: disconnected -> inactive
Mar 29 08:53:29 system NetworkManager[1050]: <info>  [1774792409.4815] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Mar 29 08:53:29 system NetworkManager[1050]: <warn>  [1774792409.8568] device (wlan0): no secrets: User canceled the secrets request.
Mar 29 08:53:29 system NetworkManager[1050]: <info>  [1774792409.8569] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', managed-type: 'full')
Mar 29 08:53:29 system NetworkManager[1050]: <info>  [1774792409.8579] manager: NetworkManager state is now DISCONNECTED
Mar 29 08:53:29 system NetworkManager[1050]: <info>  [1774792409.8992] device (wlan0): set-hw-addr: set MAC address to D6:18:95:9E:5A:26 (scanning)
Mar 29 08:53:29 system NetworkManager[1050]: <warn>  [1774792409.9035] device (wlan0): Activation: failed for connection 'MY-SSID-1'
Mar 29 08:53:29 system NetworkManager[1050]: <info>  [1774792409.9041] device (wlan0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Mar 29 08:53:32 system NetworkManager[1050]: <info>  [1774792412.5102] device (wlan0): supplicant interface state: inactive -> associated
Mar 29 08:53:32 system NetworkManager[1050]: <info>  [1774792412.5103] device (p2p-dev-wlan0): supplicant management interface state: inactive -> associated
Mar 29 08:53:32 system NetworkManager[1050]: <info>  [1774792412.5157] device (wlan0): supplicant interface state: associated -> disconnected
Mar 29 08:53:32 system NetworkManager[1050]: <info>  [1774792412.5158] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Mar 29 08:53:32 system NetworkManager[1050]: <info>  [1774792412.6157] device (wlan0): supplicant interface state: disconnected -> inactive
Mar 29 08:53:32 system NetworkManager[1050]: <info>  [1774792412.6158] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
-- I connected to my router's second SSID (2.4 GHz); same password as first SSID, says it's able to connect --
Mar 29 09:00:23 system NetworkManager[1050]: <info>  [1774792823.7955] device (wlan0): set-hw-addr: set MAC address to 9A:6C:38:E2:99:7C (scanning)
Mar 29 09:00:23 system NetworkManager[1050]: <info>  [1774792823.8015] device (wlan0): supplicant interface state: inactive -> interface_disabled
Mar 29 09:00:23 system NetworkManager[1050]: <info>  [1774792823.8016] device (p2p-dev-wlan0): supplicant management interface state: inactive -> interface_disabled
Mar 29 09:00:23 system NetworkManager[1050]: <info>  [1774792823.8029] device (wlan0): supplicant interface state: interface_disabled -> inactive
Mar 29 09:00:23 system NetworkManager[1050]: <info>  [1774792823.8030] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive
Mar 29 09:00:24 system NetworkManager[1050]: <info>  [1774792824.9938] device (wlan0): supplicant interface state: inactive -> associated
Mar 29 09:00:24 system NetworkManager[1050]: <info>  [1774792824.9938] device (p2p-dev-wlan0): supplicant management interface state: inactive -> associated
Mar 29 09:00:24 system NetworkManager[1050]: <info>  [1774792824.9994] device (wlan0): supplicant interface state: associated -> disconnected
Mar 29 09:00:24 system NetworkManager[1050]: <info>  [1774792824.9994] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Mar 29 09:00:25 system NetworkManager[1050]: <info>  [1774792825.0991] device (wlan0): supplicant interface state: disconnected -> inactive
Mar 29 09:00:25 system NetworkManager[1050]: <info>  [1774792825.0991] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.5593] device (wlan0): Activation: starting connection 'MY-SSID-2' (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.5594] audit: op="connection-add-activate" uuid="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" name="MY-SSID-2" pid=1507 uid=1000 result="success"
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.5599] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.5601] manager: NetworkManager state is now CONNECTING
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6003] device (wlan0): set-hw-addr: reset MAC address to XX:XX:XX:XX:XX:XX (preserve)
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6055] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6056] device (wlan0): Activation: (wifi) access point 'MY-SSID-2' has security, but secrets are required.
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6056] device (wlan0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6057] sup-iface[d6e5653e0d9092ff,0,wlan0]: wps: type pbc start...
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6060] device (wlan0): supplicant interface state: inactive -> disconnected
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6061] device (p2p-dev-wlan0): supplicant management interface state: inactive -> disconnected
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6062] device (wlan0): supplicant interface state: disconnected -> inactive
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6062] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6076] device (wlan0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6078] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6079] device (wlan0): Activation: (wifi) connection 'MY-SSID-2' has security, and secrets exist.  No new secrets needed.
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6080] Config: added 'ssid' value 'MY-SSID-2'
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6080] Config: added 'scan_ssid' value '1'
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6080] Config: added 'bgscan' value 'simple:30:-70:86400'
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6080] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 SAE'
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6080] Config: added 'auth_alg' value 'OPEN'
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6080] Config: added 'psk' value '<hidden>'
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6083] device (wlan0): supplicant interface state: inactive -> scanning
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6083] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6541] device (wlan0): supplicant interface state: scanning -> authenticating
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6541] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6721] device (wlan0): supplicant interface state: authenticating -> disconnected
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6721] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> disconnected
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6916] device (wlan0): supplicant interface state: disconnected -> associated
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6916] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> associated
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6969] device (wlan0): supplicant interface state: associated -> disconnected
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.6969] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.7986] device (wlan0): supplicant interface state: disconnected -> scanning
Mar 29 09:01:28 system NetworkManager[1050]: <info>  [1774792888.7986] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Mar 29 09:01:39 system NetworkManager[1050]: <info>  [1774792899.9757] device (wlan0): supplicant interface state: scanning -> authenticating
Mar 29 09:01:39 system NetworkManager[1050]: <info>  [1774792899.9758] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating
Mar 29 09:01:39 system NetworkManager[1050]: <info>  [1774792899.9827] device (wlan0): supplicant interface state: authenticating -> associating
Mar 29 09:01:39 system NetworkManager[1050]: <info>  [1774792899.9827] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.0079] device (wlan0): supplicant interface state: associating -> associated
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.0080] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.1075] device (wlan0): supplicant interface state: associated -> completed
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.1076] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "MY-SSID-2"
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.1076] device (p2p-dev-wlan0): supplicant management interface state: associated -> completed
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.1079] device (wlan0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.1105] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.7408] dhcp4 (wlan0): state changed new lease, address=192.168.1.111, acd pending
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.8567] dhcp4 (wlan0): state changed new lease, address=192.168.1.111
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.8618] policy: set 'MY-SSID-2' (wlan0) as default for IPv4 routing and DNS
Mar 29 09:01:40 system NetworkManager[1050]: <warn>  [1774792900.8838] dns-sd-resolved[b5d77ac50c51bcf9]: send-updates SetLinkDomains@3 failed: GDBus.Error:org.freedesktop.resolve1.LinkBusy: Link wlan0 is managed.
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.8848] device (wlan0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.9403] device (wlan0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.9406] device (wlan0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.9411] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 29 09:01:40 system NetworkManager[1050]: <info>  [1774792900.9421] device (wlan0): Activation: successful, device activated.
-- here, I disconnected from the network via KDE Networks GUI (thru NetworkManager) --
Mar 29 09:02:25 system NetworkManager[1050]: <info>  [1774792945.1881] audit: op="statistics" interface="wlan0" ifindex=3 args="2000" pid=1507 uid=1000 result="success"
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.3635] device (wlan0): state change: activated -> deactivating (reason 'user-requested', managed-type: 'full')
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.3642] manager: NetworkManager state is now DISCONNECTING
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.3666] audit: op="device-disconnect" interface="wlan0" ifindex=3 pid=1507 uid=1000 result="success"
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.3944] audit: op="statistics" interface="wlan0" ifindex=3 args="0" pid=1507 uid=1000 result="success"
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.4298] device (wlan0): supplicant interface state: completed -> disconnected
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.4299] device (p2p-dev-wlan0): supplicant management interface state: completed -> disconnected
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.4300] device (wlan0): state change: deactivating -> disconnected (reason 'user-requested', managed-type: 'full')
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.4308] dhcp4 (wlan0): canceled DHCP transaction
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.4308] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.4308] dhcp4 (wlan0): state changed no lease
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.4460] device (wlan0): set-hw-addr: set MAC address to 2E:34:97:3E:DB:5D (scanning)
Mar 29 09:02:30 system NetworkManager[1050]: <info>  [1774792950.5023] manager: NetworkManager state is now DISCONNECTED
-- after this, `ip address` briefly showed wlan0 with no IP addr, but now shows I'm on 192.168.1.116; I am still able to access the web --

from when I first login to now, I am still able to access the internet (I'm posting this from the device in question) regardless of what NetworkManager says (or is even running). when I try reconnecting (to the same or a different SSID) I'm given a new DHCP ip address. I do not have access to another SSID to check if I'm actually able to connect to a different subnet/router, since MY-SSID-1 and 2 are the same router but different radios. Right now, KDE Networks GUI and `nmcli` still report me as "disconnected"

seth · 2026-03-29 15:10:50

You now have iwd, system-networkd and NM enabled.
Previously the former two will have setup your network, but some networkmanager applet will of course not have reflected that.
Make up your mind how you want to configure your network and if that's NM, disable iwd and all systemd-networkd* units.
If you want to use iwd as NM backend see https://wiki.archlinux.org/title/Networ … Fi_backend

Arch Linux

#1 2026-03-27 03:08:57

"systemd-boot: Assertion failed, halting" after system update

#2 2026-03-27 06:46:53

Re: "systemd-boot: Assertion failed, halting" after system update

#3 2026-03-27 19:10:55

Re: "systemd-boot: Assertion failed, halting" after system update

#4 2026-03-28 00:53:36

Re: "systemd-boot: Assertion failed, halting" after system update

#5 2026-03-28 04:28:07

Re: "systemd-boot: Assertion failed, halting" after system update

#6 2026-03-28 13:33:17

Re: "systemd-boot: Assertion failed, halting" after system update

#7 2026-03-28 14:54:48

Re: "systemd-boot: Assertion failed, halting" after system update

#8 2026-03-28 15:17:08

Re: "systemd-boot: Assertion failed, halting" after system update

#9 2026-03-28 15:19:28

Re: "systemd-boot: Assertion failed, halting" after system update

#10 2026-03-28 15:49:24

Re: "systemd-boot: Assertion failed, halting" after system update

#11 2026-03-28 16:39:41

Re: "systemd-boot: Assertion failed, halting" after system update

#12 2026-03-28 16:54:40

Re: "systemd-boot: Assertion failed, halting" after system update

#13 2026-03-28 17:33:28

Re: "systemd-boot: Assertion failed, halting" after system update

#14 2026-03-28 20:17:53

Re: "systemd-boot: Assertion failed, halting" after system update

#15 2026-03-29 14:39:22

Re: "systemd-boot: Assertion failed, halting" after system update

#16 2026-03-29 15:10:50

Re: "systemd-boot: Assertion failed, halting" after system update

Board footer