This isn't reproducible in yakkety, but it does reproduce locally in a
QEMU xenial instance (although a lot harder than on the infra, which is
why I didn't see it at first). It seems systemd 229's systemd-networkd-
wait-online has a bug that it does not actually wait for the interfaces
to be fully
http://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#network-manager and
http://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#systemd tests look fine, but
http://autopkgtest.ubuntu.com/packages/n/nplan/xenial/amd64 fails
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-16.10 => ubuntu-16.11
--
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/1624071
Title:
libnss-resolve: Fallback from
You need to install the new libpam-systemd as well at least; there could
be more binaries of the systemd source that you have installed. Check
with "dpkg -l | grep ^.i.*229-4"
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because
http://autopkgtest.ubuntu.com/packages/n/network-manager succeeds again
on xenial, thus verified.
** Tags removed: verification-done-precise verification-done-trusty
verification-done-xenial verification-done-yakkety verification-needed
** Tags added: verification-done
--
You received this bug
Cherry-picked into xenial branch.
** Changed in: network-manager (Ubuntu Xenial)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** Changed in: nplan (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1627641
Title:
Backport netplan to
Hello Louis, or anyone else affected,
Accepted apt into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.15 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for network-manager has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for network-manager has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
) breaks multipath-tools
tests
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in:
This is the log from a manual test run, with "nova console-log" at the
end. This is a bit curious -- the instance does seem to get an IP via
DHCP, but sshing to it says "no route to host". Unfortunately my only
"foot into the door" without ssh is console-log, which is read-only.
Public bug reported:
https://launchpad.net/ubuntu/+source/initramfs-tools/0.125ubuntu4
reliably breaks multipath-tools' autopkgtests on the infrastructure. The
instances don't reboot after test setup, thus cause a "tempfail", and
are being retried infinitely.
This does not reproduce with QEMU
The verification of the Stable Release Update for isc-dhcp has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
** Changed in: systemd (Ubuntu Xenial)
Importance: High => Wishlist
** Changed in: systemd (Ubuntu Xenial)
Importance: Wishlist => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
For snappy (at first at least) we need to provide netplan in xenial, as
for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read
configuration and connections from /run/NetworkManager/.
** Description changed:
For snappy (at first at least) we need to provide netplan in xenial, as
for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read
configuration and connections from /run/NetworkManager/.
nassigned) => Martin Pitt (pitti)
--
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/1627641
Title:
Backport netplan to xenial
Status in network-manager package in Ubuntu:
With the backported nplan one test case fails:
==
FAIL: test_manual_addresses (__main__.TestNetworkd)
--
Traceback (most recent call last):
File
** Description changed:
For snappy (at first at least) we need to provide netplan in xenial, as
for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read
configuration and connections from /run/NetworkManager/.
Status: Fix Released
** Affects: network-manager (Ubuntu Xenial)
Importance: Wishlist
Assignee: Martin Pitt (pitti)
Status: Triaged
** Affects: nplan (Ubuntu Xenial)
Importance: Wishlist
Assignee: Martin Pitt (pitti)
Status: Triaged
** Also affects: net
md (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch see
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1626737
Title:
[4.8.0-14/ppc64el regression]
On the u-s-d side there is some potential optimization: Ideally the
brightness would always be set through xrandr XBACKLIGHT, which works
unprivileged, and only fall back to the helper if that is not available
and the brightness needs to be set via sysfs properties. However, even
then there is no
Changing tasks as this is somewhere between unity-settings-daemon and
polkit.
** Package changed: linux (Ubuntu) => unity-settings-daemon (Ubuntu)
** Changed in: unity-settings-daemon (Ubuntu)
Status: Incomplete => Triaged
** Package changed: systemd (Ubuntu) => policykit-1 (Ubuntu)
**
I just dist-upgraded again, and with 4.8.0-14 my brightness keys work
again (bug 1626429). Under i3 (no unity-settings-daemon), I get a tame
and immediate reaction:
UDEV [38372.886325] change
/devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight)
ACTION=change
Oh, forgot: for evtest you might need to try with several devices, such
as "ThinkPad Extra Buttons" and the actual keyboard.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This looks like one keypress would cause a massive spew of uevents
and/or evdev events. Can you please run "sudo evtest" and "udevadm
monitor -e", then press a brightness key once, then ^C both and
copy the output?
I don't get this on my ThinkPad X230, I have the opposite problem
(brightness
http://autopkgtest.ubuntu.com/packages/s/systemd/yakkety/ppc64el passed
a few times again, and that tmpfiles crash never reproduced.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu)
Status: Fix Released => Invalid
--
You received
This was fixed in -14, scsi_debug is back.
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1625100
Fixed: https://git.launchpad.net/~network-manager/network-
manager/+git/ubuntu/commit/?id=5fbc4bdf5dd
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
t; In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1626568
Title:
Public bug reported:
The two rfkill tests now fail in yakkety since linux got upgraded to 4.8, like
in in
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/n/network-manager/20160922_091844@/log.gz
.
It still builds fine:
New => Fix Committed
** Changed in: network-manager (Ubuntu Yakkety)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: network-manager (Ubuntu Xenial)
Status: New => Triaged
** Changed in: network-manager (Ubuntu Trusty)
Status: New => Triaged
--
You re
Talked to Andy on IRC, and dropping these drivers was not intended. I
agree we should keep the most common ones built in, especially for cloud
instances; there it would really be beneficial to drop initrds
completely (see bug 1592684), as they are just bloat there.
** Changed in: systemd (Ubuntu)
> This only happens on amd64, i386 and ppc64el are fine.
FTR, this is because we run the qemu tests only on amd64. i386 also has
CONFIG_ATA=m now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This is the first test that boots the root disk without an initrd.
Indeed booting it with debug shows that the kernel detects no hard disks
then (in particular not /dev/sda1), thus the boot fails like that.
With 4.4, or with 4.8 and booting with an initrd it detects the sda hard
drive again:
[
: Undecided
Status: Confirmed
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: In Progress
** Tags: bot-stop-nagging
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu
I cannot recreate this on yakkety, there lvm2-lvmetad.socket starts up
just fine right after package installation. Can you confirm?
** Changed in: lvm2 (Ubuntu)
Status: Triaged => Fix Released
** Changed in: lvm2 (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug
Indeed the generated /var/lib/dpkg/info/lvm2.postinst does not start
lvm2-lvmetad.socket at all, even though debian/rules calls
dh_systemd_start --restart-after-upgrade \
lvm2-lvmetad.service \
lvm2-lvmpolld.service
dh_systemd_start --no-restart-on-upgrade \
Low-risk, approved.
** Changed in: account-plugins (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1587282
Title:
create
** Changed in: wpa (Ubuntu Wily)
Status: Fix Committed => Triaged
** Changed in: wpa (Ubuntu Wily)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
** Description changed:
libnss-{resolve,mymachines,myhostname} automatically add/remove
themselves from /etc/nsswitch.conf on installation/removal.
But when (manually) adding NSS action specifiers, these do not
** Description changed:
libnss-{resolve,mymachines,myhostname} automatically add/remove
themselves from /etc/nsswitch.conf on installation/removal.
But when (manually) adding NSS action specifiers, these do not get
removed along.
TEST CASE:
- * Install libnss-machines. This will
dns")
and modifying to "files resolve [!UNAVAIL=return] dns [foo=bar]", then purge
libnss-resolve again -- this should again remove the [!UNAVAIL=return] but
*NOT* "dns [foo=bar]".
** Affects: systemd (Ubuntu)
Importance: Medium
Assignee: Martin Pitt (pitti)
Cherry-picked into Xenial branch: https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu-xenial=72bc2062
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Thanks for the followup. Closing the debian-installer part now. The work
on the Debian side wrt. multiplexing the installer UI to mutiple
consoles sounds interesting, but I don't think we should houd our breath
for it -- I think this is going to be tricky given how different the
capabilities of VT
I believe this is fixed by https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=be10d22 . We should also SRU this fix.
** Summary changed:
- systemd does not allow fsck to finish on ubuntu 15.10
+ systemd does not allow fsck to finish
** Bug watch added: Debian Bug tracker
** Package changed: systemd (Ubuntu) => zfs-linux (Ubuntu)
--
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/1624844
Title:
Ubuntu 16.04 breaks boot with wrong zpool.cache
*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757
** This bug has been marked a duplicate of bug 1407757
multi-arch packages cannot be installed due to dpkg wrongly detecting them
as already installed
--
You received this bug notification because you
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
FTR, I ran the full boot-and-services test against the current PPA which
has kernel -11.12 and could not reproduce the crash. Could it be that
this was a regression in -10.11 (the test runs in the description) which
got fixed in -11.12 again?
So the only concrete thing here that I can see is the
> [kernel oops] This does everytime, though.
This was supposed to mean: This does *not happen* every time.
--
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/1625100
Title:
I tried to reproduce the full boot-and-services test log on
scalingstack, and upon rebooting into the 4.8 kernel I got the attached
kernel oops. This does everytime, though.
** Attachment added: "4.8/ppc64el kernel crash log"
** Summary changed:
- systemd 231-6 ADT test failure with linux 4.8.0-11.12
+ systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el,
systemd-tmpfiles crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
gpiccoli, great finding! Indeed it seems debian-installer interprets
console= arguments and prefers the *last* one:
rootskel-1.115ubuntu1/src/sbin/reopen-console-linux:
if [ -z "$console" ]; then
# Locate the last enabled console present on the command line
That d-i behaviour agrees with how the kernel interprets those:
https://www.kernel.org/doc/Documentation/serial-console.txt -- i. e.
kernel messages appear on all "console="s, but the last one defines what
/dev/console points to.
--
You received this bug notification because you are a member of
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1625100
Title:
systemd 231-6 ADT test failure
> I'll make it dynamically enabled
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=19e67c70
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
With https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=94a70093 it uses powersave on
intel_pstate again, like in xenial.
> pitti, can we please have a config option to disable "ondemand"?
Indeed, right now it is statically enabled, so it can only be disabled
with "systemctl
amd64 failed in "upstream" tests during image preparation:
The file /dev/loop4p1 does not exist and no size was specified.
F: Failed to mkfs -t ext3
This might be just a rare race condition (I've never seen it). Does it
reproduce on retry?
ppc64el:
- One failure is due to
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=614740914
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thanks Doug! Ack, I'll change it to use "powersave" again then.
** Changed in: systemd (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
Sworddragon [2016-09-19 6:52 -]:
> But causing some output for example with echo in /etc/rc.local causes it
> to be written on the console on booting. Or is this the expected
> behavior even if the journal is used?
It's what "journal+console" does, yes -- it's similar to "tee".
--
You
The upstream issue actually applies to both. IMHO, if you restrict a DNS
server to a particular list of domains it should be used *exactly* for
the given domains (only). Querying it for other domains is a privacy
leak, and querying other name servers for those domains is most probably
going to
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
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/1624965
Title:
console respawn is sometimes slow and
$TERM only gets set for units which have Standard{Output,Error}=tty. By
default services only have a stdout/err pipe to the journal, and rc-
local.service uses journal+console which is still a pipe. So it would be
actively wrong to set $TERM there as it is not actually a terminal. (See
man
Does not reproduce with local QEMU, and does not reproduce any more in
production environment -- I fixed the long reboot issue yesterday,
perhaps that caused it. Retried a test run.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The primary purpose of adding 127.0.0.53 to resolv.conf is for client
software that wants to do DNS resolution by itself instead of using NSS
-- most notable example is Google Chrome, and third-party software which
is statically linked (e. g. Go).
However, other software like NetworkManager or
> The preferred governor with the intel_pstate driver is powersave.
Do you have some references/proof for that? This is contrary to what
kernel developers say, see comment 1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This matches https://github.com/systemd/systemd/issues/3421 very closely
(I've worked on this a bit, but it got stalled, sorry). I think that is
the exact symptom you are seeing, can you confirm?
** Bug watch added: github.com/systemd/systemd/issues #3421
outh-start'))
AssertionError: False is not true
Same assertion failure on some other systemd-fsckd tests.
** Affects: systemd (Ubuntu)
Importance: High
Assignee: Martin Pitt (pitti)
Status: In Progress
** Tags: autopkgtest yakkety
** Tags added: autopkgtest yakkety
** Changed i
** Changed in: gnome-session (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: gnome-session (Ubuntu)
Status: Won't Fix => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
** Changed in: upstart (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1618886
Title:
unity-gtk-module.service is
start (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1618886
Title:
unity-gtk-module.service is racy; session ser
** Tags added: bootspeed regression-release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1622893
Title:
NetworkManager takes very long to start, or times out,
Upstream PR sent with a possible fix:
https://github.com/systemd/systemd/pull/4164
With that "resolve [!UNAVAIL=return] dns" does the right thing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4157
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** C
Thanks for reporting this, well spotted!
The reason for having "dns" is *not* to guard against failures of
resolved -- if the daemon is not running, then nss-resolve already falls
back to glibc's resolver (i. e. "dns").
The reason is that libnss-resolve itself might not be available. E. g.
you
Hello Scott, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.8-1-g3705bb5-0ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
I uploaded that init-system-helpers fix to
https://launchpad.net/~pitti/+archive/ubuntu/systemd . Once that gets
uploaded to -proposed, I will add a versioned Breaks: to the new systemd
binary.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
Rationale: For backporting snapd to 14.04 LTS, we need to provide
systemd's service manager (not just logind and auxiliary services like
logind or timesyncd). upstart will continue to do the actual booting,
and systemd will act as a "deputy init" which by default
signee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1616422
Title:
[trusty SRU/FFE] Add systemd binary package for snap
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
** Changed in: init-system-helpers (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
in cloud-init users can install packages via cloud-config:
#cloud-config
packages: [apache2]
Due to some intricacies of systemd and service installation that doesn't work
all that well.
We fixed the issue for simple services that do not have any dependencies
I just filed bug 1623868 which is fallout from this change, so blocking
this SRU for now.
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Please file bugs with ubuntu-bug; there should already be a crash report
with the apt, dmesg, and other interesting logs.
This is most likely due to a corrupted file system or RAM; it could be a
bug in dpkg (although very unlikely). Can you reproduce this after a
clean boot and "sudo apt-get -f
Committed to master branch: https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=72a90870
Cherry-picked into xenial branch for next SRU round:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-xenial=f79508898
** Changed in: systemd (Ubuntu Xenial)
Interesting observation, thanks! I cannot confirm that the single line
is generally broken -- I've tested it on two different computers
(although only amd64) and it works fine. However, there is no harm in
splitting the rule, so I'll do that for the next SRU if it helps things.
--
You received
Hello Matthias, or anyone else affected,
Accepted python3.5 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.5/3.5.2-2~16.04 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: bootspeed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1581801
Title:
UUID base RESUME always wait 5 seconds for activating LVM swap
Status in
As I said I cannot test this patch on a current kernel really as it
works just fine with IPv6 disabled. Please test this, and if it works
for you I can send this upstream and SRU.
** Patch added: "proposed patch"
> an empty IFLA_AF_SPEC seems to cause the kernel to return EINVAL
This only seems to happen on older kernels. I tried it on 4.4 and an
empty container works fine. In particular, I made
socket_ipv6_is_supported() always return false, and now networkd only
configures IPv4 on my interface without
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Does that kernel support IPv6, i. e. does socket_ipv6_is_supported()
succeed and the whole AF_INET6 setup is actually done?
I. e. is the problem the mere existence of the IFLA_AF_SPEC container in
the netlink message (which already isn't supported by the kernel) or
only trying to set the IPv6
init-system-helpers is still sitting in the SRU queue and needs to be
reviewed/accepted.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1576692
Title:
fully
** Changed in: pm-utils (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1548392
Title:
Fix for 1172692 fa
401 - 500 of 4015 matches
Mail list logo
