@slashd, this seems to be an issue that should be solved in Debian and
then pulled into the development release for Ubuntu, but it doesn't seem
like something that needs to be SRUed, right? I'm going to mark the SRU
releases wontfix, but if that's incorrect please do feel free to open it
back up for sru
** Changed in: systemd (Ubuntu Bionic)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Focal)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Groovy)
Status: New => Won't Fix
** Also affects: systemd (Ubuntu Impish)
Importance: Wishlist
Status: New
** Changed in: systemd (Ubuntu Hirsute)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1915936
Title:
systemd-coredump user is created by something other than its derived
systemd packages
Status in systemd package in Ubuntu:
New
Status in systemd source package in Bionic:
Won't Fix
Status in systemd source package in Focal:
Won't Fix
Status in systemd source package in Groovy:
Won't Fix
Status in systemd source package in Hirsute:
Won't Fix
Status in systemd source package in Impish:
New
Status in systemd package in Debian:
New
Bug description:
systemd-coredump binary package is instructed as follows:
#debian/systemd-coredump.postinst:
adduser --quiet --system --group --no-create-home --home /run/systemd \
--gecos "systemd Core Dumper" systemd-coredump
But one doesn't need this package to be installed to have the systemd-
coredump user created. This was taken from a focal 20.04.2 fresh
installation (Right after a vanilla installation):
# cat /etc/passwd:
...
systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
...
# dpkg -l | grep -i systemd
ii dbus-user-session 1.12.16-2ubuntu2.1
amd64 simple interprocess messaging system (systemd --user integration)
ii libnss-systemd:amd64 245.4-4ubuntu3.4
amd64 nss module providing dynamic user and group name resolution
ii libpam-systemd:amd64 245.4-4ubuntu3.4
amd64 system and service manager - PAM module
ii libsystemd0:amd64 245.4-4ubuntu3.4
amd64 systemd utility library
ii networkd-dispatcher 2.0.1-1
all Dispatcher service for systemd-networkd connection status changes
ii python3-systemd 234-3build2
amd64 Python 3 bindings for systemd
ii systemd 245.4-4ubuntu3.4
amd64 system and service manager
ii systemd-sysv 245.4-4ubuntu3.4
amd64 system and service manager - SysV links
ii systemd-timesyncd 245.4-4ubuntu3.4
amd64 minimalistic service to synchronize local time with NTP servers
# /var/log/syslog
syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group
systemd-coredump with gid 999.
syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.
Additionnally, you may notice the home directory during the user creation at
installation sets it to "/" as opposed to "/run/systemd" directive in the
appropriate postint. It is contradictory.
* Why systemd-coredump user is created at installation time and/or without
'systemd-coredump' package installed ?
* Why this early creation set the home directory to "/" ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
