Ah, I thought this would happen if there already was a tmp.mount in
systemd's brain (e. g. from a manual mount or fstab) and then adding the
unit to /etc would cause that. But indeed I cannot reproduce this
either.
So, Sworddragon, please do the steps in comment #1.
** Changed in: systemd (Ubuntu)
Status: Fix Committed => 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 : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
