[Bug 1407790] Re: GRUB >= 2.00 has been unpacked but not yet configured.

2024-06-17 Thread Mate Kukri
I believe this was fixed in grub2 2.04-6 in 2020. ** Changed in: grub2 (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/1407790 Title: GRUB >= 2.00 has been

[Bug 1407790] Re: GRUB >= 2.00 has been unpacked but not yet configured.

2016-12-16 Thread Catalin Bararu
** Changed in: grub2 (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407790 Title: GRUB >= 2.00 has been unpacked but not yet configured. To manage notificatio

[Bug 1407790] Re: GRUB >= 2.00 has been unpacked but not yet configured.

2016-12-15 Thread Catalin Bararu
** Changed in: grub2 (Ubuntu) Status: Expired => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407790 Title: GRUB >= 2.00 has been unpacked but not yet configured. To manage notific

[Bug 1407790] Re: GRUB >= 2.00 has been unpacked but not yet configured.

2016-12-15 Thread Catalin Bararu
Hey, the same thing is happening to me. I saw that @Phillip Susi said that "The script is checking to see if /etc/grub.d/00_header still references it, which it shouldn't as it has been removed". Do you mean that the script has been removed or that the script has changed and is no longer referen

[Bug 1407790] Re: GRUB >= 2.00 has been unpacked but not yet configured.

2015-03-30 Thread Launchpad Bug Tracker
[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grub2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407790 T

[Bug 1407790] Re: GRUB >= 2.00 has been unpacked but not yet configured.

2015-01-29 Thread Mathieu Trudel-Lapierre
Could you please attach /var/log/dist-upgrade/main.log and /var/log /dist-upgrade/apt.log if you still have them from the upgrade? This may help figuring out what went wrong. ** Changed in: grub2 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a

[Bug 1407790] Re: GRUB >= 2.00 has been unpacked but not yet configured.

2015-01-06 Thread mca
Thanks for the swift reply. Purging grub-common (and manually removing /boot/grub) following by an install of grub-pc indeed did the trick. Most have gone wrong in one of the previous upgrades as you suggested. Only one warning remained during install, but that easy to fix: Warning: Setting GRUB_T

[Bug 1407790] Re: GRUB >= 2.00 has been unpacked but not yet configured.

2015-01-05 Thread Phillip Susi
That should not have made any difference since the script is not actually referencing GRUB_PREFIX since it was removed. The script is checking to see if /etc/grub.d/00_header still references it, which it shouldn't as it has been removed. Does your 00_header still reference it? If so something