Bootkit daemon fails to start on Cockpit

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.

See below for the screenshot.

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.

Any help is appreciated.

Thanks, Jaymo

System information in case it is helpful:

System:
  Host: jadams-Aspire-A315-23 Kernel: 7.2.4-1-default arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.7.5 Distro: openSUSE Tumbleweed 20260910
Machine:
  Type: Laptop System: Acer product: Aspire A315-23 v: V1.21
    serial: <superuser required>
  Mobo: DL model: Lotus_DA v: V1.21 serial: <superuser required>
    Firmware: UEFI vendor: Insyde v: 1.21 date: 09/08/2022
Battery:
  ID-1: BAT1 charge: 34.5 Wh (100%) condition: 34.5/41.8 Wh (82.7%)
CPU:
  Info: dual core model: AMD Athlon Silver 3050U with Radeon Graphics bits: 64
    type: MCP cache: L2: 1024 KiB
  Speed (MHz): avg: 2559 min/max: 1400/3200 cores: 1: 2559 2: 2559
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega
    Series / Radeon Mobile Series] driver: amdgpu v: kernel
  Device-2: Chicony VGA WebCam driver: uvcvideo type: USB
  Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
    dri: radeonsi gpu: amdgpu resolution: 1: 1680x1050~60Hz 2: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: radeonsi,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.2.2 renderer: AMD Radeon
    Graphics (radeonsi raven2 ACO DRM 3.64 7.2.4-1-default)
  API: Vulkan v: 1.4.357 drivers: radv,llvmpipe surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
    Audio driver: snd_hda_intel
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor
    driver: snd_pci_acp3x
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio
    driver: snd_hda_intel
  API: ALSA v: k7.2.4-1-default status: kernel-api
  Server-1: PipeWire v: 1.6.8 status: active
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
  IF: wlp2s0 state: up mac: 10:a5:1d:83:97:1c
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp3s0 state: down mac: c0:18:50:a6:09:ea
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: 10:A5:1D:83:97:20 bt-v: 4.2
Drives:
  Local Storage: total: 2.05 TiB used: 266.1 GiB (12.7%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM256GD3JX016N
    size: 238.47 GiB
  ID-2: /dev/sda model: One Touch w/PW size: 1.82 TiB type: USB
Partition:
  ID-1: / size: 235.47 GiB used: 89.9 GiB (38.2%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 1022 MiB used: 898.8 MiB (88.0%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 235.47 GiB used: 89.9 GiB (38.2%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-4: /opt size: 235.47 GiB used: 89.9 GiB (38.2%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-5: /var size: 235.47 GiB used: 89.9 GiB (38.2%) fs: btrfs
    dev: /dev/nvme0n1p2
Swap:
  ID-1: swap-1 type: partition size: 2 GiB used: 15 MiB (0.7%)
    dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 60.0 C mobo: N/A gpu: amdgpu temp: 60.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 6 GiB available: 5.72 GiB used: 2.98 GiB (52.0%)
  Processes: 292 Uptime: 0h 12m Shell: Zsh inxi: 3.3.41

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.

I am also running Tumbleweed with systemd-boot.

@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.

1 Like

Nothing buggy about this:


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.

@knurpht Thank you for the explanation.

1 Like

@knurpht That makes sense, that it would be due to a conflicting service. Thanks for clarifying. I will mark this as “solved”

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.