*** This bug is a duplicate of bug 1792575 ***
https://bugs.launchpad.net/bugs/1792575
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 1792575
Boot failure with efi shims from 20180913.0
--
You received this bug notification because you are a member
You have extra spaces in /etc/default/grub when you changed
GRUB_CMDLINE_DEFAULT:
GRUB_CMDLINE_LINUX_DEFAULT = ""
There shouldn't be spaces around the =.
Closing as Invalid since this isn't a bug in grub.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug
ged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792262
Title:
package
A patch is attached, and it's a well-defined problem. Just needs that I
take the patch and test that it behaves correctly to land it.
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification
This isn't a security issue.
You may have unsigned kernels on your system, but we're planning to have
grub enforce signed kernels if Secure Boot is enabled -- therefore we
need to catch the case where no kernel is appropriately signed by a key
that is known to the firmware or to shim.
There's
: mokutil (Ubuntu)
Importance: Undecided => High
** Changed in: mokutil (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Not a kernel bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790586
Title:
The proposed grub package in Trusty / Bionic
My guess is lodygin fails to boot from the network, and cycles all the
way to booting from Hard drive (0004), in which case, since shim and
everything really /are/ installed on disk, it gets run to recreate the
missing "ubuntu" entry.
Assuming you can reproduce this issue easily, can you check if
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787630
Title:
Include HTTP
I disagree. This needs to be fixed in Debian as well -- none of the
options are crazy hacks, they are taken as explicit decisions meant to
fix actual problems that people are having.
I have to rebase the patches for Debian, sure; but I don't think we
should leave breadcrumbs around because a test
How is this system installed?
Shim 15 works quite well here to chainload Windows or boot to grub in
cosmic, and isn't yet available to users in other releases of Ubuntu.
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783044
Title:
grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (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/1780598
Title:
grub
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: grub2 (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/1768312
Title:
Not a bug in ubiquity or grub2. This will need changes in debian-cd (if
I'm not mistaken) in how we generate the menu for live CDs.
** No longer affects: ubiquity (Ubuntu)
** Also affects: debian-cd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: debian-cd (Ubuntu)
Sadly, I looked into that already, and we don't have that option: the
firmware does not let us know that it really didn't create the entry.
Closing as "Invalid" since the issue was reportedly fixed by disabling
Boot Order Lock.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You
Should be fixed in 2.02~beta3-4ubuntu7.3; the flashing should be solved
which should be avoiding the crashes (which are likely due to the
graphics card really not liking the flickering).
Can you please confirm whether updating to the new pacakge fixes the
problem?
Can you reach a good menu by
This is likely a duplicate of
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1758447
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762862
Title:
Install with encrypted lvm on reboot gives
What filesystem did you use to install? Is it possible that you picked
XFS or another filesystem other than Ext2/3/4 ?
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1258597 ***
https://bugs.launchpad.net/bugs/1258597
Fix Released: this was fixed in grub2 2.02-2ubuntu12 (in cosmic), and
the work is tracked in bug https://bugs.launchpad.net/bugs/1258597
** This bug has been marked a duplicate of bug 1258597
[Patch]
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763151
Title:
Triaged:
xfs is clearly not on the list of modules included in signed images, and
there's a very solid point in making sure the images we ship include all
the filesystems we support at install time (zfs is even listed).
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in:
AFAIK, grub-installer (the udeb package) already has logic to install
correctly on RAID systems, by using the underlying devices. This should
be writing grub-*/install-devices as well, which should be taking care
of package upgrades.
diskfilter writes not being supported in grub is certainly not
This is possibly a firmware issue, seeing as the default state for grub
as provided by maas/curtin config should be to skip modifying nvram.
However, how is the system booting in general? Was BootOrder really set
to booting to the network first? If it's set to other devices, and the
other device
This would be an enhancement request.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Landed in grub2 2.02+dfsg1-5ubuntu5.
** Changed in: grub2 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754586
Title:
[FFe request] Enable booting
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Also affects: grub2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Xenial)
Status: New => Triaged
** Changed in:
Could you check in the devices' firmware Setup utility, if there is a
feature called "Boot Order Lock" that is enabled?
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Closing as Fix Released:
grub2 (2.02~beta3-4ubuntu7.3) artful; urgency=medium
* Drop debian/patches/mkconfig_keep_native_term_active.patch, which can
lead to flickering between graphical and text mode when traversing the
menu. (LP: #1752767)
** Changed in: grub2 (Ubuntu)
Are the disks changing in any way? Is this a Dell system? A Lenovo
system?
This has the earmarks of a firmware issue, where the BootEntry variables
are lost -- the system will then try to boot straight to disk, fail to
find a valid boot image, and be stuck; all this possibly because it
manages to
What are you attempting to do as the time? Is this an upgrade to a new
release of Ubuntu?
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The menu looks about the way it should look, except for what appears
likely to be issues with the screen that displays the menu (the small
sections of black that mess with the text and the lines on top).
Could you please further describe what you see as being the problem?
** Changed in: grub2
*** This bug is a duplicate of bug 1258597 ***
https://bugs.launchpad.net/bugs/1258597
We fixed this recently; this is effectively a duplicate of bug 1258597.
** This bug has been marked a duplicate of bug 1258597
[Patch] Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT
How was this system installed? Was it installed in BIOS mode and then
changed to UEFI?
Is shim-signed correctly installed on the system? Without shim-signed
installed and present on the ESP partition
(/boot/efi/EFI/ubuntu/bootx64.efi); as well as listed as the BootEntry
to load (sudo efibootmgr
It looks like your /boot partition has run out of space. You will want
to remove old kernels ('sudo apt remove linux-image-')
then run 'sudo apt -f install' to finish the installation.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
We don't currently support this form of full-disk encryption without the
manual interventions you mentioned, and the installer currently sets up
encryption is a way that things will work.
Setting Triaged/Wishlist as this constitutes an obviously valid
enhancement request.
** Changed in: grub2
Assigning to linux to we can investigate whether this is caused by a
kernel bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
How was this system installed? Have the disks been replaced or changed
in some way since it was installed?
Could you please run the following command and attach its output to this
bug?
debconf-show grub-pc
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in:
Is this still reproducible? We have changed the default gfx mode to stay
"text" on EFI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720197
Title:
Every second(?) boot fails to display anything
Not a bug in shim, but we are adding a Breaks in shim-signed for the
purposes of SRUs to avoid people upgrading into a broken state. As such,
the task for cosmic in Invalid; but absolutely in progress / committed
for other releases.
** Changed in: shim-signed (Ubuntu)
Status: New =>
This does not appear to be a bug in shim at all, closing the shim tasks
as Invalid.
** Changed in: shim (Ubuntu)
Status: New => Invalid
** Changed in: shim (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
** Changed in: shim (Ubuntu Xenial)
Is this a crash that people are able to easily reproduce? I can't figure
out how to get that crash here, but I have a patch likely to fix the
issue (and the patch is necessary anyway).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1766872 ***
https://bugs.launchpad.net/bugs/1766872
It's not quite a duplicate, because this message appears before the
network option is even attempted -- it's a bug in the menu code; but
we'll mark it as a duplicate anyway as it's only really apparent when
: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768783
Title:
mtu is missing in doc reference (only mentioned in example)
To manage notificati
** Changed in: netplan.io (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768798
Title:
netplan try: terminal d
** Description changed:
- ## DRAFT ##
-
[Impact]
-
- "netplan ip leases " command is failing with a Traceback[1]
- when specifying an interface non-existing on the system. non-dhcp
- configured or non configured with netplan.
+ "netplan ip leases " command is failing with a Traceback[1] when
** Description changed:
+ [Impact]
+ Netplan documentation
+
+ [Test case]
+ 1) Run 'man netplan'
+ 2) Validate that the documentation contains a correctly spelled parameter
"gratuitous-arp".
+
+ [Regression potential]
+ This is a documentation-only fix. Watch out for documentation that fails
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771440
Title:
"//" at beginning of YAML file path when error in network config
** Changed in: netplan
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771704
Title:
support for ipv4 link-local addressing
To manage notifications about
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Released
** Description changed:
+ [Impact]
+ All Ubuntu users.
+
+ [Test case]
+ 1) Look at the netplan manpage:
+
+ man netplan
+
+ 2) Verify that
netplan.io 0.40 in cosmic contains this fix.
** Description changed:
+ [Impact]
+ Users configuring IPv6 static address with NetworkManager as a backend.
+
+ [Test cases]
+ 1) Configure netplan for static addresses for IPv6, dns settings, but no IPv4
configuration:
+
+ [...]
+ ens8:
+
netplan.io 0.40 landed in cosmic.
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793309
Title:
Backport netplan.io 0.40
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Released
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
[Impact]
All users of Ubuntu with network configurations using netplan.yaml.
[Test case]
+ 1) Configure network via netplan.yaml for the feature one wants to verify.
+
+ Individual bugs have been opened for separate bugs fixed / features
+ added.
+
+ 1) Run
** Description changed:
+ [Impact]
+ Netplan users setting up bridges.
+
+ [Test cases]
+ 1) Add a new bridge configuration in netplan yaml, without an IP address set:
+
+ [...]
+ bridges:
+ br0:
+ interfaces: [ interface ]
+ dhcp4: false
+ parameters:
+
** Changed in: netplan
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736975
Title:
netplan does not bring up anonymous bridge on boot
To manage
** Description changed:
+ [Impact]
+ netplan.io users who define custom routes
+
+ [Test case]
+ 1) Configure netplan.
+ 2) Add a route:
+ [...]
+ routes:
+ - to: 10.10.10.0/24
+ scope: link
+
+ 3) Validate that the route is correctly added to the routing table
+ (using 'sudo ip
** Description changed:
+ [Impact]
+ All netplan users.
+
+ [Test case]
+ 1) Run 'sudo netplan try' to "try" a new netplan config.
+ 2) Hit Control-C during the timer, to escape to the terminal without applying
the configuration.
+
+ Validate that text typed on the terminal after hitting
** Description changed:
+ [Impact]
+ Ubuntu users who make use of IPv4 link-local addresses.
+
+ [Test case]
+ 1) Add 'link-local: [ ipv4 ]' to the netplan configuration.
+ 2) Run 'sudo netplan apply'
+
+ [Regression Potential]
+ Enabling link local means additional addresses are available on
** Description changed:
+ [Impact]
+ Ubuntu users configuring a custom umask on their system
+
+ [Test case]
+ 1) set UMASK in /etc/login.defs to 077
+ 2) Configure netplan to use the networkd renderer, run 'sudo netplan apply'.
+ 3) Verify that systemd-network applies the correct network
** Description changed:
+ [Impact]
+ Chainloading grub via grub in a netboot context using MAAS's Boot to local
disk feature.
+
+ [Test cases]
+ 1) Deploy UEFI system using MAAS
+ 2) After deployment, have the system reboot to local disk (via netboot).
+
+ [Regression potential]
+ It is
Bug was confirmed fix, although we don't have a formal version number
for the pacakge that was tested, let's mark this verification-done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are
What is the status of this MIR? Is it still required to provide some
feature?
Changes were requested, they don't appear to be all done, but I wouldn't
necessarily block on needing to use something other than JAM if the
maintainability of the pacakge is good.
** Changed in: argyll (Ubuntu)
Desktop team NAKed maintaining it, and it looks like reverse-
dependencies would need changes (and for one, having written the nm-
applet patch, I rather this be removed to use standard status icon code
than appindicators). Setting to Incomplete.
If this needs to be in main to support software,
@Alan,
Can you confirm which version of plymouth you had installed?
You can use the following command to do so:
dpkg -l plymouth | cat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Sponsored the package.
Woodrow, for next SRU uploads like this (which is effectively a
backport), or for other SRUs, please update the version number to be
above the one already in the archive, but below the version number for
the next release. For example:
in bionic right now: 0.79-2build1
the
** Description changed:
[Impact]
All users of Ubuntu with network configurations using netplan.yaml.
[Test case]
[Regression potential]
-
---
Let's backport netplan.io 0.40 to bionic; as per policy for netplan.io
releases.
Given that it's a core component of the
Public bug reported:
[Impact]
All users of Ubuntu with network configurations using netplan.yaml.
[Test case]
[Regression potential]
---
Let's backport netplan.io 0.40 to bionic; as per policy for netplan.io
releases.
Given that it's a core component of the networking story, and new
That's not what I mean though. For SRU verification we should aim to
have a positive identification of the exact version of the plymouth
package that was used for the tests.
For example, this can be achieved by looking at 'dpkg -l plymouth |
cat':
要望=(U)不明/(I)インストール/(R)削除/(P)完全削除/(H)保持
|
@Alan, could you please confirm which version of plymouth you have
installed for the tests you did?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Login password from GDM is
Not a regression in shim -- shim is doing what it should, but exposes an
actual latent bug in the grub2 EFI patchset. This is still in progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790724
This is identified as a proper "typo" bug in grub, fixing.
** Description changed:
+ [Impact]
+ Dual-boot installs of Ubuntu and Windows 10, and other instances of
chainloading another bootloader from grub2.
+
+ [Test cases]
+ 1) Install Windows 10
+ 2) Install Ubuntu in a dual-boot setup with
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Triaged
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785493
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage
* Changed in: shim (Ubuntu Bionic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when Secure Bo
We rolled back shim; this would now be regression-proposed.
** Changed in: shim-signed (Ubuntu)
Status: New => Triaged
** Changed in: shim-signed (Ubuntu)
Importance: Undecided => Critical
** Changed in: shim-signed (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel
The package versions we need are for grub-efi-amd64 and grub-efi-
amd64-signed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage
So, the patch would apply, but you're not seeing the error messages that
I expect you should be seeing if that was the problem. We can certainly
try to apply the patch (I will make it available in a PPA), but I'm not
sure that will help.
For one thing, you are using the same grub in both cases,
** Changed in: gpsd (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
** Changed in: gpsd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
until the
package's lintian warnings are fixed and the package modernized to use /
provide python3 bindings instead of python2; and a clear list of the
binary packages to be promoted.
--
Mathieu Trudel-Lapierre
Freenode: cyphermox, Jabber: mathieu...@gmail.com
4096R/65B58DA1 818A D123 0992 275B 23C2
Public bug reported:
Shim 15+1533136590.3beb971-0ubuntu1
MokSBStateRT isn't on /sys/firmware/efi/efivars when validation is
disabled.
** Affects: shim (Ubuntu)
Importance: High
Status: New
** Changed in: shim (Ubuntu)
Importance: Undecided => High
--
You received this bug
** Tags removed: verification-needed verification-needed-bionic
verification-needed-trusty verification-needed-xenial
** Tags added: verification-done-bionic verification-done-trusty
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
There does not appear to be a patch attached? What do you need
sponsored?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789786
Title:
SRU ledmon into Bionic
To manage notifications about this bug
nical Foundations Team (canonical-foundations) => Mathieu
Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Login password from GDM is shown in plain text on t
Rebuilds in PPA have all passed -- the failures for efitools are exactly
the same as they previously were and due to EFI not being available (or
sbsigntool, efivar, etc.) on those architectures:
https://launchpad.net/~cyphermox/+archive/ubuntu/rebuild-tests/+packages
In any case, amd64 (the only
Verification-done for shim, shim-signed on bionic:
shim 15+1533136590.3beb971-0ubuntu1
shim-signed 1.37~18.04.1+15+1533136590.3beb971-0ubuntu1
System is booting as expected with the new shim, and mokutil allows for
importing a certificate and enabling validation at the same time (or any
multiple
This confirms the system boots and is in Secure Boot mode. Do you have
time to run through the other test cases using mokutil?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708245
Title:
shim
Verification-done on bionic with initramfs-tools 0.130ubuntu3.3:
Verified that with the SRU applied, the initramfs configured to use
MODULES=dep can still determine that the root is over ZFS, and
accordingly add the files needed in the initramfs.
** Description changed:
[Impact]
- Ubuntu
Verification-done for bionic with initramfs-tools 0.130ubuntu3.3:
Verified that at boot the system does get the additional config for
netplan in /run/netplan and that it forces systemd-networkd not to
release the IP lease.
** Tags removed: verification-needed verification-needed-artful
: Undecided
Status: New
** Changed in: grub2 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: grub2-signed (Ubuntu Bionic)
Status: New => In Progress
** Changed in: grub2-signed (Ubuntu Bionic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Fix Committed
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785033
Title:
GRUB needs to support 64-bit efi linear frame buffer
shim and shim-signed 15 / 1.37 are already in Cosmic.
** Also affects: shim (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: shim (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: shim (Ubuntu Cosmic)
Importance: Undecided
Status:
** Description changed:
[Impact]
All users on UEFI systems.
Gnu-efi needs to be backported everywhere to support new shim releases.
This applies to bionic, xenial, and trusty.
This is to properly build the new shim releases on these releases of
Ubuntu.
-
[Test cases]
--
Public bug reported:
[Impact]
All UEFI users.
[Test case]
== shim ==
1) Enable Secure Boot in firmware.
2) Update to new shim and shim-signed packages (shim 15+, shim-signed 1.37~)
3) Validate that the system still boots and validates the shim image as well as
the grub binary.
== MokManager
lso affects: syslinux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: syslinux (Ubuntu)
Status: New => In Progress
** Changed in: syslinux (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: syslinux (Ubuntu)
I
701 - 800 of 8811 matches
Mail list logo
