The update doesn't seem to have fixed the SIGTRAP error; looking at https://fedoraproject.org/wiki/Changes/Reserve_resources_for_active_user_WS it seems some of the sysfs endpoints must now be obsolete? for instance /sys/fs/cgroup/user.slice/memory.low could potentially now be in /sys/fs/cgroup/memory/user.slice/memory.* though there is no obvious equivalent of memory.low among the alternatives

Hmm, if /sys/fs/cgroup/memory/user.slice/memory.* sounds like a cgroupv1 path. I didn't think that Fedora supports that at this point. Or am I missing something?

$ ls -al /sys/fs/cgroup/memory/user.slice/
total 0
drwxr-xr-x.  3 root root 0 Jun 14 08:45 .
dr-xr-xr-x. 12 root root 0 Jun 14  2022 ..
-rw-r--r--.  1 root root 0 Jun 14 09:05 cgroup.clone_children
--w--w--w-.  1 root root 0 Jun 14 09:05 cgroup.event_control
-rw-r--r--.  1 root root 0 Jun 14 09:05 cgroup.procs
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.failcnt
--w-------.  1 root root 0 Jun 14 09:05 memory.force_empty
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.kmem.failcnt
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.kmem.limit_in_bytes
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.kmem.max_usage_in_bytes
-r--r--r--.  1 root root 0 Jun 14 09:05 memory.kmem.slabinfo
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.kmem.tcp.failcnt
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.kmem.tcp.limit_in_bytes
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.kmem.tcp.max_usage_in_bytes
-r--r--r--.  1 root root 0 Jun 14 09:05 memory.kmem.tcp.usage_in_bytes
-r--r--r--.  1 root root 0 Jun 14 09:05 memory.kmem.usage_in_bytes
-rw-r--r--.  1 root root 0 Jun 14 08:45 memory.limit_in_bytes
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.max_usage_in_bytes
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.memsw.failcnt
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.memsw.limit_in_bytes
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.memsw.max_usage_in_bytes
-r--r--r--.  1 root root 0 Jun 14 09:05 memory.memsw.usage_in_bytes
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.move_charge_at_immigrate
-r--r--r--.  1 root root 0 Jun 14 09:05 memory.numa_stat
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.oom_control
----------.  1 root root 0 Jun 14 09:05 memory.pressure_level
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.soft_limit_in_bytes
-r--r--r--.  1 root root 0 Jun 14 09:05 memory.stat
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.swappiness
-r--r--r--.  1 root root 0 Jun 14 09:05 memory.usage_in_bytes
-rw-r--r--.  1 root root 0 Jun 14 09:05 memory.use_hierarchy
-rw-r--r--.  1 root root 0 Jun 14 09:05 notify_on_release
-rw-r--r--.  1 root root 0 Jun 14 09:05 tasks
drwxr-xr-x.  4 root root 0 Jun 14 08:46 user-1000.slice

You're right though, as I found systemd.unified_cgroup_hierarchy=0 in my cmdline that maybe I have to blame docker for. uresourced maybe should handle it more gracefully though, well at least you know what to add for testing now :-)

No issues found.