[Bug 955075] New: yast2 bootloader crashes from missing grub_installdevice
http://bugzilla.opensuse.org/show_bug.cgi?id=955075 Bug ID: 955075 Summary: yast2 bootloader crashes from missing grub_installdevice Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: snwint@suse.com Reporter: bwiedemann@suse.com QA Contact: jsrain@suse.com Found By: Development Blocker: --- Created attachment 655927 --> http://bugzilla.opensuse.org/attachment.cgi?id=655927&action=edit yast2 logs /etc/default/grub_installdevice was still referencing a nonexistent /dev/disk/by-id/wwn-0x50014ee2af1d729b-part6 (might be related to moving my rootfs from sda6 to sda2) and then yast bootloader threw a fatal error -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=955075 http://bugzilla.opensuse.org/show_bug.cgi?id=955075#c4 Christoph Obexer <cobexer@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P0 - Crit Sit CC| |cobexer@gmail.com Flags|needinfo?(bwiedemann@suse.c | |om) | --- Comment #4 from Christoph Obexer <cobexer@gmail.com> --- Hi I just got a new notebook and restored a backup of my openSUSE installation onto the new disk, which made my Yast2-Bootloader crash upon opening (at first it displays an error, then it crashes with signal 11). I expect that in case the grub install device can't be found that the module asks me what to do. I opened Yast2-Bootloader to update the entry after all. Also I hope that RPM updates of grub2 would fail if it can't actually update the installed bootloader stage 1... Crashing is never an appropriate response to wrong/outdated configuration ;) I guess that provides the needed info, thus I cleared the NEEDINFO flag Br, Christoph -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=955075 http://bugzilla.opensuse.org/show_bug.cgi?id=955075#c5 --- Comment #5 from Bernhard Wiedemann <bwiedemann@suse.com> --- (In reply to Josef Reidinger from comment #2)
Bernhard - /etc/default/grub_installdevice is authoritative source for info where stage1 is installed. If device no longer exists, what you expect from bootloader?
At least it should not crash, but give a message asking the user to correct the value in /etc/default/grub_installdevice or provide the yast UI to fix the value. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=955075 http://bugzilla.opensuse.org/show_bug.cgi?id=955075#c6 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P0 - Crit Sit |P2 - High Status|NEW |CONFIRMED --- Comment #6 from Josef Reidinger <jreidinger@suse.com> --- Well, my plan is to detect such stuff and if found offer user to repropose bootloader configuration or exit bootloader, but it need some changes in architecture, so it is not so easy fix, but I am working on it. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com