Bug 348860 - Missing ability to choose, which grub2-system to start after reboot
Summary: Missing ability to choose, which grub2-system to start after reboot
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Session Management (show other bugs)
Version: 5.27.5
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Lubos Lunak
URL:
Keywords:
: 405557 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-06-07 21:12 UTC by H.H.
Modified: 2024-01-28 19:08 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description H.H. 2015-06-07 21:12:37 UTC
I often switch between linux and windows, and without an option, which os to boot after restart (like in kde 3/4), I often end up starting the default instead of the wanted one.

Please re-add this feature again.

Reproducible: Always
Comment 1 David Edmundson 2015-10-14 14:42:17 UTC
I've had a look.

This used to be done by KDM in a horrible looking file called "bootman.c" which reads and edits grubs config file.

ksmserver then had a special interface to talk to it.

UX was pretty bad, the user has to configure in KDE what boot manager they're using, 
Programs like grub-reboot help, but it relies on people adding GRUB_DEFAULT=saved to their menu settings, which isn't usable either

Personally I'm not convinced this is viable, grub is losing popularity and we can't have n backends for this.

If you can file a request on systemd that'd help
Comment 2 Dainius Masiliūnas 2016-10-20 21:32:31 UTC
How about efibootmgr -n? UEFI hardware is quite common nowadays.
There's now also CONFIG_EFI_BOOTLOADER_CONTROL, but not sure how many bootloaders handle that yet.
Comment 3 Andrey 2017-08-20 22:12:10 UTC
+1 for UEFI support.
Should we file separate bug on that?
Comment 4 Nate Graham 2018-09-09 23:53:47 UTC
(In reply to David Edmundson from comment #1)
> Personally I'm not convinced this is viable, grub is losing popularity and
> we can't have n backends for this.

GRUB2 seems pretty popular at this point. Maybe we could limit it to just GRUB2 systems, or even systems using GRUB2 with UEFI. Does that make this any more feasible?
Comment 5 Nate Graham 2019-03-17 23:41:16 UTC
*** Bug 405557 has been marked as a duplicate of this bug. ***
Comment 6 Marcus Furlong 2019-12-22 20:41:30 UTC
I use grub2-once for this functionality. i.e.

$ sudo grub2-once 'Windows Boot Manager (on /dev/sda1)'

It would be great if we got this feature back, it's sorely missed.
Comment 7 H.H. 2024-01-28 19:08:58 UTC
Implementing this back in kde could not be so complicated, at the moment, I have a workaround, having to open konsole, and type as root:

grub2-reboot "Windows Boot Manager (on /dev/nvme0n1p1)" && reboot