[Bug 1532508] Update Released

The verification of the Stable Release Update for unity 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

[Bug 1392012] Re: [MIR] libteam

Override component to main libteam 1.26-1 in bionic: universe/misc -> main libteam-dev 1.26-1 in bionic amd64: universe/libdevel/optional/100% -> main libteam-dev 1.26-1 in bionic arm64: universe/libdevel/optional/100% -> main libteam-dev 1.26-1 in bionic armhf: universe/libdevel/optional/100% ->

[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

** Also affects: glibc (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Bionic) Importance: High Status: Invalid ** Also affects: systemd (Ubuntu Bionic) Importance: High Status: Triaged -- You received this bug notification

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

fetchmail integrates with resolvconf via /etc/resolvconf/update- libc.d/fetchmail; I think this warrants another look. ** Changed in: fetchmail (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1746765] Re: systemd FTBFS on arm64

** Bug watch added: Sourceware.org Bugzilla #22764 https://sourceware.org/bugzilla/show_bug.cgi?id=22764 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=22764 Importance: Unknown Status: Unknown -- You received this bug notification because you are

[Bug 1746765] Re: systemd FTBFS on arm64

** Also affects: binutils (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnu-efi (Ubuntu Bionic) Importance: Undecided Assignee: Julian Andres Klode (juliank) Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status:

[Bug 1737250] Re: systemd-resolved returns only short hostname when PTR record of local IP is requested

*** This bug is a duplicate of bug 1739672 *** https://bugs.launchpad.net/bugs/1739672 ** This bug has been marked a duplicate of bug 1739672 Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR -- You received this bug

[Bug 1676115] Re: systemd-resolved spams the system log with useless “Processing query...” messages

> This was fixed upstream in v233 by downgrading this message from log_info to log_debug: So this is fixed in Ubuntu 17.10 and later. ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1661716] Re: Domain names not resolving on bootup

There were a number of bugs reported in the 16.10 timeframe about this issue. I believe these have all been resolved as of Ubuntu 17.04, so am closing this bug fix-released. If you are still seeing issues with systemd-resolved in a currently supported release of Ubuntu, please reopen this

[Bug 1650877] Re: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary

*** This bug is a duplicate of bug 1682499 *** https://bugs.launchpad.net/bugs/1682499 ** This bug has been marked a duplicate of bug 1682499 Disable DNSSEC by default -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in

[Bug 1663031] Re: cannot resolve www.facebook.com

*** This bug is a duplicate of bug 1682499 *** https://bugs.launchpad.net/bugs/1682499 ** This bug is no longer a duplicate of bug 1650877 systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary ** This bug has been marked a duplicate of bug 1682499 Disable

[Bug 1659520] Re: openvpn network manager plugin dns server settings do not take effect in 16.10

I believe this was fixed in Ubuntu 17.04 and later. If you are still experiencing this problem with a currently supported Ubuntu release, please reopen this report. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member

[Bug 1653495] Re: systemd-resolved breaks Steam

*** This bug is a duplicate of bug 1647031 *** https://bugs.launchpad.net/bugs/1647031 ** This bug has been marked a duplicate of bug 1647031 systemd-resolved’s 127.0.0.53 server does not follow CNAME records -- You received this bug notification because you are a member of Ubuntu

[Bug 1742310] Re: No network in recovery mode (systemd-resolved does not start)

** Package changed: systemd (Ubuntu) => friendly-recovery (Ubuntu) ** Changed in: friendly-recovery (Ubuntu) Importance: Undecided => High ** Changed in: friendly-recovery (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1668296] Re: not failing back to IPv4 when AAAA returns SERVFAIL

I cannot reproduce this with the libnss-resolve in Ubuntu 17.04 or 17.10. The original problem was reported with systemd 231; 17.04 shipped with 232. It is possible that this has been fixed in systemd upstream (the linked upstream bug has been closed), or it's possible that the DNS configuration

[Bug 1731211] Re: systemd breaks interface configuration due to late resolv.conf

What exactly are the contents of /etc/network/interfaces.d/vlan0? I would not normally expect dnsmasq to be started as part of the network interface configuration via ifupdown. If there is a reason to configure it this way, then /lib/systemd/system/networking.service would need to be changed to

[Bug 1730744] Re: sudo is slow (10 seconds) when hostname is not resolvable

*** This bug is a duplicate of bug 1739672 *** https://bugs.launchpad.net/bugs/1739672 ** This bug has been marked a duplicate of bug 1739672 Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR -- You received this bug

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

According to https://github.com/systemd/systemd/issues/6520 this can be worked around by setting DNSStubListener=yes in /etc/systemd/resolved.conf. This is disabled by default due to . It is not ideal to have systemd-resolved conflict with other

[Bug 1729194] Re: Systemd-Resolvd Forgets to Resolv Request

127.0.1.1 is not the address of systemd-resolved, as you noted; it's the address used by dnsmasq. It sounds like your network-manager config is pointing to dnsmasq, which is no longer the default in 17.10, and should have been dropped from your config on upgrade from 16.10 to 17.04. Can you

[Bug 1738375] Re: Resolving DNS entry, answer too big to handle

$ ping www.ziggogo.tv PING www.ziggogo.tv(2001:730:3400:8000::14 (2001:730:3400:8000::14)) 56 data bytes 64 bytes from 2001:730:3400:8000::14 (2001:730:3400:8000::14): icmp_seq=1 ttl=52 time=176 ms 64 bytes from 2001:730:3400:8000::14 (2001:730:3400:8000::14): icmp_seq=2 ttl=52 time=178 ms ^C

[Bug 1632681] Re: SonicWall NetExteder broken by new nsswitch.conf configuration

In Ubuntu 17.10 and later, this is resolved by removing libnss-resolve from the default install and only using systemd-resolved via resolv.conf. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu

[Bug 1628287] Re: systemd-resolved crashed with SIGABRT in log_assert_failed()

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

[Bug 1626647] Re: systemd-resolved assert failure: *** Error in `/lib/systemd/systemd-resolved': malloc(): memory corruption: 0x000055fd92c8e370 ***

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

[Bug 1625437] Re: systemd-resolved crashed with SIGSEGV in sd_event_source_unref()

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

[Bug 1621316] Re: systemd-resolved crashed with SIGSEGV

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

[Bug 1605307] Re: systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

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

[Bug 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

** 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 =>

[Bug 1685045] Re: stop using libnss_resolve.so for name resolution

** 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

[Bug 1737772] Re: gnome-software frontend can close while packages are still configuring, breaking debconf prompts (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/u

** 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

[Bug 1743366] Re: Systemd .path units are not working properly in Bionic

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

[Bug 1713176] Re: [MIR] gnome-characters

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:

[Bug 1731870] Re: Failed to start Cryptography Setup for cryptswap1

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)

[Bug 1739675] Re: 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

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

[Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

** 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 --

[Bug 1723956] Re: busybox-static: several network applets segfaulting

** 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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

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.

[Bug 1737772] Re: 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

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

[Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start

** 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

[Bug 1733925] [NEW] systemd 234-2ubuntu12.1 takes 1minute+ for systemctl --system daemon-reload

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

[Bug 1548057] Re: rfkill state is not restored on reboot

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,

[Bug 1728445] Re: DNS not working for IPv6-only host names when using Miredo

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

[Bug 1442859] Re: package libpam-systemd:amd64 219-7ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

*** 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

[Bug 1406724] Re: package libpam-systemd:amd64 204-5ubuntu20.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

*** 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

[Bug 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

** 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

[Bug 1712639] Re: nfs-kernel-server doesn't wait on (luks) encrypted fs on startup

** 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

[Bug 1712283] Re: Cannot resolve DNS in artful daily

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

[Bug 1712283] Re: Cannot resolve DNS in artful daily

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

[Bug 1712283] Re: Cannot resolve DNS in artful daily

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

[Bug 1724890] [NEW] after upgrade to 17.10, getting gnome-flashback by default under X

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,

[Bug 1718029] Re: cloudstack and azure datasources broken when using netplan/systemd-networkd

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

[Bug 1719720] Re: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

'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

[Bug 1718842] [NEW] autopkgtest environments end up with duplicate default routes

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

[Bug 1718771] Re: Incorrect handling of link-local IPv6 DNS servers

** 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

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

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:

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

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.

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

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

[Bug 1716979] Re: clean up unmodified /etc/rc.local on upgrade

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.

[Bug 1712921] Re: enabling networkd appears to eat up entropy

** 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:

[Bug 1713536] Re: udev: boot script does not trigger subsystem coldplug

** 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

[Bug 1712955] Re: RM: obsolete product

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

[Bug 1712955] Re: RM: obsolete product

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

[Bug 1712955] Re: RM: obsolete product

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

[Bug 1712955] Re: RM: obsolete product

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

[Bug 1712955] Re: RM: obsolete product

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

[Bug 1712955] Re: RM: obsolete product

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

[Bug 1712955] Re: RM: obsolete product

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

[Bug 1712955] Re: RM: obsolete product

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

[Bug 1708409] Re: kdump service does not start after configure/reboot

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

[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

** 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)

[Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=

** 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

[Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure

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:

[Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

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:

[Bug 1685867] Re: [MIR] caribou

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]

[Bug 1685867] Re: [MIR] caribou

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:

[Bug 1656830] Re: Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

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

[Bug 1694156] [NEW] systemd-resolved and libvirt dnsmasq instance get into a busy loop when a query is issued for a URI or SRV record

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

[Bug 1664818] Re: Not possible to render pre-up, pre-down, post-up, or post-down snippets

> 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 >

[Bug 1664846] Re: [Wishlist] Support for teaming driver

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

[Bug 1689425] Please test proposed package

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

[Bug 1689425] Re: /usr/bin/gnome-software:11:g_source_attach:debconf_accept_cb:socket_source_dispatch:g_main_dispatch:g_main_context_dispatch

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

[Bug 1689425] Please test proposed package

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.

[Bug 1688704] Re: Update gjs to 1.48.3

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

[Bug 1688407] Update Released

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

[Bug 1672424] Re: Cannot install Debian files outside of the repositories

** 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

[Bug 1688407] Re: Snap title field reverted to summary

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

[Bug 1685045] [NEW] stop using libnss_resolve.so for name resolution

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

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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 **

[Bug 1679435] Re: installing dkms package from gnome-software, no debconf frontend: package shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed pos

** 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

[Bug 1679435] Re: installing dkms package from gnome-software, no debconf frontend: package shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed pos

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

[Bug 1679435] Re: installing dkms package from software-center, no debconf frontend: package shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed po

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,

[Bug 1679435] Re: installing dkms package from software-center, no debconf frontend: package shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed po

** 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 =>

[Bug 1675369] Update Released

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

[Bug 1673860] Re: systemd-resolved unit should run Before=network-online.target

** 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

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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

[Bug 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04

** 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

[Bug 1633824] Update Released

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

[Bug 1644320] Update Released

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

[Bug 1638245] Update Released

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

[Bug 1651518] Re: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create

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)

<    1   2   3   4   5   6   7   8   9   10   >