This bug was fixed in the package systemd - 218-3ubuntu1
---------------
systemd (218-3ubuntu1) vivid; urgency=medium
* Merge with Debian unstable. Remaining Ubuntu changes:
- Create disk/by-partlabel links for mmcblk partitions.
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
- Don't install 80-networking.rules and the Debian *.agent scripts, we
never supported them in Ubuntu. Instead, extend systemd's "net" device
udev rule to trigger ifup@.service on network devices.
- Keep our much simpler udev maintainer scripts (all platforms must
support udev, no debconf).
- debian/extra/initramfs.top: Drop $ROOTDELAY, we do that in a more
sensible way with wait-for-root. Will get applicable to Debian once
Debian gets wait-for-root in initramfs-tools.
- debian/extra/initramfs.bottom: If LVM is installed, settle udev,
otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add 40-hyperv-hotadd.rules: Workaround for LP #1233466.
- Mark graphics devices as PRIMARY_DEVICE_FOR_DISPLAY so that we can wait
for those in plymouth.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
dependencies to "lvm2" which is handled with udev rules in Ubuntu.
- Add HP ProLiant Server Cartridge power control support.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/ifup@.service: Additionally run for "auto" class. We don't really
support "allow-hotplug" in Ubuntu at the moment, so we need to deal with
"auto" devices appearing after "/etc/init.d/networking start" already
ran. (LP: #1374521)
- Lower Breaks: to plymouth version which has the udev inotify fix in
Ubuntu.
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
Ubuntu we currently keep the setting whether the RTC is in local or UTC
time in /etc/default/rcS "UTC=yes|no", instead of /etc/adjtime.
(LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
user LXC containers work under systemd. (LP: #1346734)
- Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
This currently fails when being triggered by Jenkins, but is totally
unreproducible when running this manually on the exact same machine.
Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
systemd (218-3) experimental; urgency=medium
* build-logind autopkgtest: Re-enforce that sd_login_monitor_new() succeeds,
and restrict this test to isolation-container. (Reproduces LP #1400203)
* Bring back patch to make sd_login_monitor_new() work under other init
systems where /sys/fs/cgroup/systemd/machine does not exist.
(LP: #1400203)
* build-login autopkgtest: Build against libsystemd, not libsystemd-login
any more.
* Add debian/extra/systemd-vconsole-setup.service dependency shim for
the console-setup init script, to avoid breaking dependencies of
third-party packages. Install it for Ubuntu only for now, as in Debian
plymouth's unit got adjusted. (LP: #1392970, Debian #755194)
* Mark systemd{,-sysv} as M-A: foreign (thanks lintian).
* Quiesce maintainer-script-calls-systemctl lintian warning.
* Quiesce possibly-insecure-handling-of-tmp-files lintian warning, it's
wrong there (we are handling tmpfiles.d/ files which are not in a temp
dir).
* Use dh_installinit's --noscript instead of --no-start for the upstart
jobs without sysvinit scripts (thanks lintian).
* Put systemd.pc into arch specific pkgconfig dir, as it contains the arch
specific libdir value.
* Don't enable audit by default. It causes flooding of dmesg and syslog,
suppressing actually important messages. (Closes: #773528)
* Cherrypick various bug fixes in loopback device setup and netlink socket
communication. Fixes massive CPU usage due to tight retry loops in user
LXC containers.
-- Martin Pitt <martin.p...@ubuntu.com> Tue, 30 Dec 2014 21:28:23 +0100
** Changed in: systemd (Ubuntu Vivid)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392970
Title:
systemd[1]: Cannot add dependency job for unit systemd-vconsole-
setup.service, ignoring: Unit systemd-vconsole-setup.service failed to
load: No such file or directory.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392970/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
