Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  WARNING: No Upgrades until further notice! EDIT: siduction is ok, Debian not!  (Read 3149 times)

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838
Please do not update until further Notice!
The install of grub* 2.04-9 could lead to a unbootable system

Bitte vorerst keine Updates!
Vermutlich führt die Installation von grub* 2.04-9 zu einem nicht startfähige System

Background: BootHole. Fixes for that are coming in and they are broken!
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509
https://bugzilla.redhat.com/show_bug.cgi?id=1861977

If you have installed the grub-packages with version number 2.04-9, please report.
« Last Edit: 2020/07/30, 23:45:57 by devil »

Offline titan

  • User
  • Posts: 312
Re: WARNING: No Upgrades until further notice!
« Reply #1 on: 2020/07/30, 21:52:39 »
If this was this morning (what time zone is the forum clock on) I rebooted after DU ( new kernel ) I am on Grub 2-04-9 . However I will leave PC on until fix appears.

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838
Re: WARNING: No Upgrades until further notice!
« Reply #2 on: 2020/07/30, 22:14:30 »
This is just a precaution, because other distros like Ubuntu, Red Hat  and Debian Stable are having problems.

Offline tranquil

  • User
  • Posts: 111
Re: WARNING: No Upgrades until further notice!
« Reply #3 on: 2020/07/30, 22:29:06 »
Darn, I need to remember to check here before upgrading. I've already upgraded one of my computers. Hopefully the Grub upgrade doesn't hose my system. Thank you for the warning.
Dual-booting Debian Stable and Unstable with Openbox window manager and Tint2 panel.

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838
Re: WARNING: No Upgrades until further notice!
« Reply #4 on: 2020/07/30, 23:14:51 »
After some more investigation it seems that this only fails with secure boot signed kernels. Ours is not. Others liked Debian, Ubuntu, Mint and others are. I set up a test system and it rebooted fine after the upgrade. So siduction is safe, but Debian is not, from what I hear.

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838

Offline pjnsmb

  • User
  • Posts: 88
@devil


after a grub update my system boots ok


BUT I loose my internet connection.............................


This is after only updating grub without any other updates.
« Last Edit: 2020/07/31, 06:54:29 by pjnsmb »
regards
pjnsmb

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838
I doubt, loosing your connection is related to this bug. Please completely dist-upgrade your system and see if connection is back.

Offline pjnsmb

  • User
  • Posts: 88
@ devil


I have these on hold :



cups-client/unstable 2.3.3-2 amd64 [upgradable from: 2.3.3-1]
cups-common/unstable 2.3.3-2 all [upgradable from: 2.3.3-1]
cups-core-drivers/unstable 2.3.3-2 amd64 [upgradable from: 2.3.3-1]
cups-daemon/unstable 2.3.3-2 amd64 [upgradable from: 2.3.3-1]
cups-ipp-utils/unstable 2.3.3-2 amd64 [upgradable from: 2.3.3-1]
cups-ppdc/unstable 2.3.3-2 amd64 [upgradable from: 2.3.3-1]
cups-server-common/unstable 2.3.3-2 all [upgradable from: 2.3.3-1]
cups/unstable 2.3.3-2 amd64 [upgradable from: 2.3.3-1]
grub-common/unstable 2.04-9 amd64 [upgradable from: 2.04-8]
grub-efi-amd64-bin/unstable 2.04-9 amd64 [upgradable from: 2.04-8]
grub-efi-ia32-bin/unstable 2.04-9 amd64 [upgradable from: 2.04-8]
grub-pc-bin/unstable 2.04-9 amd64 [upgradable from: 2.04-8]
grub-pc/unstable 2.04-9 amd64 [upgradable from: 2.04-8]
grub2-common/unstable 2.04-9 amd64 [upgradable from: 2.04-8]
libcups2/unstable 2.3.3-2 amd64 [upgradable from: 2.3.3-1]


I am having a problem with my HP printer if I update cups so it's on hold


As soon as I try to update grub I loose my connection

regards
pjnsmb

Offline Camelot

  • User
  • Posts: 81
I had the update yesterday (+ today) and can booting without problems (or warning).

Code: [Select]
apt-cache policy grub-common grub2-common
grub-common:
  Installed: 2.04-9
  Candidate: 2.04-9
  Version table:
 *** 2.04-9 500
        500 http://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
grub2-common:
  Installed: 2.04-9
  Candidate: 2.04-9
  Version table:
 *** 2.04-9 500
        500 http://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
Code: [Select]
Kernel: 5.7.11-towo.2-siduction-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.2
« Last Edit: 2020/07/31, 10:57:24 by Camelot »

Offline sunrat

  • User
  • Posts: 406
I haven't tried updating siduction, but there was a grub update 2 days ago and a regression fix update today in Buster so presumably it would be good in sid now also.
« Last Edit: 2020/07/31, 13:31:17 by sunrat »

Offline charlyheinz

  • User
  • Posts: 99
I' ve just run a DU and everything is working nice... .
- grub2 2.04-9 installed

Offline eriefisher

  • User
  • Posts: 264
Confirmed after yesterdays d-u. Grub 2.04-9. Reboot was good.

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838
pjnsmb, you can update grub now and if the problem persists, open a new thread for it.

Offline pjnsmb

  • User
  • Posts: 88
@devil


As always thanks for your help and advice.


I will leave my explanation of the answer to my problem on this thread to help anyone else searching the forum for a similar boot problem :


After I updated grub to  2.04-9 I kept getting this line repeated in terminal after  using 'apt update':


Failed to fetch http://httpredir.debian.org/debian/dists/unstable/InRelease  Something wicked happened resolving 'httpredir.debian.org:http' (-5 - No address associated with hostname)


After a forum search I found out this appeared to be a DNS problem and on investigation realised that as part of the grub updates it was updating network manager settings.
I use dnscrypt-proxy for my dns and have added the advice :


'edit the file in /etc/Networkmanager/NetworkManger.conf and add "dns=none" under the [main] section'
[/size]to stop my resolv.conf file from being altered.After removing this line apt worked properly again.



regards
pjnsmb