https://bugs.kde.org/show_bug.cgi?id=521329
--- Comment #8 from John <[email protected]> --- Created attachment 193074 --> https://bugs.kde.org/attachment.cgi?id=193074&action=edit Successful updates for the firmware after deleting, resetting SecureBoot keys in the firmware and booting in the real UEFI mode Anyway, after a few tries to delete and reset the SecureBook keys, like in those comments on Github, I manged to bring the size back to 35%: Filesystem 1K-blocks Used Available Use% Mounted on efivarfs 384 132 248 35% /sys/firmware/efi/efivars --------------------------------------------------------------------------------------------------- After multiple trials and changes to the SecureBoot, I manged to delete + reset the keys and changed something from custom to the default, where I chose from the radio buttons the KEK option. Then booted with the entry that has the "UEFI:" prefix even though also "debian" as as an UEFI boot entry as I looked better. After restart Dolphin checked for updates and showed these 2, which installed successfully, though requiring a restart. With 35% usage in /sys/firmware/efi/efivars, everything is fine. Though I wanted to check with Dolphin too, but Dolphin show the wrong free space available when you are in the /sys/firmware/efi/efivars/ folder (many GiBs available) A bug that might be related to this: https://bugs.kde.org/show_bug.cgi?id=521063 Anyway, with the right firmware configuration and booting in the right mode, Dolphin and its backend works for firmare updates too or at least for the SecureBook keys, like in this case. Sorry for all the noise for nothing! -- You are receiving this mail because: You are watching all bug changes.
