Arch Linux Forums

systemd-udevd 261.3-1 severe boot hang/slowdown, USB+DisplayPort broke

dummy@example.com (seth) — Sat, 12 Sep 2026 15:06:09 +0000

https://archlinux.org/packages/core/any/linux-firmware/ is a meta-package that drags all others in - you can probably remote that and the firmware packages you don't need and save like 200MB disk space

Issues with linux-firmware-amdgpu 20260910-1

dummy@example.com (loqs) — Sat, 12 Sep 2026 14:28:23 +0000

luffy69a wrote:

Even though i can boot now with downgrade there is still that error coming up when i reboot my system.

Does your system's initrd need to be rebuilt? Was the error present before the upgrade?

L2TP connection stopped working

dummy@example.com (loqs) — Sat, 12 Sep 2026 14:25:18 +0000

Cooleech wrote:

after downgrading from strongswan-6.1.0-2 to strongswan-6.0.7-1, now everything is back in order.

Please consider building strongswan 6.1.0 locally with IKE1 enabled so you benefit from the security fixes in the 6.1.0 release. This will also prepare your system for the openssl 4.0 update that will break strongswan-6.0.7-1.

Installing arch with a bios who block the usb boot

dummy@example.com (cryptearth) — Sat, 12 Sep 2026 14:12:47 +0000

"bios who block" -> https://deepl.com
as for your issue: what system EXACTLY? exact model number
where did you got grub in the first place?
what EXACTLY do you mean by "bios blocks boot from usb"?
where did you got the posted code from?

Hyprland scratchpad is not showing on anything other than desktop 1

dummy@example.com (thoth) — Sat, 12 Sep 2026 14:11:30 +0000

updated this morning and now does what it says on the tin, "Hyprland scratchpad is not showing on anything other than desktop 1"

Hyprland 0.56.2 built from branch v0.56.2 at commit efb50993780079460b0cbed1363e2166a2de1d9f clean ([gha] Nix: update inputs).
Date: Wed Aug 5 14:13:21 2026
Tag: v0.56.2, commits: 7661

Libraries:
Hyprgraphics: built against 0.5.1, system has 0.5.1
Hyprutils: built against 0.14.1, system has 0.14.2
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.8, system has 0.6.8
Aquamarine: built against 0.15.0, system has 0.15.0

Version ABI string: efb50993780079460b0cbed1363e2166a2de1d9f_aq_0.15_hu_0.14_hg_0.5_hc_0.1_hlg_0.6
no flags were set

I am in omarchy so this could be something with those configs, but here is my customizations:
https://github.com/joshuacox/stowfiles

Also when I throw stuff to another desktop e.g.
ctrl - super - 2 <-- chuck a window at desktop 2
the window I threw disappears and the other windows become inactive. Whereas it used to take my active window put it on 2 and switch me to 2 with it.

Anyone else seeing odd behavior?

Can't make test print on CUPS

dummy@example.com (nera) — Sat, 12 Sep 2026 13:19:24 +0000

Sorry my bad. It seems like cachyos and manjaro hadn't yet merged those changes in their repositories. Since when I tried updating, it says already up-to-date

[SOLVED] System freezes during boot with most recent firmware (AMD)

dummy@example.com (questionask) — Sat, 12 Sep 2026 11:09:38 +0000

Downgrading to linux-firmware-amdgpu 20260810-2 worked for me as well. I could change the kernel command line in GRUB and do it from a shell.

[SOLVED] kdeconnect and other apps crashing after switching to wayland

dummy@example.com (UnknownError) — Sat, 12 Sep 2026 10:49:02 +0000

Okay I think I solved it. My laptop is quite old and I used to start my plasma session via .xinitrc, so I still had the following there.

export DESKTOP_SESSION=plasma
exec startplasma-x11

This was run when I started my plasma session via sddm, so it started the x11 session. After removing these lines the wayland session would not start, but I have now switched to Plasma Login Manager and everything seems to work now.

Network issues with kernel 7

dummy@example.com (amhairghin) — Sat, 12 Sep 2026 10:21:47 +0000

The truth is, I can't tell you exactly which kernel version is causing the problem or why it's happening—I only know what the symptoms are and that it's clearly related to Kernel 7, which has been giving us a series of rather interesting “surprises” lately.

