Service: Group name with whitespace not working anymore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
On Ubuntu 16.04.x, I have a perfectly working custom systemd service file which sets username and group for the service as
[Service]
User=user
Group=domain users
where both group and user come from an AD domain joined to with winbind.
This is not working anymore on 18.04. Even with the group name quoted, or mangled with systemd-escape. The service doesn't start with one of the following messages in the journal (depending on how it's spelled):
/lib/systemd/
/lib/systemd/
/lib/systemd/
/lib/systemd/
The only thing that works is to use the GID instead of the group name.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.12
ProcVersionSign
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Feb 14 12:58:59 2019
InstallationDate: Installed on 2019-01-28 (16 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-
LC_COLLATE=C
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: VMware Virtual Platform
dmi.product.
dmi.sys.vendor: VMware, Inc.
Changed in systemd (Ubuntu): | |
status: | New → Confirmed |
please reopen if this is still an issue