Thank you for reporting this issue and helping to improve Ubuntu.
This bug was reported against the version of systemd in Ubuntu 16.10,
which has reached End Of Life. As such, we will not be fixing bugs in
this version of the package. If this problem is reproducible on later
supported versions of
Thank you for reporting this issue and helping to improve Ubuntu.
This bug was reported against the version of systemd in Ubuntu 16.10,
which has reached End Of Life. As such, we will not be fixing bugs in
this version of the package. If this problem is reproducible on later
supported versions of
Thank you for reporting this issue and helping to improve Ubuntu.
This bug was reported against the version of systemd in Ubuntu 16.10,
which has reached End Of Life. As such, we will not be fixing bugs in
this version of the package. If this problem is reproducible on later
supported versions of
Thank you for reporting this issue and helping to improve Ubuntu.
This bug was reported against the version of systemd in Ubuntu 16.10,
which has reached End Of Life. As such, we will not be fixing bugs in
this version of the package. If this problem is reproducible on later
supported versions of
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Xenial)
Status: New => Triaged
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided =>
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1685045
Title:
stop using libnss_resolve.so for name
** Summary changed:
- package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
install/upgrade: subprocess installed post-installation script returned error
exit status 1
+ gnome-software frontend can close while packages are still configuring,
breaking debconf prompts
We discussed on IRC that this is because *no* systemd units are being
activated; the user session is not being run under systemd. This is a
regression vs. unity, and should be considered a bug in the desktop
session as a whole.
Reassigning this to gnome-session, which seems like the correct
Override component to main
gnome-characters 3.26.2-2 in bionic: universe/misc -> main
gnome-characters 3.26.2-2 in bionic amd64: universe/gnome/optional/100% -> main
gnome-characters 3.26.2-2 in bionic arm64: universe/gnome/optional/100% -> main
gnome-characters 3.26.2-2 in bionic armhf:
This appears to be a bug in the systemd cryptsetup helper, which has a
constraint requiring a block device where no such constraint exists in
cryptsetup itself. Since Ubuntu 17.10 now uses swap files by default
instead of swap partitions, this will fail.
** Package changed: cryptsetup (Ubuntu)
This is a failure to configure shim-signed because the debconf frontend
started by gnome-software has exited, leaving the socket behind. This
is a bug in gnome-software; reassigning.
** Package changed: shim-signed (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification
** Changed in: systemd (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Zesty)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Artful)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => Won't Fix
--
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1723956
Title:
busybox-static: several network applets
snapd will not function without systemd as a deputy init. nothing to
fix in snapd.
** Changed in: snapd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Reassigning to gnome-software, which should take care to not let the
debconf frontend die while dpkg is still running.
** Package changed: shim-signed (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** No longer affects: shorewall (Ubuntu)
** No longer affects: shorewall (Ubuntu Xenial)
** No longer affects: ipsec-tools (Ubuntu Xenial)
** No longer affects: ipsec-tools (Ubuntu)
** No longer affects: shorewall6 (Ubuntu Xenial)
** No longer affects: shorewall6 (Ubuntu)
** No longer
Public bug reported:
I noticed that today's package upgrades were taking a long time.
Looking at the process list, I saw that systemctl daemon-reload was
running from each maintainer script and taking a long time to complete -
upwards of 1 minute for each invocation.
I did not see such behavior
This is now handled by the systemd package (/lib/systemd/systemd-rfkill;
/lib/systemd/system/rfkill.service). And yes, it is buggy from what I
can see.
** Package changed: rfkill (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Quick question. If we enable the proposed PPA, how do we go back to
getting stable updates? Just remove the PPA and keep apt updating like
normal?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
systemd-resolve is not part of resolvconf, it is part of systemd;
reassigning.
A possible quick fix is to modify the /etc/nsswitch.conf:
Or even remove "resolve" completely: "hosts: ... dns"
We are not installing libnss-resolve by default in Ubuntu, we are using
systemd-resolved as a DNS
Public bug reported:
Some applications disable "Night Light" and it is not reenabled upon
exiting application.
Examples:
Minecraft
Nvidia Settings
World of Warcraft via Wine.
You can go into settings and manually toggle "Night Light" off and back
on in order to get the blue light reduction to
*** This bug is a duplicate of bug 1607929 ***
https://bugs.launchpad.net/bugs/1607929
** This bug is no longer a duplicate of bug 1372193
package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 128 in
*** This bug is a duplicate of bug 1607929 ***
https://bugs.launchpad.net/bugs/1607929
** This bug is no longer a duplicate of bug 1372193
package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 128 in
** Changed in: pam (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1699360
Title:
package libpam-systemd:amd64 232-21ubuntu4
According to the Gmail email notice I received:
"Google will continue to block sign-in attempts from the app you're using
because it has known security problems or is out of date. You can continue to
use this app by allowing access to less secure apps, but this may leave your
account
** Package changed: nfs-utils (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1712639
livecd-rootfs fixed in version 2.468:
livecd-rootfs (2.468) artful; urgency=medium
[ Dimitri John Ledkov ]
* Drop obsolete fix-ups of resolv.conf, debootstrap should now result in
correct symlink to resolved without any further fixes.
[ Michael Hudson-Doyle ]
* Have
netcfg is also fixed.
netcfg (1.142ubuntu4) artful; urgency=medium
* Add resolved support. LP: #1714167
-- Dimitri John Ledkov Wed, 20 Sep 2017 09:52:03
+0100
** Changed in: netcfg (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification
network-manager is also fixed:
network-manager (1.8.2-1ubuntu6) artful; urgency=medium
* src/dns/nm-dns-manager.c:
- Fix resolved detection, the symlink target is usually relative to
the root, such that in chroots the file points to a file inside the
chroot. But keep absolute
Public bug reported:
My laptop has been continuously upgraded (sometimes during development
cycles, sometimes only after release) since Ubuntu 10.04.
After upgrade to 17.10, I initially used wayland, but ran into some
problem with VT switching which led me to switch to X.
Upon switching to X,
Yes, zesty is affected. artful is not affected, as upstream did not
apply the fix for CVE-2017-183 to trunk, due to the introduction of
using libarchive by default. trusty is also not affected, as the mime
types configure processing is handled differently there.
--
You received this bug
I understand that systemd in artful is already exposing these options
upstream, so marking this task fixed.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in
'MemoryDenyWriteExecute=yes' is defined in systemd.exec(5) as:
If set, attempts to create memory mappings that are writable and
executable at the same time, or to change existing memory mappings to
become executable, or mapping shared memory segments as executable are
prohibited. Specifically, a
Public bug reported:
With the migration to netplan/systemd-networkd/systemd-resolved,
autopkgtest VMs now end up with multiple default routes. This causes
miscellaneous autopkgtest failures of packages that assume a single
record will be returned when grepping route -n output for 0.0.0.0.
These
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Tags added: netplan-transition
** Changed in: systemd (Ubuntu)
Importance: Critical => High
** Also affects: systemd (Ubuntu Artful)
Importance: High
Status: New
--
You received this bug notification because
netscript-2.4 is an alternate network manager package which would make
its own technology selections independent of Ubuntu defaults and
systemd.
** Changed in: netscript-2.4 (Ubuntu)
Status: New => Won't Fix
** Changed in: whereami (Ubuntu)
Status: New => Triaged
** Changed in:
isc-dhcp-client only suggests resolvconf, it does not interface with it.
** Changed in: isc-dhcp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
dibbler-client doesn't interface with resolvconf, it only recommends it.
This does not warrant carrying an Ubuntu delta.
** Changed in: dibbler (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Dimitri intends to handle this in systemd postinst instead.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** Also affects: openssh (Ubuntu Artful)
Importance: Critical
Assignee: Dimitri John Ledkov (xnox)
Status: Fix Released
** Also affects: systemd (Ubuntu Artful)
Importance: Critical
Assignee: Dimitri John Ledkov (xnox)
Status: Triaged
** Tags removed:
** Package changed: initramfs-tools-ubuntu-touch (Ubuntu) => systemd
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1713536
Title:
udev: boot script does not trigger
Removing packages from artful:
platform-api 3.0.1+17.04.20170215-0ubuntu1 in artful
libplatform-api-headers 3.0.1+17.04.20170215-0ubuntu1 in artful
amd64
libplatform-api-headers 3.0.1+17.04.20170215-0ubuntu1 in artful
arm64
Removing packages from artful:
location-service 3.0.0+16.10.20160912-0ubuntu4 in artful
libubuntu-location-service-dbg 3.0.0+16.10.20160912-0ubuntu4 in
artful amd64
libubuntu-location-service-dbg 3.0.0+16.10.20160912-0ubuntu4 in
artful arm64
Removing packages from artful:
qtvideo-node 0.2.1+17.04.20170214-0ubuntu1 in artful
qtvideonode-plugin 0.2.1+17.04.20170214-0ubuntu1 in artful amd64
qtvideonode-plugin 0.2.1+17.04.20170214-0ubuntu1 in artful arm64
qtvideonode-plugin
Removing packages from artful:
qtubuntu-camera 0.3.3+16.04.20160517-0ubuntu1 in artful
cameraplugin-aal 0.3.3+16.04.20160517-0ubuntu1 in artful amd64
cameraplugin-aal 0.3.3+16.04.20160517-0ubuntu1 in artful arm64
cameraplugin-aal
ubuntu-application-api3-desktop (platform-api) depends: libubuntu-
location-service3 (location-service). libubuntu-location-service3
depends: libubuntu-platform-hardware-api3 (platform-api). Packages to
be removed together.
--
You received this bug notification because you are a member of
Removing packages from artful:
repowerd 2017.03+17.04.20170403-0ubuntu1 in artful
powerd 2017.03+17.04.20170403-0ubuntu1 in artful amd64
powerd 2017.03+17.04.20170403-0ubuntu1 in artful arm64
powerd 2017.03+17.04.20170403-0ubuntu1 in artful
Removing packages from artful:
python-ubuntu-platform-api 1.1+14.10.20140612-0ubuntu1 in artful
python-ubuntu-platform-api 1.1+14.10.20140612-0ubuntu1 in
artful armhf
Comment: obsoleted product, no longer developed; LP: #1712955
1 package successfully removed.
** Changed
Removing packages from artful:
powerd 0.16+16.04.20160204.1-0ubuntu2~xenial1 in artful
Comment: obsoleted product, no longer developed; LP: #1712955
1 package successfully removed.
** Changed in: powerd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
The referenced upstream bug report shows that upstream agrees this is a
regression in systemd behavior which they are planning to correct, which
is reasonable.
However, I think this is also a bug in the kdump-tools package.
'default.target' is a meta-target, which no package can know whether
it's
** Summary changed:
- udevadm trigger subsystem-match=net doesn't always run rules
+ udevadm trigger subsystem-match=net doesn't always run rules because of
reconfiguration rate-limiting
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Also affects: systemd (Ubuntu Artful)
** Package changed: linux (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You
ok sounds like this needs to be addressed in netplan.
** Package changed: systemd (Ubuntu) => nplan (Ubuntu)
** Changed in: nplan (Ubuntu)
Importance: Undecided => High
** Changed in: nplan (Ubuntu)
Status: Incomplete => Triaged
** Changed in: nplan (Ubuntu)
Assignee:
The watchdogs are by design. The unclean journal may not be. OTOH if
this only happens with the ephemeral journal in /run, the impact is
minor. We should check whether the unclean journal problem is
reproducible with /var/log/journal.
** Also affects: systemd (Ubuntu Artful)
Importance:
desktop-packages now subscribed.
** Changed in: caribou (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1685867
Title:
[MIR]
This MIR was approved without a team subscriber. Reopening the bug and
targeting so that this gets sorted.
** Changed in: caribou (Ubuntu)
Importance: Undecided => High
** Changed in: caribou (Ubuntu)
Status: Fix Released => Incomplete
** Changed in: caribou (Ubuntu)
Milestone:
We believe this is most likely a duplicate of bug #1682499 which was
fixed in systemd 232-21ubuntu3. If you can still reproduce this problem
after upgrading to the zesty-updates version of systemd, please reopen.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You
Public bug reported:
I have a zesty system that uses systemd-resolved, as per default, which
also has dnsmasq configured for use on interface virbr0 for my libvirt
bridge.
This system is also part of a Kerberos realm. Recent versions of
Kerberos do a lookup of a URI RR, à la:
$ nslookup -q=URI
> The requirement here is, I need to know when ens1 goes up or down, so
> that I can make changes to the bridge interface. The `ifmonitor` script
> will monitor the link status of ens1, and then take appropriate actions,
> such as restarting a DHCP client, adding or removing routes that have
>
I guess lack of ifupdown support is worked around with
{pre,post}-{up,down} scripts.
The first thing to do is figure out whether / how this needs to be
represented in the network yaml. Is there a reason to treat this as a
different kind/class of network config than a bond using the bonding
Hello errors.ubuntu.com, or anyone else affected,
Accepted gnome-software into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170509.0.8292905-0ubuntu1 in a few hours, and then
in the -proposed repository.
Please
Hi Robert, just so you know, we appear to be seeing bug reports also on
the package upgrade side as a result of these dropped debconf socket
connections, e.g.: bug #1691983. It's sensible for gnome-software not
to crash on a failed connection, but I think ultimately what we need are
succeeding
Hello errors.ubuntu.com, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170509.0.8292905-0ubuntu1~xenial1 in a few hours,
and then in the -proposed repository.
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721
Public bug reported:
Install hung up at 51%, then window wouldn't close. Later attempt appeared to
install, but I still got an error report.
Ubuntu 17.04
New user. Just installed OS yesterday.
Hello Jeremy, or anyone else affected,
Accepted gjs into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gjs/1.48.3-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
Package:
gnome-disk-utility-3.10.0_1ubuntu3_i386
OS:
LiveDVD Ubuntu 14.04.1 ubuntu 3.13.0-32 i686
Hardware:
Dell Dimension 4550 4mB Pentium 4
Seagate Backup Plus 1TB
I tried to create a disk image of the primary disk's boot partition on an
external USB backup drive.
The verification of the Stable Release Update for gnome-software 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
** No longer affects: gconf2 (Ubuntu)
** No longer affects: gconf2 (Ubuntu Xenial)
** No longer affects: gconf2 (Ubuntu Yakkety)
** No longer affects: gconf2 (Ubuntu Zesty)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Hello Robert, or anyone else affected,
Accepted gnome-software into zesty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.22.7-0ubuntu3.17.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
Public bug reported:
Once we have systemd-resolved's stub DNS resolver on a solid footing
everywhere (LP: #1682499; LP: #1647031), we should stop using
libnss_resolve.so for name resolution and *only* use the DNS stub
resolver via libnss_dns.so.
The reason is that libnss_resolve.so is
Verified by way of a slightly modified test case:
- boot a yakkety cloud image
- verify 127.0.0.53 in /etc/resolv.conf
- sudo sed -i -e's/resolve \[[^]]*\] //' /etc/nsswitch.conf
- ping www.freedesktop.org -> FAIL
- install systemd from -proposed
- ping www.freedesktop.org -> SUCCESS
**
** Changed in: gnome-software (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1679435
Title:
installing dkms package from
this is an incomplete fix; we also need to change the code to tell
aptdaemon which debconf frontend to use.
** Changed in: gnome-software (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I believe the problem is that nothing ensures that the desktop
components which select and install software have access to a GUI
debconf frontend.
I think the proper solution is for each of the frontends to aptdaemon to
depend/recommend a suitable debconf frontend component (libgtk2-perl,
** Also affects: gnome-software (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-software (Ubuntu)
Status: New => Triaged
** Changed in: gnome-software (Ubuntu)
Importance: Undecided => Critical
** Changed in: shim-signed (Ubuntu)
Status: Triaged =>
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
The verification of the Stable Release Update for metacity 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
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in
I was reminded that libnss-resolve is in 'standard' now, which means
it's also installed by default on server and any bugs that affect only
the stub DNS resolver without affecting the dbus service - such as this
one - do not impact DNS resolution by default on server in 16.10.
(I was wondering
As I recall resolved is also enabled by default in Ubuntu Server 16.10
(though not on Desktop), so this is a critical issue there as well.
Dimitri, could you please have a look at this backport?
Could someone who's seeing the DNSSEC problem please also file a
separate bug report, so we can track
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Trusty)
Status: New => Triaged
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
The verification of the Stable Release Update for glib2.0 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 glib2.0 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 glib2.0 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 indicated upstream patch, f50582649f8eee73f59aff95fadd9a963ed4ffea,
does not apply cleanly against systemd 229. Are there known
prerequisites for this patch?
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Yakkety)
My kernel is at 4.4.0-57-generic #78 but I still has this problem
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1647187
Title:
gnome-software crashed with signal 5 in
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: glibc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
The resolvconf portion of this issue has been moved to bug #1649931.
I'm removing resolvconf 1.78ubuntu3 from xenial-proposed and will
replace it with a resolvconf 1.78ubuntu4 with the correct bug ref.
** Changed in: resolvconf (Ubuntu Xenial)
Status: Fix Committed => Invalid
** Changed
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: resolvconf (Ubuntu Yakkety)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Public bug reported:
I have an ipv4 entry for a key host on my network listed in /etc/hosts,
for network recovery purposes. This host also has ipv6 connectivity;
the ipv6 address is resolvable via DNS, but I do not have it in
/etc/hosts. Resolution of hostname should be independent for each
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Yakkety)
Importance: Undecided
Status: Confirmed
** Changed in: systemd (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because
Override component to main
location-service 3.0.0+16.10.20160811-0ubuntu1 in yakkety: universe/utils ->
main
libubuntu-location-service-dbg 3.0.0+16.10.20160811-0ubuntu1 in yakkety amd64:
universe/debug/optional/100% -> main
libubuntu-location-service-dbg 3.0.0+16.10.20160811-0ubuntu1 in yakkety
Override component to main
zeromq3 4.1.5-2 in yakkety: universe/libs -> main
libzmq3-dev 4.1.5-2 in yakkety amd64: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety arm64: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety armhf:
Override component to main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety: universe/net -> main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety amd64:
universe/net/optional/100% -> main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety arm64:
universe/net/optional/100% -> main
Hello Dave, or anyone else affected,
Accepted ubiquity into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubiquity/2.21.63.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've thought about this some more, and while the /bin/readlink
/usr/bin/readlink in busybox is a bug, fixing this is definitely not
going to fix the problem in the installer. In the installer,
/etc/udev/rules.d/80-net-setup-link.rules will never exist since this is
an admin override; so the
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1615021
Title:
Unable to network boot Ubuntu 16.04
Examining the initrd shows that readlink is provided as
/usr/bin/readlink -> /bin/busybox, not as /bin/readlink where systemd
expects it (and where it's shipped on an installed system). This is a
bug in debian-installer's construction of that image - though gee it
would be nice if systemd didn't
Nothing that depends on network-manager-openvpn has yet been seeded in
main. Re-demoting until this is done.
** Changed in: network-manager-openvpn (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
501 - 600 of 2745 matches
Mail list logo