This bug was fixed in the package systemd - 219-4ubuntu1
---------------
systemd (219-4ubuntu1) vivid; urgency=medium
* Merge with Debian experimental. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
support udev, no debconf).
- initramfs init-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.
- initramfs init-bottom: If LVM is installed, settle udev,
otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
dependencies to "lvm2" which is handled with udev rules in Ubuntu.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/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) Also, check if devices are actually defined
in /etc/network/interfaces as we don't use Debian's net.agent.
- ifup@.service: Drop dependency on networking.service (i. e.
/etc/init.d/networking), and merely ensure that /run/network exists.
This avoids unnecessary dependencies/waiting during boot and dependency
cycles if hooks wait for other interfaces to come up (like ifenslave
with bonding interfaces). (LP: #1414544)
- 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)
- Lower Breaks: to plymouth version which has the udev inotify fix in
Ubuntu.
- Lower libappamor1 dep to the Ubuntu version where it moved to /lib.
- 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.
- Clean up obsolete /etc/udev/rules.d/README.
systemd (219-4) experimental; urgency=medium
* tmpfiles: Avoid creating duplicate ACL entries. Add postinst code to clean
them up on upgrade. (Closes: #778656)
* bootchart: Fix path to default init. (LP: #1423867)
* Add "bootchart" autopkgtest, to spot regressions like the above.
* autopkgtests: Factorize out "assert.sh" utility functions, and use them in
the tests for useful failure messages.
* Downgrade requirement for timedated, hostnamed, localed-locale, and
logind autopkgtests from machine to container isolation.
* boot-and-services and display-manager autopkgtest: Add systemd-sysv as
proper test dependency instead of apt-get installing it. This works now
also under Ubuntu 15.04.
* boot-and-services autopkgtest: Check cleanup of temporary files during
boot. Reproduces #779169.
* Clean up /tmp/ directory again. (Closes: #779169, LP: #1424992)
-- Martin Pitt <martin.p...@ubuntu.com> Fri, 27 Feb 2015 08:48:16 +0100
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1423867
Title:
init=/lib/systemd/systemd-bootchart on 219 triggers a kernel panic on
kvm
Status in systemd package in Ubuntu:
Fix Released
Bug description:
if setting init=/lib/systemd/systemd-bootchart, this one doesn't
reexecute systemd as expected:
opening output file '/run/log/bootchart-<timestamp>': No such file or
directory
opening output file '/run/log/bootchart-<timestamp>': No such file or
directory
and then, triggers a kernel panic.
Had to use init='/lib/systemd/systemd-bootchart -i
/lib/systemd/systemd' to get it booting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423867/+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
