Bug#966554: how to apply the workaround?

2020-08-07 Thread quixote
Well, I waited till the weekend so if I needed hours to recover my system, I wouldn't have to drop the ball on all the other things going on in my life. And I made sure I had printouts of the instructions on recovering grub, and grug-efi, using chroot, and that I had a bootable recent live thum

Bug#966554: how to apply the workaround?

2020-08-05 Thread quixote
Thanks very much for your answers. There's something bizarre going on. Yes, my /sys/firmware/efi/efivars/ said it was full and had dump-* files in it. I removed those a few days ago. But after your comment I went to look if there were new ones cluttering the place up. No, there weren't, but df

Bug#966554: how to apply the workaround?

2020-08-03 Thread quixote
Dumb question time, because I'm still not seeing the updates to fix grub, and running grub-install /dev/sda still gets me the same errors about "no space left on device." (I checked: it's 200MB, and has 98% free space.) I only have two repositories in my sources.list, since I have a plain van

Bug#966554: how to apply the workaround?

2020-08-03 Thread quixote
On Mon, 3 Aug 2020 10:26:01 +0100 Colin Watson wrote: > On Mon, Aug 03, 2020 at 08:21:59PM +1200, quixote wrote: > > I haven't seen the fix appear yet in the regular upgrades. Is that right. or > > did I somehow miss it? > > You missed it. It's in bust

Bug#966554: how to apply the workaround?

2020-08-03 Thread quixote
I haven't seen the fix appear yet in the regular upgrades. Is that right. or did I somehow miss it? Following this link given above, https://people.debian.org/~cjwatson/tmp/grub2-buster/ I downloaded the following debs for my system (based on what was already installed): grub2-common_2.02+df