# systemctl is-enabled tmp.mount ; echo $?
Failed to get unit file state for tmp.mount: No such file or directory
0
Ouch, so systemctl exiting successfully (with 0) for a nonexisting
tmp.mount is indeed bad, and would cause this bug. dino99 correctly gets
an "1" there, so dino99 and Sworddragon do *not* experience the same bug
here. As Sworddragon reported this, let's concentrate on this issue now.
Sworddragon, can you please look for any tmp.mount units you may have
around, with
find /{etc,lib,run}/systemd -name tmp.mount | xargs ls -l
?
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
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/1545707
Title:
Error message "Operation failed: No such file or directory" on
installing/reconfiguring systemd
Status in systemd package in Ubuntu:
Incomplete
Bug description:
I'm using Ubuntu 16.04 dev with systemd 229-1ubuntu2 and on
installing/reconfiguring it I'm getting this output (the first error
has already its own bug report here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094 ):
root@ubuntu:~# dpkg-reconfigure systemd
addgroup: The group `systemd-journal' already exists as a system group.
Exiting.
Operation failed: No such file or directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545707/+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
