Package: uucp Version: 1.07-30 Followup-For: Bug #1110981 I can confirm this bug. It has caused significant communication breakdown as suddenly all my outbound mails were no longer transported due to the lack of permission to create the lock file.
Changing the group of /run/lock to "uucp" and adding g+w permissions works as a work-around, but given that /run/lock is RAM only, this is non-persistent and needs to happen after every boot. -- System Information: Debian Release: forky/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.38+deb13-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages uucp depends on: ii bsd-mailx [mailx] 8.1.2-0.20220412cvs-1.1 ii cron [cron-daemon] 3.0pl1-197 ii libc6 2.41-12 ii libpam-runtime 1.7.0-5 ii libpam0g 1.7.0-5 ii netbase 6.5 Versions of packages uucp recommends: ii cu 1.07-30 ii exim4 4.98.2-2 ii inetutils-inetd [inet-superserver] 2:2.6-4 ii logrotate 3.22.0-1 uucp suggests no packages. -- Configuration Files: /etc/uucp/call changed [not included] /etc/uucp/dial changed [not included] /etc/uucp/passwd changed [not included] /etc/uucp/port changed [not included] -- no debconf information
