Public bug reported:
ntp-systemd-netif.path contains the following:
[Install]
WantedBy=network-pre.target
However, network-pre.target is a passive systemd target. It is used
only for ordering, and is not guaranteed to be pulled in unless
something else calls for it explicitly.
On a host where
This behavior is also presenting on Bionic.
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770248
Title:
console-setup fails intermittently due to a missing file in /tmp
To
Packages from security-proposed tested and look ok.
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752306
Title:
Security bug in XMLTooling-C before 1.6.4
Debdiff attached which fixes the problem for Xenial.
Since there is no corresponding Debian release to fakesync this from for
Xenial, I've just recreated the patch sequence against the version
already in Xenial. It includes the same two quilt patches which have
been fake-synced into Trusty, and
Here's a debdiff for Xenial. It is my understanding that Trusty can get
a fakesync from Jessie.
** Patch added: "CVE-2018-0486.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xmltooling/+bug/1743762/+attachment/5038524/+files/CVE-2018-0486.debdiff
--
You received this bug notification
Also note that the previous (current) version of network-manager
(1.2.6-0ubuntu0.16.04.1) is also failing s390x autopkgtest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696415
Title:
The autopkgtest failure on s390x is in a test that checks rfkill
integration. s390 kernels do not have CONFIG_RFKILL set. Behavior
change might have something to do with the recent change to s390x
autopkgtest from LXC containers to VMs?
Version 1.2.6-0ubuntu0.16.04.2 has been deployed here to several
machines that were experiencing the bug multiple times per day. All
DHCP renewal requests since deployment have resulted in renewal
notifications being successfully delivered to NetworkManager.
** Tags removed:
Sorry for the delay - I was away for a week. I have deployed the
packages from -proposed and will confirm after keeping an eye on DHCP
lease renewals for a while.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sjors:
I'm interested to know how it goes for you with this update (either from
the included debdiff, or from the packages when they hit -proposed.) We
were seeing the exact same symptoms you were, and deep-dove into your
backported fix from the GNOME bug and it all seems like it should fix
the
** Description changed:
I've found an issue on some of our Xenial office machines, causing
NetworkManager to drop its IP address lease in some cases when it
shouldn't. I'm not sure if the actual bug is in NetworkManager or
perhaps dbus or dhclient, but I'll do my best to help to figure
Correction/Addendum to the SRU justification above:
Fixed in current Ubuntu. Bionic uses NM 1.8.x. This bug was fixed in
1.4.
[Impact]
* This LP bug's original submitter backported the upstream 1.4 fix to
1.2, not Upstream.
[Regression Potential]
* The patch changes both nm-dhcp-helper and
[Impact]
* nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
lease renewal due to a DBus race condition.
* Upstream NetworkManager 1.4 fixes the race condition by changing
nm-dhcp-helper's DBus notification from signal "Event" to method
"Notify".
* Upstream
Upstream GNOME bug fixed. I've applied the fix to Xenial's NM and
tested. SRU incoming.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696415
Title:
NetworkManager does not update IPv4 address
*** This bug is a duplicate of bug 1676380 ***
https://bugs.launchpad.net/bugs/1676380
** This bug has been marked a duplicate of bug 1676380
Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures
--
You received this bug notification because you are a member of
Can confirm. Saw this failure on dozens of machines today when 2.1.3-4
failed to upgrade to 2.1.3-4ubuntu0.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676993
Title:
package cups-daemon
Public bug reported:
The cyrus-admin-2.4 package only contains the cyradm, sieveshell, and
installsieve scripts, and their associated documentation. These
utilities are for remote administration/interaction with a Cyrus IMAP or
Sieve server, and really only need to depend on
*** This bug is a security vulnerability ***
Public security bug reported:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4545
From CVE report:
--
cURL and libcurl 7.18.0 through 7.32.0, when built with OpenSSL, disables the
certificate CN and SAN name field verification
It can happen much more frequently than that.
I have three machines in particular that do weekly reboots. They all
have two network interfaces, but only one of them is used. Every week,
one or more of them will lose on an interface that matters (loopback or
the used network interface), and
Public bug reported:
Ubuntu 12.04.2
ifupdown 0.7~beta2ubuntu8
Symptom: Every so often, /etc/init/network-interface.conf fails to bring
up the loopback interface.
Mar 25 16:39:37 kernel: [ 28.793922] init: network-
interface (lo) pre-start process (1079) terminated with status 1
Note: Exact same locking semantics are present in latest ifupdown
(0.7.40) from upstream Debian.
Suggested fix: Lock a lockfile, not the statefile.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug reported upstream (to Debian) against latest version (0.7.40). Will
update with Debain bug number when accepted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160490
Title:
race condition
Upsteam bug report:
#704003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704003
** Bug watch added: Debian Bug tracker #704003
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704003
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Tested 1.4.3-1ubuntu1.6 from lucid-proposed.
Works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/857663
Title:
cups crashes on SIGHUP if printer classes are defined
To manage notifications
Public bug reported:
After automatically resolving conflicts in pam-config stubs, pam-auth-
update will still pop up a warning notification that requires the user
to select [Ok].
Requiring user interaction kind of defeats the purpose of having the
automatic Conflicts and Priority
Then why does pam-auth-update deactivate only the lower priority module
when a Conflict: is found?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965662
Title:
pam-auth-update conflict resolution
Public bug reported:
Currently, libpam-ldap provides a pam-auth-update stub that inserts
pam_ldap into the authorization stack as Account-Type: Primary.
Unfortunately, this means that, should pam_unix (also Account-Type:
Primary) succeed, pam_ldap will never be checked. It also means that
Public bug reported:
Currently, libpam-ldap provides a pam-auth-update stub that inserts
pam_ldap into the authorization stack as Account-Type: Primary.
Unfortunately, this means that, should pam_unix (also Account-Type:
Primary) succeed, pam_ldap will never be checked. It also means that
The discussion was via private email.
In short, the existing code's call to krb5_set_default_in_tkt_etypes()
with a second argument that may be NULL is a sneaky way of avoiding the
situation where using a restricted credential will restrict all
credentials in the current thread. It fixes one bit
Public bug reported:
/usr/lib/libsocksd.so - libsocksd0.so.0
/usr/lib/libsocksd.so.0 - libsocksd.so.0.1.0
/usr/lib/libsocksd.so.0.1.0
Note that libsocksd.so links to libsocksd0.so.0, which does not exist,
instead of libsocksd.so.0.
This prevents linking against the shared version of libsocksd.
Even if an actual MTA is added to the d-i pkgsel/include debconf
question in the installer preseed file, setting up software RAID in the
installer will cause postfix to be installed, prompting the user for
configuration information, and then postfix will silently be replaced
with the MTA requested
** Description changed:
- Known bug in CUPS 1.4.3, fixed in 1.4.4.
+ Affects: cups 1.4.3-1ubuntu1.5 on Lucid.
+
+ Known bug in CUPS 1.4.3, fixed in 1.4.4. When cups receives a SIGHUP
+ (for log rotation, restart, etc), the cleanup routines free pointers to
+ printer policy info, but then later
** Patch added: str3524.patch
https://bugs.launchpad.net/bugs/857663/+attachment/2449024/+files/str3524.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/857663
Title:
cups crashes on SIGHUP
Public bug reported:
Affects: cups 1.4.3-1ubuntu1.5 on Lucid.
Ubuntu releases with a cups derived from 1.4.4 or later are unaffected.
Known bug in CUPS 1.4.3, fixed in 1.4.4. When cups receives a SIGHUP
(for log rotation, restart, etc), the cleanup routines free pointers to
printer policy
Public bug reported:
Heimdal's libgssapi init_auth() makes a call to
krb5_set_default_in_tkt_etypes() to support certain NFS clients.
However, this call is always made, and thus can also be made when the
second argument passed can be NULL. The behaviour of
krb5_set_default_in_tkt_etypes() in
** Patch added: Patch to lib/gssapi/krb5/init_sec_context.c
https://bugs.launchpad.net/bugs/849349/+attachment/2399116/+files/lib.gssapi.krb5.init_sec_context.c.patch-1.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A reply from the upstream developer to my upstream patch submission has
revealed that fixing this bug exposes another edge-case bug elsewhere.
A decision on what to do upstream is pending.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The fix to this bug is arguably incorrect. The UID_MIN value in
login.defs is only for specifying the start of the range of dynamically-
allocated UIDs assigned by useradd or newusers. It does not account for
user accounts added to the system via other means, such as pre-existing
accounts with
Note that just rebuilding a newer version of heimdal that contains the
allow_weak_crypto fix will introduce the following Maverick/Natty bug
into Lucid:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/663319
It will also not actually fix any existing Lucid binaries, as they
depend on
** Description changed:
The allow_weak_crypto krb5.conf option was added to Heimdal during the
1.2 release, but was implemented incorrectly. The check for desired
enctypes was performed before the check to see if allow_weak_crypto is
true.
This has the unfortunate effect of
** Summary changed:
- Lucid/Maverick heimdal packages have missing/broken allow_weak_crypto
implementation
+ Maverick heimdal packages have broken allow_weak_crypto implementation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Forget everything I wrote about Lucid. There is currently no need to
backport anything from 1.4 into the version of 1.2 in Lucid. The old
enctypes had yet to be deprecated in the version that appears in Lucid,
so there is no need for allow_weak_crypto in Lucid.
However, the caveat still stands
Public bug reported:
The allow_weak_crypto krb5.conf option was added to Heimdal during the
1.2 release, but was implemented incorrectly. The check for desired
enctypes was performed before the check to see if allow_weak_crypto is
true.
This has the unfortunate effect of resulting in a
43 matches
Mail list logo
