[Expired for grub2-signed (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: grub2-signed (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: grub2-signed (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
Hello
"dpkg: erreur de traitement du paquet grub-efi-amd64 (--configure) :
installed grub-efi-amd64 package post-installation script subprocess was
interrupted
Traitement des actions différées (« triggers ») pour ureadahead (0.100.0-20) ...
ureadahead will be reprofiled on next reboot
dpkg:
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
This has completely bricked an AMD E-350-based mini PC.
I recently installed ubuntu 18.04 server; and 3 updates later, I can't
boot the device at all. Not even POST video output. Pulling the CMOS
battery didn't help.
The system ran fine for 4+ years running CentOS 7 server.
Here's the apt
Just hit this on an Dell E5250
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
install/upgrade: installed
I have a DELL 9343 XPS running 'Ubuntu 18.04.1'. The first recent
indication that I had a problem with the Software Updater was with an
update I installed on 31-JAN-2019 when Software Updater returned the
message 'package operation failed'.
Looking back at the logs, I found in /var/log/dpkg.log
I'm seeing the same error.
$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0
workaround #11 just worked for me. Dell XPS-13 (9343) circa 2016-02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
This is the error I just got, and the warning when I used workaround #11
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully
That appears to be unrelated to this bug, plenty of space left here for
me with no dump files.
I'm seeing the same error everyone else is seeing: efibootmgr unable to
delete a file in EFI via sysfs, as Thierry Mallard's strace already
showed:
Hi, I had the same bug since summer 2018. But for me, the following fixed the
problem:
The bug was caused by a "no space left on device error" on the "efi firmware".
There was a hint in the apt log.
So a colleague of mine (https://launchpad.net/~aburch) gave me the tip to
delete dump files in
And I just had exactly the same problem (failure to modify EFI variable)
during update of secureboot-db and again running postinstall script
immediately after reboot worked OK.
Silence is becoming ridiculous. What we need is kernel with verbose
debug output about handling EFI variables. Right now
Just hit me again updating to
grub-efi (2.02-2ubuntu8.7)
workaround from #11 worked again
Dell Latitude E5450
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package
Had the same issue on a Dell Latitude E5550. Reboot also fixed it for
me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
This also just happened to me for the second time updating to 1.93.7
Workaround fixed it again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed
Dell XPS 13 here too, Ronan Mooney's workaround does the trick and
everything was fine.
Updating to 1.93.7 brought up this same error once again :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have installed the IEEE version of the GRUB. Package: grub-ieee1275.
It seems to work perfectly.
However, I am not expert in computer science, therefore I have no idea
of the possible consequences of this change.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I updated UEFI from Asus, but same version I was using since April.
Still only can boot with rEFInd from sdc or flash drive with full
install of Ubuntu.
UEFI does not want to see ESP on sda which is mounted by fstab. It changes
entries to like drive disconnected.
And on reboot all new entries
Latitude E7450. Same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
install/upgrade: installed
Ronan Mooney's workaround worked for me.
Also Dell XPS 13. Sounds like this is a machine specific issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed
I got the same error ("efibootmgr failed") again after today's update
and again running "dpkg --configure -a" immediately after reboot
completed without errors. It really sounds like kernel issue - something
goes wrong over time.
--
You received this bug notification because you are a member of
Ya. I am facing same issue. Anyone know how to resolve it ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
This the message I get after running:
sudo dpkg --configure -a
Cannot upgrade Secure Boot enforcement policy due to unsigned kernels
│ │
│ Your system has UEFI Secure Boot enabled in firmware, and the
After rebooting everything worked again
bor@bor-Latitude-E5450:~$ sudo dpkg --configure -a
Настраивается пакет grub-efi-amd64-signed (1.93.4+2.02-2ubuntu8.3) …
Выполняется установка для платформы x86_64-efi.
Установка завершена. Ошибок нет.
Обрабатываются триггеры для shim-signed
It is possible that there are different problems but in my case the
problem is that efibootmgr cannot delete EFI variable:
root@bor-Latitude-E5450:~# LC_ALL=C grub-install
Installing for x86_64-efi platform.
Could not delete variable: Invalid argument
grub-install: error: efibootmgr failed to
May be related to this bug.
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1787692
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed
WORKAROUND:
From:
https://askubuntu.com/questions/1031066/errors-during-upgrade-
from-17-10-to-18-04-shim-signed-and-grub-efi-amd64-signed
sudo su -
cd /boot/efi/EFI
mv ubuntu ubuntu-old
apt install -f
mv ubuntu-old ubuntu
update-grub2
exit
"It seems that the newer
I hit this issue during an update last night. I am now worried about
rebooting my laptop. Is any other info required to investigate this?
I think #8 is unrelated, and actually due to lack of space on the EFI
partition. There is plenty of room in my system, and removing the exe
does not help
# df
Dell XPS 13 9343 here too, running Ubuntu 18.04.1 with 4.15.0-23-generic.
However, I do not use the same method as @mes2k for BIOS updates. I just boot
into Windows to install the .exe... Therefore I have nothing under /boot/efi
that could be causing it...
➜ ~ sudo dpkg-reconfigure
My hardware: Dell XPS 13 (9343)
I am able to reproduce the error using
$ sudo dpkg-reconfigure grub-efi-amd64-signed
Then I thought what might be different on my system, because this kind
of error should normally affect more people. I remembered a BIOS update
some weeks ago. Before attempting
Experiencing this on 18.04 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
install/upgrade: installed
Any workaround available for this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
install/upgrade: installed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2-signed (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/1753518
Furthermore, I looked for the postinst script and found out that it's
just the « grub-install » command which fails.
root@ingatech-XPS-13-9343:~# LC_ALL=C grub-install
Installing for x86_64-efi platform.
Could not delete variable: Invalid argument
grub-install: error: efibootmgr failed to
... and LC_ALL=C version of the grub-install -v command
** Attachment added: "grub-install.txt"
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518/+attachment/5070955/+files/grub-install.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I made a strace for the installation process and find the following
error in a subprocess, which seems to be the cause.
strace -qf -o /tmp/grub_installation.log dpkg --configure grub-efi-
amd64-signed
** Attachment added: "Strace log extract for the dpkg --configure strace -qf -o
37 matches
Mail list logo
