*** This bug is a duplicate of bug 1365509 ***
https://bugs.launchpad.net/bugs/1365509
Patch for "master" branch: https://reviews.mahara.org/9877
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
** Changed in: openssl (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
** No longer affects: apt (Ubuntu Artful)
** No longer affects: apt (Ubuntu Xenial)
** No longer affects: apt (Ubuntu Trusty)
** No longer affects: apt (Ubuntu)
** Changed in: unattended-upgrades (Ubuntu Trusty)
Status: New => Won't Fix
--
You received this bug notification because
** No longer affects: snapd (Ubuntu Bionic)
** No longer affects: snapd (Ubuntu Xenial)
** No longer affects: snapd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
*** This bug is a duplicate of bug 1365509 ***
https://bugs.launchpad.net/bugs/1365509
Patch for "master" branch: https://reviews.mahara.org/9874
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
** No longer affects: python-apt (Ubuntu Bionic)
** No longer affects: python-apt (Ubuntu Xenial)
** No longer affects: python-apt (Ubuntu)
** This bug is no longer a duplicate of bug 1260041
Unattended-Upgrades crashes with a dpkg error
--
You received this bug notification because you
** Project changed: initramfs-tools => ubuntu
** No longer affects: ubuntu
** Project changed: software-center => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
A better fix for this issue is available in Bionic and later and also
backported to Xenial with bug 1675079.
unattended-upgrades and update-manager will now remove unused kernel
packages when there are other updates to be installed.
I'm closing this initramfs-tools task since a fix specifically
per test in bionic, turn on proposed channel, do a 'apt install
modemmanager'. it will upgrade to version 1.10.0-1~ubuntu18.04.1 and
also upgrade related libmbim and libqmi library.
I do that separate on two machine, that have DW5820e and DW5821e
separately with a sim card inside.
I confim I can
I have reclaimed /var/lib with chown to root:root and now everything is
working.
Thank you so much for your help in chasing it down! I couldn't figure
it out since it didn't point me all those levels up. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
oh it was my mistake, i was not using the native cp & mv binary, i have
solved it now. I will close the report now. Thanks for you support
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
krisbee@mythserver2018:~$ sudo ls -la /
total 120
drwxr-xr-x 25 root root 4096 Apr 11 18:41 .
drwxr-xr-x 25 root root 4096 Apr 11 18:41 ..
drwxr-xr-x 2 root root 4096 Apr 20 15:34 bin
drwxr-xr-x 3 root root 4096 Apr 20 15:37 boot
drwxrwxr-x 2 root root 4096 Jul 8 2018 cdrom
The bluez version hasn't changed (in any meaningful way) between cosmic
and disco. So I don't think that's the cause. Also, those log messages
are from the kernel.
Can you please try downgrading your kernel to something more like cosmic
(4.18) and tell us which versions do or don't have the bug?
** Tags added: regression
--
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/1825378
Title:
systemd-networkd doesn't set wireguard peer endpoint
Status in systemd package in
Looks like there is a similar open bug, so I will add a comment to it
with additional info
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1826311
Title:
** No longer affects: mysql-5.5 (Ubuntu)
** Also affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: unattended-upgrades (Ubuntu Xenial)
Status: New => Fix Released
--
You received this bug notification because you are a member of
You are running a correct/ubuntu kernel, and otherwise things look up to
date.
But you do report the below
Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks
encountered in /var/lib/colord/icc, refusing.
Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe
** Changed in: cups (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cups (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: cups (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: cups (Ubuntu Disco)
Importance: Undecided => Medium
--
You
I still haven't been able to reproduce this. If you can reproduce this
easily, maybe I can provide some kernels to be tested?
I'll keep trying to reproduce here. I compared my VM settings to why is
in the bug description, and I have the same config, except the region.
I wouldn't think that
I disagree with closing this as “WORKSFORME”. Just because core Firefox
plastered over the problem does not mean it's not an issue for other
cases. I have at least one Firefox add-on that continues to display
unreadable text because this bug causes the CSS InfoBackground and
InfoText values in
Hello, this is pretty confusing: coreutils in both 18.10 and 19.04 have
mv -Z support, so regardless of which coreutils package was unpacked at
the time, the command should have succeeded.
Could you do some investigation?
which mv
mv --help | grep Z
ls -l `which mv`
dpkg -S `which mv`
debsums
** Changed in: ipython
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1602900
Title:
libzmq3 crashes when 'getifaddrs()' is unavailable
Thanks Jann
** Information type changed from Private Security to Public Security
--
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/1814596
Title:
DynamicUser can create
Public bug reported:
root@search-3 /run/systemd/network # for i in *; do echo $i; echo; cat $i; done
; sudo service systemd-networkd stop; SYSTEMD_LOG_LEVEL=debug
/lib/systemd/systemd-networkd
10-netplan-enp0s31f6.network
[Match]
Name=enp0s31f6
[Network]
LinkLocalAddressing=ipv6
heres also the netplan file for it:
root@search-3 /run/systemd/network # netplan --debug apply
** (generate:22984): DEBUG: 21:03:47.073: Processing input file
/etc/netplan/01-netcfg.yaml..
** (generate:22984): DEBUG: 21:03:47.073: starting new processing pass
** (generate:22984): DEBUG:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-4.8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
IBus is not always launched via im-config when GNOME is involved. In
Ubuntu 19.10 im-config will be disabled by default in Wayland sessions.
So to achieve a consistent address of ibus daemon, it's better to change
the default in ibus itself. Attached please find a debdiff with a
proposed fix.
Still nothing?
--
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/1815987
Title:
Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Status in systemd package in Ubuntu:
** Changed in: gnome-online-accounts
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1825580
Title:
Gnome Online Accounts fails
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407
Another thing that I have noticed is that this problem only arises when
I click suspend or close the lid. If the laptop naturally goes sleep
then this problem doesn't occur.
--
You received this bug
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1826429
Title:
package apparmor 2.13.2-9ubuntu6 failed to install/upgrade: installed
Public bug reported:
error when upgrading from ubuntu 18.10 to 19.04
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: apparmor 2.13.2-9ubuntu6
ProcVersionSignature: Error: [Errno 2] No such file or directory:
'/proc/version_signature'
Uname: Linux 4.20.0-042000-generic x86_64
The attachment "unattended-upgrade-shutdown.patch" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user
Additional information:
I've tried to reproduce this with a virtual machine to no effect -
including installing cosmic, enabling firewall, upgrading to disco and
seeing if it still occurs. As of yet, I have not managed to reproduce it
(save for the fact that this exact problem is affecting two
I went back to the 4.18 kernel but am not running VirtualBox (running
bare metal).
Also seeing issues with libglib. gnome-shell won't run due to a trap in
libglib-2.0.so:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826025
--
You received this bug notification because you are a
Update to 2 hours ago:
Started getting segfault problems with libglib. Again re-install fixed
that but then I was getting segfaults elsewhere too.
I have now reverted to a full system backup of 18.10 that I made earlier
&& will probably stay on that for a bit longer.
--
You received this bug
On the way but could not start the sru process due to releasing Disco.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1824804
Title:
Unattended upgrades falls
Nothing helpful in this post but can confirm this issue still exists in
19.04. :(
--
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/1748839
Title:
Problem to connect
The autofirma package can be downloaded from:
https://firmaelectronica.gob.es/Home/Descargas.html
You click in "Autofirma para Linux" and download a zip file that
contains the deb package and some documentation in Spanish (if you think
there might be something useful in the documentation or in
Hello Matthias, or anyone else affected,
Accepted python-stdlib-extensions into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/python-stdlib-extensions/2.7.16-2~18.04 in a few hours, and then in the
-proposed repository.
Please help us by
Hello Matthias, or anyone else affected,
Accepted python3-stdlib-extensions into bionic-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/python3-stdlib-
extensions/3.6.8-1~18.04 in a few hours, and then in the -proposed
repository.
Please help us by
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
Public bug reported:
When unattended-upgrades sends it's status to plymouth it sends a multi-
line string which causes plymouth to display overlapping text, because
plymouth only scrolls one line when the message is sent.
The attached patch fixes this issue.
** Affects: unattended-upgrades
Public bug reported:
When booting Ubuntu 19.04 with the Ethernet cable plugged in, after
boot, network manager won't connect. Unplugging and plugging back in the
cable with the system running doesn't work to establish a connection.
The workaround is to boot with the cable unplugged, then to plug
same problem in container environment. when i do a live migration
(suspend/resume) the systemd-resolve doesn't work. i should restart the
daemon.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@mquiros: Where can I download the autofirma package? I just ran into
another source of certificates that have the same issue and I want to
investigate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in
Even though comment #2 claims that this bug is not related to bug
1764848 it may actually be related to bug 1764848. It depends on the
content of the autofirma package that apparently triggers this
situation, it may be that the package contains duplicate certificates.
--
You received this bug
I noticed that the OP had VirtualBox installed, same for me. This taints
the kernel ...
Are people who posted about going back to the old kernel using VBox?
So, re-installing 'VirtualBox' and ubuntu package 'menu' worked for me,
and keeping the new kernel
Suggest "dmesg | grep vbox" (YMMV)
I
How to get fix for Bionic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1824804
Title:
Unattended upgrades falls back to adjust all upgradable packages in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
1. Ubuntu 19.04
2. HP Deskjet 400, hpcups 3.19.3
Examine the file obtained in the previous step by running the command
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cups 2.2.10-4
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic
** Attachment added: "pdf"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826395/+attachment/5259000/+files/0425-0430.pdf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
I forwarded the proposed kbd fix upstream:
https://lists.altlinux.org/pipermail/kbd/2019-April/000653.html
** Changed in: kbd (Ubuntu Eoan)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
*** This bug is a duplicate of bug 1260041 ***
https://bugs.launchpad.net/bugs/1260041
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
Public bug reported:
Reported upstream as https://github.com/systemd/systemd/issues/10118
Ubuntu bionic, systemd version 237-3ubuntu10.19
When systemd-networkd is used to manage network bonds, upon systemd-
networkd, bonds are brought down for ~10 seconds affecting connectivity
to the server.
@jarnos #61
this is a separate issue fixed later, calculating upgradable packages leaves
the upgradable packages in the cache, and u-u counts them as the reverse
dependencies of the first kernel to be removed.
This keeps the first kernel on the system, but when there are no upgradable
packages
The verification of the Stable Release Update for shadow 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
This bug was fixed in the package shadow - 1:4.2-3.1ubuntu5.4
---
shadow (1:4.2-3.1ubuntu5.4) xenial; urgency=medium
* patches/1012_extrausers_chfn.patch:
- add --extrausers option to "chfn" (LP: #1495580)
* debian/patches/1013_extrausers_deluser.patch:
- add --extrausers
This bug was fixed in the package shadow - 1:4.2-3.1ubuntu5.4
---
shadow (1:4.2-3.1ubuntu5.4) xenial; urgency=medium
* patches/1012_extrausers_chfn.patch:
- add --extrausers option to "chfn" (LP: #1495580)
* debian/patches/1013_extrausers_deluser.patch:
- add --extrausers
1 - 100 of 118 matches
Mail list logo