The thing is, I'm working away quietly on my computer (an AMD) when suddenly I lose my network connection—nothing responds at all. About a minute after it happens, if I go to the journal, I see this appear:

sep 12 12:06:46 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 14: transmit queue 0 timed out 5440 ms
sep 12 12:06:46 hell kernel: r8169 0000:0e:00.0 enp14s0: ASPM disabled on Tx timeout
sep 12 12:06:46 hell kernel: r8169 0000:0e:00.0 enp14s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
sep 12 12:06:52 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 14: transmit queue 0 timed out 5777 ms
sep 12 12:07:08 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5681 ms
sep 12 12:07:14 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 14: transmit queue 0 timed out 5399 ms
sep 12 12:07:20 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 11: transmit queue 0 timed out 5693 ms
sep 12 12:07:26 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 1: transmit queue 0 timed out 5492 ms
sep 12 12:07:26 hell kernel: r8169 0000:0e:00.0 enp14s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
sep 12 12:07:58 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 9: transmit queue 0 timed out 5784 ms
sep 12 12:07:58 hell kernel: r8169 0000:0e:00.0 enp14s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).

At that point, the only thing left for me to do is restart. There is (as far as I know) no way to recover the network.

This doesn't happen to me all the time; it's completely random. It might happen shortly after I start up the computer, or I might go days without it crashing. The only thing I know for sure is that this is a problem with Kernel version 7.

Anyway, I'm just leaving this here to let you know that if this happens to anyone else, you're not alone, my friend.

Request to Add arm-linux-gnueabihf-gcc Package

dummy@example.com (Lone_Wolf) — Sat, 12 Sep 2026 10:14:23 +0000

Please building/installing arm-linux-gnueabihf-gcc-stage1 .

System freezes while trying to sleep

dummy@example.com (Lone_Wolf) — Sat, 12 Sep 2026 10:04:22 +0000

Keep in mind that there are also reports of users that solved issues by using ntfs-3g instead of the kernel driver.

Moderator Note
Closing this old thread.

showtime crash with vulkan renderer

dummy@example.com (injiniero) — Sat, 12 Sep 2026 09:53:38 +0000

seth wrote:

looks sketchy (see the format value matching the width, might be bug or stack corruption)

This seems to be debugger noise.

I've updated the issue info after some new test: https://gitlab.gnome.org/GNOME/gtk/-/work_items/8333

Pointing to software decoded video between gsk and vulkan.

nvidia 615.71.09-1 seems to break on Wayland

dummy@example.com (marcs) — Sat, 12 Sep 2026 07:52:55 +0000

After upgrading to nvidia drivers version 615.71.09-1, both plasma-login-manager and gdm cannot load and I got a black screen. I tested sddm and it loads fine since it's on Xorg but fails to load any desktop environments that run on Wayland.
While trying to load a DE I got this message on dmesg, I don't know if related to the problem, might be:

ERROR: GPU:1: nvHandleCpEventDeferredWork: DisplayId 0x10000 Invalid

I rolled back to version 610.57.04 to get a functioning desktop environment.

Phone-to-USB-C connection failing

dummy@example.com (killertofus) — Sat, 12 Sep 2026 06:07:00 +0000

can you plug it into a usb port instead of a usbc port?

Snapper snapshots ok in @ / subvolume or not?

dummy@example.com (drucifer) — Sat, 12 Sep 2026 03:13:41 +0000

PhilArch33 wrote:

I did some research and apparently booting from a snapshot only boots in read only mode but it allows you to find the right snapshot before the system broke. There's a "rollback" command on the openSUSE systems but apparently in Arch you have to do it manually. Mount your desired snapshot temporarily and overwrite the root subvolume but like you, I'm going to wait until it happens to play around with this.

I have snapper, snap-pac, and grub-btrfs (available from btrfs-progs). Snapper does have a rollback command.

You boot into the snapshot from GRUB

Confirm it is the correct snapshot

Rollback with sudo snapper -c root rollback

That replaces your 0 snapshot (current) with the desired snapshot.

Then you can reboot the system and it will resume operations from the restored snapshot.

If you mean a literal "rollback" command, one could create an alias of the snapper command.