This appears to still be unresolved. What are the next steps? Do we
still want to add a Pre-Depends? How will d-i and image builds be
verified to not regress?
** Changed in: sysvinit (Ubuntu Xenial)
Status: In Progress => Triaged
** Changed in: sysvinit (Ubuntu Xenial)
Assignee: Steve
For Xenial we're currently blocked on some kernel work that needs to
happen before we enable enforcement for that release in grub2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401532
Title:
GRUB'
** Changed in: shim-signed (Ubuntu)
Status: New => Triaged
** Changed in: shim-signed (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829029
Title:
This is a more complex issue; it's not just about LXD, but the general
story for installing "minimal" installs.
The fact that openssh-server was not installed as part of the ubuntu-
server is a separate bug we've covered in a different bug report.
Currently, desktops allow picking a "full" instal
I have a similar issue on Debian 9 (Stretch) on a Lenovo X1 Carbon 6th
Gen laptop.
DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET63W (1.38 ) 04/20/2019
The built-in speaker volume is limited to about 20% even if the volume
is set at 100%.
The sound card is a ALC285 handled by the snd_hda_intel dr
I don't think it's *-control-center.
At the time, that was filed there by pitti, who correctly pointed out
that something might need to depend on libnss-myhostname (from systemd)
for a fallback to resolving hostname via just /etc/hostname (since
/etc/hosts isn't changed). At this point though, it
Public bug reported:
https://github.com/CanonicalLtd/netplan/blob/ea47bd4e1c5319b1a624ea61c843ee96e7c128da/src/networkd.c#L208
The separator used to add multiple ARP IP targets for the networkd
renderer is ",".
Unfortunately, networkd doesn't allow that, but rather expects
whitespace:
(in confi
** Changed in: ubiquity (Ubuntu Wily)
Status: Triaged => Won't Fix
** Package changed: ubiquity (Ubuntu) => partman-auto (Ubuntu)
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Tags removed: rls-x-incoming
** Tags added: rls-ee-incoming
** Also affects: gnome-control-center (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unity-control-center (Ubuntu Xeni
I believe we've fixed this already, especially since it is a bug that
was reported prior to the release of 16.04. We do have developers who
routinely use dvorak for keymap and would otherwise not have been able
to login to their systems.
Reassigning to console-setup, since it is the most likely cu
I'll sponsor this patch.
Please follow the steps at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure to update the bug
description for SRUing this to bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Autopkgtests are passing (linked above); marking this verification-done.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-disco
** Tags added: verification-done-bionic verification-done-cosmic
verification-done-disco
--
You received
Seems like this would still apply to Eoan, marking rls-ee-tracking
** Tags removed: rls-x-incoming
** Tags added: rls-ee-tracking
** Changed in: isc-dhcp (Ubuntu)
Status: Confirmed => Triaged
** Also affects: isc-dhcp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also af
** Description changed:
[Impact]
This release contains both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
-* [d96a6a0] networkd: force bringing up devices with no IP addresses
-
Verification-done for disco:
ubuntu@right-elf:~$ lsb_release -cs
disco
ubuntu@right-elf:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.97-0ubuntu1~19.04.1 amd64YAML network
configuration abstraction for various backends
ubuntu@right-elf:~$ cat /etc/netplan/50-cloud-init.yaml
# This
Verification-done on cosmic:
ubuntu@brave-elf:~$ lsb_release -cs
cosmic
ubuntu@brave-elf:~$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configurati
** Also affects: gucharmap (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828884
Title:
[META] Handling Japanese ne
mozc appears to already be Fix Released for most releases; this has been
handled as bug 1823444.
** Description changed:
[Background]
Many packages are affected by the requirement to support the new era "Reiwa"
(令和）
This is the meta bug to track packages that need fixes; which packages
libreoffice SRUs appear to be handled in bug 1827451.
** Changed in: libreoffice (Ubuntu)
Status: New => In Progress
** Changed in: libreoffice-l10n (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
[Background]
Many packages are affected by the requirement to support the new era "Reiwa"
(令和）
This is the meta bug to track packages that need fixes; which packages
have already been SRUd to previous releases, how to prioritize the work
needed, and general test cases for ve
Is this really a sufficient test case? It seems to me like there should
be extra work put in to making sure the glyphs also appear correctly on
date formatting, to show, for example:
令和１年５月１日
Which is achieved by setting the Cell Format appropriately, in the same
way as above.
--
You received t
@Lars, thanks!
Marking verification-done-bionic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763608
Title:
Ne
So; this has landed in Eoan now, and also in -proposed repositories for
18.04, 18.10, 19.04. I'll start doing testing on these releases, but
since I don't have an openvswitch setup, any and all further independent
confirmation that the issue is fixed (or indeed, if it's not), is
welcome.
--
You r
This is still verification-done; has not changed in releases: this SRU
is a backport that includes the same upstream patch as what was
previously cherry-picked in the previous round of SRUs; hence it
appearing again in changelog.
** Tags removed: verification-needed verification-needed-bionic
ver
default renderer when
multiple files specify it globally (LP: #1825206)
- Fixed networkd activation. (LP: #1821867)
* Drop all patches; they are included in the upstream release.
-- Mathieu Trudel-Lapierre Wed, 08 May 2019
16:50:13 -0400
** Changed in: netplan.io (Ubuntu)
Status
Public bug reported:
[Impact]
This release contains both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
* [d96a6a0] networkd: force bringing up devices with no IP addresses
(LP: #1763608)
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Critical
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Description changed:
+ [Impact]
+ Netplan u
I am still unable to reproduce this failure case. I don't know what else
to try.
I'm leaving this open so I can discuss this with other developers; but
I'll leave the bug aside for now so we can get back to it and have a way
to track this issue if we manage to find something that needs fixing in
t
This is still verification-done for bionic and cosmic:
netplan.io/0.96-0ubuntu0.18.04.4
netplan.io/0.96-0ubuntu0.18.10.3
Confirmed that this is still working as expected with the new SRUs after
quickly re-verifying given the changes uploaded to fix the regression in
bug #1825206.
** Tags remov
Still verification-done on bionic and cosmic; this hasn't changed with
the new revision in -proposed.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification
Still verification-done on bionic and cosmic; this hasn't changed with
the new revision in -proposed.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification
Still verification-done on bionic and cosmic; this hasn't changed with
the new revision in -proposed.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification
Verification-done for cosmic:
ubuntu@ip-172-30-0-50:~$ lsb_release -cs
cosmic
ubuntu@ip-172-30-0-50:~$ apt policy netplan.io
netplan.io:
Installed: 0.96-0ubuntu0.18.10.3
Candidate: 0.96-0ubuntu0.18.10.3
Version table:
*** 0.96-0ubuntu0.18.10.3 500
500 http://us-east-1.ec2.archive.ub
Verification-done for bionic:
ubuntu@ip-172-30-0-32:~$ lsb_release -cs
bionic
ubuntu@ip-172-30-0-32:~$ apt policy netplan.io
netplan.io:
Installed: 0.96-0ubuntu0.18.04.4
Candidate: 0.96-0ubuntu0.18.04.4
Version table:
*** 0.96-0ubuntu0.18.04.4 500
500 http://us-east-1.ec2.archive.ub
This is still verification-done for bionic and cosmic; re-upload was to
address a regression in choosing the renderer; but switching renderers
has been confirmed to cause files to be removed/ re-created and the
services restarted.
** Tags removed: verification-needed verification-needed-bionic
ve
Confirmed this is still unchanged for bionic and cosmic SRUs:
netplan.io/0.96-0ubuntu0.18.04.4
netplan.io/0.96-0ubuntu0.18.10.3
NetworkManager renderer works as expected; files are being written with
the .nmconnection suffix and work correctly.
** Tags removed: verification-needed verification-n
Verification-done for bionic:
After installing netplan 0.96-0ubuntu0.18.04.4 the wireless network on
my Thinkpad X230 is again available in Gnome-Shell's network drop-down
(you see the wifi icon); and 'nmcli dev' correctly reports wlp3s0 being
connected to a netplan-X connection.
** Tags remo
*** This bug is a duplicate of bug 1767570 ***
https://bugs.launchpad.net/bugs/1767570
** This bug has been marked a duplicate of bug 1767570
Could not delete variable: No space left on device (package shim-signed
1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
Is anyone still seeing this bug on their system?
If so, could you please run the following command so we can see what
might be causing the firmware space to get filled?
ls /sys/firmware/efi/efivars/
Then attach the output to this bug report.
We would like to know, for example, if there are "du
*** This bug is a duplicate of bug 1805490 ***
https://bugs.launchpad.net/bugs/1805490
** This bug is no longer a duplicate of bug 1767474
Could not delete variable: Invalid argument (package shim-signed
1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
post-inst
*** This bug is a duplicate of bug 1805490 ***
https://bugs.launchpad.net/bugs/1805490
** This bug is no longer a duplicate of bug 1767474
Could not delete variable: Invalid argument (package shim-signed
1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
post-inst
*** This bug is a duplicate of bug 1805490 ***
https://bugs.launchpad.net/bugs/1805490
** This bug has been marked a duplicate of bug 1805490
[master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required. / Could not delete variable: Invalid argument
*** This bug is a duplicate of bug 1805490 ***
https://bugs.launchpad.net/bugs/1805490
** This bug is no longer a duplicate of bug 1767474
Could not delete variable: Invalid argument (package shim-signed
1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
post-inst
** Summary changed:
- [master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required."
+ [master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required. / Could not delete variable: Invalid argument"
--
You received
** Package changed: grub2 (Ubuntu) => efibootmgr (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509660
Title:
Fails to upgrade: `efibootmgr: Could not add entry to BootOrder: No
space lef
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug is no longer a duplicate of bug 1805490
[master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required."
** This bug has been marked a duplicate of bug
** This bug is no longer a duplicate of bug 1805490
[master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required."
** Summary changed:
- package grub-efi-amd64-signed 1.93.8+2.02-2ubuntu8.7 failed to
install/upgrade: 'efibootmgr failed to register the
I've had a look, certainly seems fine packaging-wise; but should be
looked at by the Security Team.
** Changed in: libheif (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Public bug reported:
# Steps to reproduce
- Install a fresh Lubuntu 19.04 in a virtual machine,
- optionally, read Bug #1827433 to be aware of the OK button problem,
- create an empty file on the desktop,
- right-click on the file>Open With...> Other Applications,
- click on the "Custom Command"
** Description changed:
# Steps to reproduce
- Install Lubuntu 19.04 in a virtual machine,
- create an empty file on the desktop,
- right-click on the file>Open With...> Other Applications,
- click on the "Custom Command" tab of the "Choose an Application" window,
- write "vim" in t
Setting back to verification-done; this is still verified for bionic and
cosmic (no change with new revision in -proposed).
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received
Setting back to verification-done; this is still verified for bionic and
cosmic (no change with new revision in -proposed).
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verificati
Setting back to verification-done; this is still verified for bionic and
cosmic (no change with new revision in -proposed).
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received
Setting back to verification-done; this is still verified for bionic and
cosmic (no change with new revision in -proposed).
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received
Public bug reported:
# Steps to reproduce
- Install Lubuntu 19.04 in a virtual machine,
- create an empty file on the desktop,
- right-click on the file>Open With...> Other Applications,
- click on the "Custom Command" tab of the "Choose an Application" window,
- write "vim" in the "Command line
I'm unable to reproduce this on an X230 or T450s. I would have thought
the firmware to be pretty similar, at least enough that I could see this
issue when a similar config is applied.
This needs more investigation in the code for the console module. I've
had a quick look, nothing obvious jumped ou
Public bug reported:
# Steps to reproduce
- Install a fresh Lubuntu 19.04,
- from the desktop, press the Super key (Windows key) to open the application
menu,
- press the "Up" key to go up in the menu.
# Expected results
The cursor which is blinking in the search field should go up to "Lock
Sc
This hasn't changed in bionic or cosmic; previously released SRU which
is again included in the changelog for this backport.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You receive
Setting back to verification-done; tests are still passing for
test_terminal, as per the above comments.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notificat
systemd's wpa-* job does not require verifying again; this will not have
changed in this new SRU. Marking verification-done again for bionic and
cosmic.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-
Public bug reported:
# Steps to reproduce
After a fresh Lubuntu 19.04 installation in a virtual machine:
- create an empty file on the desktop,
- right-click on the file>Properties>General>Open With: Vim>OK,
- double click on the file.
# Expected results
Double-clicking on the file should open
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: grub2 (Ubuntu)
Status: New => Fix Re
Thanks! Marking verification-done-xenial since it's been confirmed to
fix the issue.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Description changed:
- * Impact
+ [Impact]
+ When using a VPN the DNS requests might still be sent to a DNS server outside
the VPN when they should not
- When using a VPN the DNS requests might still be sent to a DNS server
- outside the VPN when they should not
+ [Test case]
+ 1) Set up a
Verification-done for cosmic:
I've installed from mini.iso to get an Ubuntu Desktop; both
01-netcfg.yaml and 01-network-manager-all.yaml are present on disk as
expected. After installing netplan.io 0.96-0ubuntu0.18.10.3 I can see
the netplan-* connection from the installer in the Gnome Shell dropd
Hi Dexuan,
You might want to try this again. There were some delays in completely
processing all the required files for this SRU, which may have
translated in it not being available when you tried.
Judging from deploying a VM here with bionic-proposed enabled, it should
be available now:
ubuntu@
Marc;
Thanks for the quick turnaround testing this. We don't always have bug
reporters going back to test the changes once we upload changes to
-proposed. It's much appreciated.
I'll take care of testing this on bionic and cosmic.
Marking verification-done-disco since the original bug reporter v
** Description changed:
+ [Impact]
+ Ubuntu users installing from the d-i installer (mini.iso) to set up a
desktop, as well as users with complex setups for netplan, managed by both
networkd and NetworkManager in multiple files.
+
+ [Test case]
+ 1) Install ubuntu from mini.iso.
+ 2) Configure
lt
(https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/commit/?id=38d9e2f862a96a039ae8ca8b87b8615d154ceda4).
I'm asking the patch author (Mathieu Trudel-Lapierre) to submit the
patch to the upstream grub and this is the upstream bug link:
https://savannah.gnu.org/bugs/?56217 .
Here this laun
There is now also another feature available in newer netplan versions
(0.96 and above, in progress SRU for bionic and above, so it should be
available soon on all supported releases...).
With this, you'd be able to use "dhcp4-overrides" to specify what metric
to use for routes, and whether or not
Changed in: grub2 (Ubuntu)
Status: New => Fix Released
** Changed in: grub2 (Ubuntu Xenial)
Status: New => In Progress
** Changed in: grub2 (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: grub2 (Ubuntu Xenial)
Importance:
Marking Fix Released for other releases; the patch is already provided
in Bionic and above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826453
Title:
Grub2 Booting in blind mode due to "invalid v
Started experiencing this in Ubuntu 18.04 on two different computers,
since a few days ago, presumably because of a package upgrade ; both
users are using the Unity shell (if it makes any difference; I didn't
try another one) ; disabling those shortcuts is important because
Alt+arrow are very commo
Public bug reported:
Upgrade error during update to Ubuntu 19.04
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: spamassassin 3.4.2-1
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpa
Thanks, I think we have all the information we need right now; this
needs further investigation by a developer.
** Changed in: efibootmgr (Ubuntu Disco)
Status: Incomplete => Triaged
** Changed in: efibootmgr (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notifica
: uwsgi (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820227
Title:
[MIR] uwsgi as dependency of m
After additional testing with hardware (instead of in VMs), it looks
like things are working fine on Lenovo hardware.
I managed to get access to a Lenovo SR670 server. I deployed it from an
existing MAAS, along with a second server (some random node we'll call
http-server) to be an HTTP server, si
Alright; I think I've finally made some progress on this.
Turns out "Block device required" is really a red herring. It's some
random value (15) used in efibootmgr code, for any number of causes for
failure. We can't read anything into it.
The real error in indeed "Invalid argument", and very muc
Please read this until the end before commenting. I am closing this bug
as "Invalid", because we can't deal with the many different types of
problems seen by people all on this same bug report.
This is, for most users, a firmware issue (in which case, if you're running a
Dell laptop, please chec
In addition to the above; if anyone has previously had Ubuntu 17.10
installed on the affected system, it is possible this is due to bug
1734147. Please see if the bug's description matched with what you are
seeing. If you're unsure, ask here for help.
--
You received this bug notification because
syslinux 3:6.04~git20171011.af7e95c3+dfsg1-4ubuntu1.18.10.2
verification-done in cosmic:
I've build new d-i images (mini.iso for netboot) in a PPA with the use
of the new syslinux in cosmic-proposed; the images were bootable and
correctly showing the minimal gfxboot menu expected for mini.iso.
So
Verification-done on cosmic with partman-efi/71ubuntu4.1:
Starting a d-i install with proposed enabled; with partman-efi installed
in the d-i environment; I could verify that using manual partitioning
and omitting to create an ESP in UEFI mode leads to showing the error
message and blocking the us
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Triaged
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1681
The system booted, so it's not a syslinux issue. Maybe kernel? I'm
unsure, as I didn't see anything obviously wrong (to me) in the attached
logs, but the mtrr messages are unusual and warrant some further
investigation.
Reassigning to linux.
** Package changed: syslinux (Ubuntu) => linux (Ubuntu)
This appears to work here; if I start with the screen reader enabled in the
isolinux splash (F5,
hit arrow down three times, enter).
** Changed in: casper (Ubuntu Disco)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Okay, this bug has absolutely nothing to do with grub or netplan.
Changing the renderer couldn't possibly affect the behavior of X, and
the grub configuration looks, at a glace, to be run-of-the mill; pretty
much default if you disregard that there is any number of different
installs on the system.
I'm not sure changing anything is casper will address this. Aren't the
nvidia drivers only installed towards the "end" of the installation
process, since they wouldn't be available at boot time for the live
image? AFAIK they aren't even shipped on the images.
--
You received this bug notification
Verification-done trusty:
ubuntu@profound-donkey:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.6 LTS
Release:14.04
Codename: trusty
ubuntu@profound-donkey:~$ sudo apt install shim-signed
Reading package lists... Done
Building depe
Verification-done for xenial:
ubuntu@noted-fish:~$ sudo apt install shim-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
sbsigntool
The following packages will be upgraded:
sbsigntool sh
This hasn't changed in bionic; previously released SRU which is again
included in the changelog for this backport.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This does not need re-testing, already in bionic/cosmic, just closed
again due to changelog for this big backport.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
301 - 400 of 10796 matches
Mail list logo
