On Desktop, a container that asks for unlimited locked memory now gets it. 26.11.1 removed
systemd's 8 MiB DefaultLimitMEMLOCK so GPU containers could run with --ulimit memlock=-1, and
on a hybrid laptop running 26.11.2 that still failed. PipeWire's
/etc/security/limits.d/25-pw-rlimits.conf sets @pipewire - memlock 4194304 (4 GiB, soft and
hard), and every Desktop user is in the pipewire group, so pam_limits capped each login at 4 GiB
and --ulimit memlock=-1 was answered with 4 GiB. An ROCm container on an AMD APU then could not
map the device memory that 26.11.1 had just made available. The fix is one file that sorts after
PipeWire's: /etc/security/limits.d/60-pengyos-memlock.conf, containing @pipewire - memlock
unlimited. pam_limits reads limits.d in name order and a later entry for the same group
replaces an earlier one, so this restores "no limit" and leaves PipeWire's rtprio and nice
lines alone. Locked memory still counts against a cgroup's MemoryMax=, and Server has no
PipeWire, so Server was never affected.
uv and uvx 0.13.7 are in the Server and Desktop images, in /usr/bin, built from source
with the self-update feature off, which is what upstream asks distributions to do: updates come
with the image. The one-venv-per-app recipe now runs against the host's own python3. Before
this, uv existed only in the dev guest's ~/.local/bin, which is not on the host's PATH.
The invisible part is in sysconfig. The host Python reported its compiler as
/data/build/.../host/bin/x86_64-buildroot-linux-gnu-gcc, a path on our build machine, so any
install that needed to compile died with "No such file or directory" and never reached the stubs
that explain where a compiler is. external.mk now strips the prefix, leaving gcc, g++ and
gcc-ar, and Server's post-build.sh refuses to publish an image that still carries the old
path. A package that must compile is built as a wheel in the dev guest and installed with
--find-links:
dx uvx --python 3.14 pip wheel --no-deps -w ~/wheels PKG==VERSION
uv pip install --find-links ~/wheels PKG
That path was proven on a ThinkPad running 26.11.1, installing netifaces from its sdist plus a local
C extension. The nightly change in this batch was oo7 0.7.0.beta to 0.7.0, the Secret Service
daemon behind the COSMIC keyring. 0.6.0 ignored the password given to it when no keyring existed
and created a locked, passwordless Login keyring, and COSMIC has no prompter to unlock one: 0.7
creates Login with that password. Desktop and Desktop NVIDIA were rebuilt and boot-checked, and
the checks that changed in this window are scripts/tests/test_amd_gpu_compute.py,
test_host_uv.py and test_pengyos_txt.py.