touch-packages team mailing list archive

[Launchpad Bug Tracker <1420601@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package systemd - 218-10ubuntu1

---------------
systemd (218-10ubuntu1) vivid; urgency=medium

  [ Martin Pitt ]
  * Merge with Debian unstable. 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.

  * ifup@.service: Fix syntax error. (LP: #1421556, #1420601)

  [ Didier Roche ]
  * Add systemd-fsckd multiplexer and feed its output to plymouth. This
    provides an aggregate progress report of running file system checks and
    also allows cancelling them with ^C.
    (LP: #1316796; Closes: #775093, #758902)

systemd (218-10) experimental; urgency=medium

  * Pull latest keymaps from upstream git. (LP: #1334968, #1409721)
  * rules: Fix by-path of mmc RPMB partitions and don't blkid them. Avoids
    kernel buffer I/O errors and timeouts. (LP: #1333140)
  * Clean up stale mounts when ejecting CD drives with the hardware eject
    button. (LP: #1168742)
  * Document systemctl --failed option. (Closes: #767267)
  * Quiesce confusing and irrelevant "failed to reset devices.list" warning.
    (LP: #1413193)
  * When booting with systemd-bootchart, default to run systemd rather than
    /sbin/init (which might not be systemd). (LP: #1417059)
  * boot-and-services autopkgtest: Add CgroupsTest to check cgroup
    creation/cleanup behaviour. This reproduces #777601 and verifies the fix
    for it.

systemd (218-9) experimental; urgency=medium

  [ Martin Pitt ]
  * debian/tests/logind: With dropped systemd-logind-launch we don't have a
    visible /sys/fs/cgroup/systemd/ any more under cgmanager. So adjust the
    test to check /proc/self/cgroup instead.
  * Add unit-config autopkgtest to check systemd unit/sysv init enabling and
    disabling via systemctl. This also reproduces #777613.
  * systemctl: Always install/enable/disable native units, even if there is a
    corresponding SysV script and we call update-rc.d; while the latter
    handles WantedBy=, it does not handle Alias=. (Closes: #777613)
  * cgroup: Don't trim cgroup trees created by someone else, just the ones
    that systemd itself created. This avoids cleaning up empty cgroups from
    e.g. LXC. (Closes: #777601)
  * Don't parse /etc/mtab for current mounts, but /proc/self/mountinfo. If the
    former is a file, it's most likely outdated on boot, leading to race
    conditions and unmounts during boot. (LP: #1419623)

  [ Michael Biebl ]
  * Explicitly disable the features we don't want to build for those with
    autodetection. This ensures reliable build results in dirty build
    environments.
  * Disable AppArmor support in the udeb build.
  * core: Don't fail to run services in --user instances if $HOME is missing.
    (Closes: #759320)

  [ Didier Roche ]
  * default-display-manager-generator: Avoid unnecessary /dev/null symlink and
    warning if there is no display-manager.service unit.

systemd (218-8) experimental; urgency=medium

  [ Martin Pitt ]
  * boot-and-services autopkgtest: Ensure that there are no failed units,
    except possibly systemd-modules-load.service (as that notoriously fails
    with cruft in /etc/modules).
  * Revert "input" system group creation in systemd.postinst from 218-7. It's
    already done in udev.postinst.
  * ifup@.service: Revert checking for existance of ifupdown config for that
    interface, net.agent already does that.
  * Drop Also-redirect-to-update-rc.d-when-not-using-.service.patch; not
    necessary any more with the current version (mangle_names() already takes
    care of this).
  * Merge into Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch:
    - Do-not-order-rcS.d-services-after-local-fs.target-if.patch, as it
      partially reverts the above, and is just fixing it.
    - Map-rcS.d-init-script-dependencies-to-their-systemd-.patch as it's just
      adding some missing functionality for the same purpose.
  * Merge Run-update-rc.d-defaults-before-update-rc.d-enable-d.patch into
    Make-systemctl-enable-disable-call-update-rc.d-for-s.patch as the former
    is fixing the latter and is not an independent change.
  * Drop Launch-logind-via-a-shell-wrapper.patch and systemd-logind-launch
    wrapper. The only remaining thing that we need from it is to create
    /run/systemd/, move that into the D-BUS service file directly.
  * /lib/lsb/init-functions.d/40-systemd: Avoid deadlocks during bootup and
    shutdown. DHCP/ifupdown and similar hooks which call "/etc/init.d/foo
    reload" can easily cause deadlocks, since the synchronous wait plus
    systemd's normal behaviour of transactionally processing all dependencies
    first easily causes dependency loops. Thus during boot/shutdown operate
    only on the unit and not on its dependencies, just like SysV behaves.
    (Closes: #777115, LP: #1417010)
  * Only start logind if dbus is installed. This fixes the noisy startup
    failure in environments without dbus, such as LXC containers or servers.
    (part of #772700)
  * Add getty-static.service unit which starts getty@.service on tty 2 to 6 if
    dbus is not installed, and hence logind cannot auto-start them on demand.
    (Closes: #772700)

  [ Michael Biebl ]
  * Update insserv-generator and map $x-display-manager to
    display-manager.service, following the recent change in sysv-generator.
    This avoids creating references to a no longer existing
    x-display-manager.target unit.
 -- Martin Pitt <martin.pitt@xxxxxxxxxx>   Fri, 13 Feb 2015 15:51:59 +0100

** Changed in: systemd (Ubuntu)
       Status: Incomplete => 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/1420601

Title:
  Systemd_218-6ubuntu1 and later cannot connect to network except via
  USB

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  
  systemd_218-6ubuntu1_amd64.deb   and later work ONLY with USB networking devices when booted from Dracut. Dracut network module is NOT in use, and binaries needed to connect to the network do not appear in my initramfs, yet systemd version loaded from it determines whether or not network can be connected. With an AMD Athlon II x4 machined and a Gigabyte AMD motherboard (785 series I think), I get the systemd networking unit entering a failed state, and the wired network cannot be turned on. On an Intel Atom Pine Trail netbook the wireless attempt to connect to the network but hangs on requesting an IP address from the router, never completing. Rolling back systemd to systemd_218-5ubuntu2_amd64.deb always fixes this and brings back normal network connectivity.  Finally, an AMD bulldozer machine connected by a USB wifi device has no trouble at all with the newer builds of systemd.

  systemd_218-5ubuntu2_amd64.deb , which came out Jan 23, seems to be
  the last good version. Same upstream version of systemd, apparently
  just build-time changes caused this.

  I'm not sure if this bug will appear with a normal Ubuntu initramfs-
  tools initramfs (I use Dracut with systemd in the initramfs), but I
  bring this up because my /boot partition is not normally mounted (so
  as not to corrupt a monitored hash value) and which version of systemd
  is in the initramfs, not the version on disk, determines whether or
  not networking functions on my machines.  I do understand my setup has
  diverged a lot from normal Ubuntu, someone should see if this problem
  exists in a normal Ubuntu install. If not I will need to find out what
  changed(possibly a udev rule?) and revert it myself in all later
  versions.

  I've been using systemd with dracut/systemd in the initramfs since
  last May, I now rely on it to run a parallelized version of my multi-
  encrypted disk unlocking program and am not about to revert it.
  Initramfs-tools seems to be unable to cope with multiple asynchrounous
  instances of cryptsetup, while dracut/systemd handles it just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1420601/+subscriptions