Your message dated Wed, 26 Jan 2022 17:36:03 +0100
with message-id <9d1acdcb30fbc80a975eba2e799ae551f39a63dd.ca...@43-1.org>
and subject line Re: Bug#1004392: systemd: Incorrect location of configuration
files
has caused the Debian Bug report #1004392,
regarding systemd: Incorrect location of configuration files
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1004392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 247.3-6
Severity: serious
Justification: Policy 10.7
Dear Maintainer,
/usr/lib/tmpfiles.d/x11.conf should be a configuration file. Entries in it must
be disabled in order to run containers with accelerated X11 and DRI access.
As it is under lib, changes to it are overwritten on every systemd update
breaking all containers which run X apps with direct access to local X-server.
1. There is no way to disable it permanently.
2. There is no way to override it in a way which disables the defaults
Actually, most of that directory does not belong in /usr - it should be under
/etc as per Debian policy for configuration files and should be handled as
config on
system upgrades and updates.
-- Package-specific info:
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-10
ii libapparmor1 2.13.6-10
ii libaudit1 1:3.0-2
ii libblkid1 2.36.1-8
ii libc6 2.31-13+deb11u2
ii libcap2 1:2.44-1
ii libcrypt1 1:4.4.18-4
ii libcryptsetup12 2:2.3.5-1
ii libgcrypt20 1.8.7-6
ii libgnutls30 3.7.1-5
ii libgpg-error0 1.38-2
ii libip4tc2 1.8.7-1
ii libkmod2 28-1
ii liblz4-1 1.9.3-2
ii liblzma5 5.2.5-2
ii libmount1 2.36.1-8
ii libpam0g 1.4.0-9+deb11u1
ii libseccomp2 2.5.1-1+deb11u1
ii libselinux1 3.1-3
ii libsystemd0 247.3-6
ii libzstd1 1.4.8+dfsg-2.1
ii mount 2.36.1-8
ii ntp [time-daemon] 1:4.2.8p15+dfsg-1
ii util-linux 2.36.1-8
Versions of packages systemd recommends:
ii dbus 1.12.20-2
Versions of packages systemd suggests:
ii policykit-1 0.105-31
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.140
ii libnss-systemd 247.3-6
ii libpam-systemd 247.3-6
ii udev 247.3-6
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
KillUserProcesses=yes
KillExcludeUsers=root
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 2022-01-26 at 15:41 +0000, Anton Ivanov wrote:
> /usr/lib/tmpfiles.d/x11.conf should be a configuration file. Entries
> in it must be disabled in order to run containers with accelerated
> X11 and DRI access.
>
> As it is under lib, changes to it are overwritten on every systemd
> update breaking all containers which run X apps with direct access to
> local X-server.
>
> 1. There is no way to disable it permanently.
> 2. There is no way to override it in a way which disables the
> defaults
The files in /usr can be overriden with files in /etc. See the section
"CONFIGURATION DIRECTORIES AND PRECEDENCE" in man:tmpfiles.d(5).
(It works the same for most of systemd.)
Ansgar
--- End Message ---
