Ho do I install it?
-Download file
-extract
-cd into the folder
-command line: make
thats all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788727
Title:
upgrade crashing due to unsigned kernels
This bug was fixed in the package grub2 - 2.02-2ubuntu8.9
---
grub2 (2.02-2ubuntu8.9) bionic; urgency=medium
[ Mathieu Trudel-Lapierre ]
* debian/default/grub.md5sum: add entry for 2.02-2ubuntu8.7; to force an
update of /etc/default/grub back to the correct timeout value of 0
This bug was fixed in the package grub2-signed - 1.93.10
---
grub2-signed (1.93.10) bionic; urgency=medium
* Rebuild against grub2 2.02-2ubuntu8.9 (LP: #1784363) (LP: #1788727)
-- Mathieu Trudel-Lapierre Thu, 08 Nov 2018
10:54:58 -0500
** Changed in: grub2-signed (Ubuntu Bionic
I also did receive an unsigned kernels dialog when I had a unsigned
version of vmlinuz-4.10.0-28-generic installed.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
** Attachment added: "grub2-proposed.png"
https://bugs.
I verified that an upgrade from Ubuntu 16.04 to Ubuntu 18.04 is possible
(and that grub did not bail) with -proposed enabled when the kernel you
are running also has an .efi.signed file in boot i.e I was running the
4.4.0-139-generic image.
--
You received this bug notification because you are a
Hi. Could someone please help me with updating my Ubuntu? I've received
these errors.
I'm not a software developer and pretty new to Linux so simple
explanations are appreciated.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: grub2 (Ubuntu)
Assignee: Steve figueroa (homecompsg) => (unassigned)
** Changed in: grub2 (Ubuntu Bionic)
Assignee: Steve figueroa (homecompsg) => (unassigned)
** Changed in: grub2 (Ubuntu Cosmic)
Assignee: Steve figueroa (homecompsg) => (unassigned)
** Changed in:
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Steve figueroa (homecompsg)
** Changed in: grub2 (Ubuntu Bionic)
Assignee: (unassigned) => Steve figueroa (homecompsg)
** Changed in: grub2 (Ubuntu Cosmic)
Assignee: (unassigned) => Steve figueroa (homecompsg)
** Changed in:
Hello Al, or anyone else affected,
Accepted grub2 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.9
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
** Changed in: grub2 (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: grub2-signed (Ubuntu Bionic)
Status: New => 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/1
** Changed in: grub2-signed (Ubuntu Cosmic)
Status: New => Fix Released
** Changed in: grub2-signed (Ubuntu)
Status: New => 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/178
** Tags added: id-5bdb73bc573ea205340525bc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788727
Title:
upgrade crashing due to unsigned kernels
To manage notifications about this bug go to:
https:
** 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/1788727
Title:
upgrade crashing due to unsigned kernels
To manage no
I have marked this a regression-update since the behavior was introduced
on bionic in SRU via grub2 2.02-2ubuntu8.3 post-release, and impacts all
upgrades from xenial to bionic for secureboot-enabled systems.
** Tags added: regression-update
--
You received this bug notification because you are
The overall plan is that we ARE updating the bootloader, across all
supported Ubuntu releases, to no longer boot unsigned kernels. In
various places the upgrade handling to report problems with unsigned
kernels has landed before the actual change to the bootloader. This is
correct, we certainly wo
Shouldn't this new Ubuntu bootloader refuse to boot unsigned kernels, is
this refusal to boot not implemented yet or I understood its goal
incorrectly?
In the current state it seems to have no benefits, as I can boot any
kernel I want from Ubuntu's bootloader, and cause a lot of trouble with
the f
Those kernels are absolutely not going to be signed with the Ubuntu
archive Secure Boot key. They are a separate security domain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788727
Title:
upgrad
Maybe signing the mainline kernels (kernel.ubuntu.com/~kernel-
ppa/mainline/) could prevent this happening for some users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788727
Title:
upgrade crashi
** Changed in: grub2 (Ubuntu Bionic)
Assignee: Sarath P Nath (sarathpnath) => (unassigned)
** Changed in: grub2 (Ubuntu Cosmic)
Assignee: Sarath P Nath (sarathpnath) => (unassigned)
** Changed in: grub2 (Ubuntu Bionic)
Status: Fix Released => Triaged
--
You received this bug no
** Changed in: grub2 (Ubuntu Bionic)
Assignee: (unassigned) => Sarath P Nath (sarathpnath)
** Changed in: grub2 (Ubuntu Cosmic)
Assignee: (unassigned) => Sarath P Nath (sarathpnath)
** Changed in: grub2 (Ubuntu Bionic)
Status: Triaged => Fix Released
--
You received this bug no
** Changed in: grub2 (Ubuntu Bionic)
Status: New => Triaged
** Changed in: grub2 (Ubuntu Cosmic)
Assignee: ali reza (alirezasabb) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Changed in: grub2 (Ubuntu Cosmic)
Assignee: (unassigned) => ali reza (alirezasabb)
** Changed in: grub2 (Ubuntu Bionic)
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Please take me off this list. I have already loaded a new copy of 18.04
wiping out the upgrade.
Thanks
Bob Colquhoun
On 09/10/18 08:54, Launchpad Bug Tracker wrote:
> This bug was fixed in the package grub2 - 2.02+dfsg1-5ubuntu6
>
> ---
> grub2 (2.02+dfsg1-5ubuntu6) cosmic; urgency
This bug was fixed in the package grub2 - 2.02+dfsg1-5ubuntu6
---
grub2 (2.02+dfsg1-5ubuntu6) cosmic; urgency=medium
[ Steve Langasek ]
* debian/grub-check-signatures: Handle the case where we have unsigned
vmlinuz and signed vmlinuz.efi.signed. (LP: #1788727)
-- Mathieu Tru
We'll at least address the upgrade process when the same kernel version
exists in both the vmlinuz file, and the vmlinuz.efi.signed file. We
shouldn't fail and thing this is an unsigned kernel when there's
obviously a signed copy of it also on disk, and grub config will use the
.efi.signed version.
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 cle
Isn't this a big security issue?
On Tue, Oct 2, 2018 at 12:25 AM Steve Kowalik
wrote:
> I hit this last night, it didn't impact booting, but it did fail the
> upgrade, which I had to fix up post-reboot with dpkg --configure -a.
> This should not be necessary. The problem is the *running* kernel
I hit this last night, it didn't impact booting, but it did fail the
upgrade, which I had to fix up post-reboot with dpkg --configure -a.
This should not be necessary. The problem is the *running* kernel from
16.04 is unsigned, and that is what the postinst complains about. I
would welcome an SRU t
The package shim-signed started to fail like this one in the latest
days. I have installed in my computer the following unsigned kernels:
drm-tip (4.19-rc4 with multiple patches);
4.18.6 (Ubuntu mainline)
4.18-rc1 (Ubuntu mainline)
4.17.19 (Ubuntu mainline)
4.17.18 (Ubuntu mainline)
4.17.18 (not a
Sandi, Answer to your last question first, I am a pensioner, I write
slow, make mistakes, (hence 20.18 should read 18.04), I need a good
spell checker, so I use writer to prepare what I want to say then I
paste it into the email, I must remember to paste as raw text in
future.
The computer that I
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => jai (dspace123)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788727
Title:
upgrade crashing due to unsigned kernels
To manage notifica
Forewarning, I began switching to Antergos one day after your post and
finished today, so I will not be able to provide any more hands-on data,
since Antergos is an Arch-based distribution (tried to install Arch in a
VM twice, failed both times). I switched because I was trying to make my
Ubuntu in
Sandi, I hope this is the correct procedure reporting via you. Thanks
for the email. My HP system seems a little different than yours, I
finished up with the two latest kernels and a warning that I also had
an old kernel that was not of the secure boot (efi) variety.
I deleted the old kernel, to f
Jim, I only know the GUI way of doing it. I select all of the kernels
above 4.15.xx and select remove, but only once I have booted up with the
older kernel (once the GRUB menu appears, go into Advanced options and
look for 4.15 and boot off of that, just don't select "(recovery
mode)"), type "apt a
To Sandi Vujakovic
Is it possible to send me an instruction that I can type into my computer.
I can copy and paste into terminal.
regards Jim Aird
On Fri, 7 Sep 2018 at 21:03, Sandi Vujaković <1788...@bugs.launchpad.net> wrote:
>
> The workaround that I have is removing all UKUU added/mainline kern
The workaround that I have is removing all UKUU added/mainline kernels,
finish configuring the grub packages, reinstall the latest mainline
kernel and be on my marry way.
If it installed unsigned versions alongside the signed ones, then the
UKUU kernels removed should have no effect on that. Also,
Having *any* unsigned kernel should not fail the upgrade process. At
best, a debconf warning should be presented.
** Changed in: grub2 (Ubuntu)
Status: Opinion => New
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a m
While it may be "by design," then the package system or something else
is broken "by design."
On a system that uses signed kernels, the unsigned versions of the same
kernels are also installed alongside. When I upgraded from 16.04 to
18.04, Grub choked because it found the unsigned kernels (which
Julian,
I gave up on the upgrade and installed a fresh version of 18.04, which
worked
fine. I guess the bug is in the upgrade process.
Bill
On 09/03/2018 03:07 AM, Julian Andres Klode wrote:
> That's by design to prevent you from installing a bootloader on a system
> where you have no kernel th
My kernel is Linux 4.16.14-041614-generic, It's possible that's why
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788727
Title:
upgrade crashing due to unsigned kernels
To manage notifications abo
I had the same issue whn upgrading from 17.10 to 18.04 and used the
following workaround:
cd /boot
mkdir unsigned
mv vmlinuz-4.10.0-40-generic vmlinuz-4.10.0-42-generic
vmlinuz-4.13.0-46-generic unsigned/
apt-get upgrade
and voila problem solved :-)
It seems that unsigned kernels are left in t
That's by design to prevent you from installing a bootloader on a system
where you have no kernel that will boot.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => New
** Changed in: grub2 (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a mem
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788727
Title:
upgr
** Summary changed:
- package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed
grub-efi-amd64 package post-installation script subprocess returned error exit
status 1
+ upgrade crashing due to unsigned kernels
--
You received this bug notification because you are a member of
44 matches
Mail list logo
