This bug was fixed in the package grub2 - 2.02-2ubuntu8.19
---
grub2 (2.02-2ubuntu8.19) bionic; urgency=medium
* grub-install: cherry-pick patch from grub-devel to make grub-install
fault tolerant. Create backup of files in /boot/grub, and restore them
on failure to
started with xenial install.
grub2 is at 2.02~beta2-36ubuntu3.28
put apparmor profile in place, and upgrading non-interactively
upgrade to 2.02-2ubuntu8.19 fails as expected with grub-install saying
that error cannot open /dev/vda permission denied.
grub-pc package remains in iF state.
in
@regenpfeifer
Some of the identified issues affect debian too. we are working with
debian maintainers to resolve them there too. It is unfortunate that
some of the updates got pushed out rapidly, thus causing distress.
--
You received this bug notification because you are a member of Ubuntu
Unfortunately I have switched to Debian 10 meanwhile, so I cannot test
the bugfix. Nevertheless thank you for your efforts. I will certainly
return to Ubuntu in the future.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Steve, 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.19
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: fr-114
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid drive and stop
in preinst, before unpacking files, and
@juliank thank you.
accordingly #1896608 shouldn't be listed as a blocker on
https://discourse.ubuntu.com/t/focal-fossa-20-04-1-lts-point-release-
status-tracking/17604 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@costinel It's failing due to bug 1896608 in your case which is a
regression from this update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf
manually installing grub works like this:
# grub-install --force --removable --boot-directory=/boot /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
meanwhile as a workaround I have symlinked /var/lib/dpkg/info/grub-pc.postinst
to /bin/true so other apt
I have enabled debugging on /var/lib/dpkg/info/grub-pc.postinst when
running dpkg --configure -a: https://termbin.com/7nh1
but I don't understand from the above output why it fails
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
this bionic to focal upgrade still fails. not sure if this is the proper
place to discuss.
18.04.5 installed minimal in vmware player then do-release-upgrade:
https://i.imgur.com/YGLEWvy.png
18.04.5 setup deviations from defaults: root on thin lv created manually
in terminal in live installer.
Hello Steve,
thank you for your explanation. In my case I am quite sure, that my grub
was correctly configured BEFORE the upgrade to 20.04. I am starting with
an absolutely fresh installation of 18.04 which is working flawlessly
and reboots without any problems.
I have tried the upgrade to 20.04
> "Could not install 'grub-pc'. The upgrade will continue but the 'grub-
> pc' package may not be in a working state. Please consider a bug report
> about it. Installed grub-pc package post-installation script subprocess
> returned error exit status 1."
This is not evidence that this bug is not
I can confirm that this bug is not fixed. Today Ubuntu informed me of
20.04 and I started the distribution upgrade. I got the following
message:
"Could not install 'grub-pc'. The upgrade will continue but the 'grub-
pc' package may not be in a working state. Please consider a bug report
about it.
Unfortunately, this bug seems not fixed for me.
I am using a remote server at 1&1 Hosting with a RAID 1 configuration
and logical volumes (LVM). I am starting with a fresh image of Ubuntu
18.04 LTS. With do-release-upgrade I can upgrade to Ubuntu 20.04 LTS,
but I am ending with this error:
I was unable to upgrade and this link
(https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1769446) solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Upgrade (from v18.04 to 20.04) is already released!
Thanks to everybody for your debbuging and support!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when
The strange is that the Ubuntu 20.04 LTS is already available from the Windows
10 store.
It's possible to install this version and transfer all the configuration,
applications and repositories from Ubuntu 18.04.5 LTS to 20.04 LTS?
--
You received this bug notification because you are a member
On Fri, Sep 25, 2020 at 05:57:15PM -, Chris wrote:
> Since this is the final blocker, I think they're just leaving that
> status alone until they actually publish 20.04.1 for upgrade, so they
> don't get a deluge of people asking why it's not released yet if there's
> no blockers.
>
>
Since this is the final blocker, I think they're just leaving that
status alone until they actually publish 20.04.1 for upgrade, so they
don't get a deluge of people asking why it's not released yet if there's
no blockers.
Probably running final tests on the upgrade path.
--
You received this
I wonder why this is still mentioned as upgrade blocker at
https://discourse.ubuntu.com/t/focal-fossa-20-04-1-lts-point-release-
status-tracking/17604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On September 20, 2020 5:09:37 AM PDT, Hadmut Danisch
<1891...@bugs.launchpad.net> wrote:
>So for upgrading from release X to Y both X and Y must not have
>critical bugs?
Nothing of the sort. This bug is no longer a blocker now that it's
fixed in focal, and I believe the intent is to turn on
So for upgrading from release X to Y both X and Y must not have critical
bugs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid
As you can see, Bionic status is Confirmed, not 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/1891680
Title:
grub-pc needs to detect when debconf points to invalid drive and stop
in
ok, so now that this is fixed, why is ubuntu 18.04 to 20.04.1 still
blocked?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid
Does this not need to be backported all the way to Xenial and Bionic ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid drive and
This bug was fixed in the package grub2 - 2.04-1ubuntu26.4
---
grub2 (2.04-1ubuntu26.4) focal; urgency=medium
* grub-install: cherry-pick patch from grub-devel to make grub-install
fault tolerant. Create backup of files in /boot/grub, and restore them
on failure to complete
Hi, Louis.
You made me happy for a few minutes.
Regards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid drive and stop
in
** Changed in: grub2 (Ubuntu Focal)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid
Sorry, didn't meant to change the status, I cannot revert the change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid drive and
** Changed in: grub2 (Ubuntu Focal)
Status: Fix Committed => 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/1891680
Title:
grub-pc needs to detect when debconf points to invalid
Installed from 18.04.4 media, in bios mode.
Added and loaded apparmor profile.
Enabled focal, focal-updates, focal-proposed archives.
Exported DEBIAN_FRONTEND=noniteractive to ensure non-interactive
updates.
Started upgrade of grub-pc grub-pc-bin grub2-common grub-common.
Configuration of
On Wed, Sep 09, 2020 at 08:51:49PM -, costinel wrote:
> some of us here are innocent 18.04LTS users waiting for canonical to
> enable do-release-upgrade to focal, because this issue is blocking the LTS
> to LTS upgrade process (link in comment #9)
There is a test case in the description that
@vorlon,
some of us here are innocent 18.04LTS users waiting for canonical to enable
do-release-upgrade to focal, because this issue is blocking the LTS to LTS
upgrade process (link in comment #9)
with that in mind, how can we help testing without access to focal?
--
You received this bug
Hello Steve, or anyone else affected,
Accepted grub2 into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu26.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@ded, the bug says for groovy
Started work: 2020-08-18
Completed: 2020-09-02
for focal,
Started work: 2020-09-08
so one can only guess it would take another two weeks, if the same work
conditions apply
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Is there an ETA when we can finally do-release-upgrade from 18.04 to
20.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid drive
** Changed in: grub2 (Ubuntu Focal)
Status: Confirmed => 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/1891680
Title:
grub-pc needs to detect when debconf points to invalid drive
Yes, it looks that way:
"Focal Fossa (20.04.1 LTS) Point-Release Status Tracking"
https://discourse.ubuntu.com/t/focal-fossa-20-04-1-lts-point-release-status-tracking/17604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Will this fix be backported to Focal? This is the only bug blocking
upgrades from 18.04 to 20.04, afaik.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when
This bug was fixed in the package grub2 - 2.04-1ubuntu29
---
grub2 (2.04-1ubuntu29) groovy; urgency=medium
* grub-install: cherry-pick patch from grub-devel to make grub-install
fault tolerant. Create backup of files in /boot/grub, and restore them
on failure to complete
** Changed in: grub2 (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid
** Tags added: id-5f36bab45785997ba0092e8a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid drive and stop
in preinst, before
I disagree that preinst changes are needed.
I have fixed error reporting in non-interactive postinst case.
And made grub-install resilient, w.r.t. operating against non-existent
devices or devices that refuse writing to. In all such cases, backup is
created and restored. Thus there is no need to
** Merge proposal linked:
https://code.launchpad.net/~xnox/grub/+git/grub/+merge/389968
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points
** Description changed:
[Impact]
* grub-pc currently installs new core to MBR and installs new modules
to /boot in an unsafe manner, which may lead to incompatible combination
of MBR and modules resulting in failure to boot.
[Test Case]
* Install using old point media, of
** Description changed:
[Impact]
* grub-pc currently installs new core to MBR and installs new modules
to /boot in an unsafe manner, which may lead to incompatible combination
of MBR and modules resulting in failure to boot.
[Test Case]
* Install using old point media, of
** Description changed:
- Currently on upgrade if the debconf variable for the drive to install
- grub-pc to point to a non-existent drive, the grub package will
- nevertheless happily carry on and the postinst will exit 0 - as a result
- leaving the /boot/grub contents and the MBR in an
** Changed in: grub2 (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: grub2 (Ubuntu Groovy)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
First point => yes
Second point => mostly yes, but I am not sold on having it a must in
preinst. dpkg-reconfigure does not call preinst, it only calls "prerm
config postinst", and we must have the same checks and error recovery in
postinst. (Because things can change between preinst and postinst,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Bionic)
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/1891680
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Xenial)
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/1891680
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/1891680
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Focal)
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/1891680
Title:
54 matches
Mail list logo
