I am running the latest version of openSUSE Tumbleweed (updated today).
I was just going about Cockpit to see the different options (sort of like I did with YaST when I first started with openSUSE, looking at all the different modules) and noted that the “Bootloader” section keeps failing when I click on it, and results in an error that bootkitd.service failed to start.
Reading through the Service logs, it seems that it is looking for GRUB, but I am on systemd-boot which was the default when I reinstalled Tumbleweed recently.
I wanted to check if this is a bug for Cockpit or what may be causing this.
I do not need to modify any boot settings – I just like to see what options are available compared to YaST – but I would like to know just in case I need to in the future.
Hi. I don’t have an answer, just to mention that it happened to me too. Being curious to see it in action, i installed Cockpit for the first time and also noticed this bootkitd.service failure.
@ontdekik Thanks for confirming that you are also experiencing this. I’m glad that Tumbleweed still uses YaST to configure boot loader settings (systemd boot) and I could correctly edit things through there, so no problem with that.
I just wanted to raise this in case this is a bug with Cockpit.
If you go through all the services available you’ll find more examples. Changing the stock setup requires more inntricate knowledge than just activating/running some service.