FS#65726 - [systemd] Upgrade to systemd 245 breaks default boot option

Attached to Project: Arch Linux
Opened by rainer (raneon) - Friday, 06 March 2020, 20:59 GMT
Last edited by Toolybird (Toolybird) - Monday, 25 September 2023, 07:52 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


After upgrading to systemd 245 (currently in testing), my system doesn't boot anymore to the default boot option defined in /boot/loader/loader.conf. My system boots by default to the normal linux kernel, but I do have linux-lts and memtest86-efi installed too. After the upgrade to systemd 245 now memtest86 starts.

Additional info:
* systemd 245
* systemd-boot

Steps to reproduce:
1. Upgrade to systemd 245
2. reboot
3. wrong system boots

default archlinux
timeout 0
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 25 September 2023, 07:52 GMT
Reason for closing:  Fixed
Additional comments about closing:  Old and stale. Assuming this is no longer an issue these days. But if so, please report upstream.
Comment by Christian Hesse (eworm) - Friday, 06 March 2020, 21:45 GMT
What does the remaining part of your boot configuration look like?
Comment by Doug Newgard (Scimmia) - Saturday, 07 March 2020, 04:10 GMT
systemd-boot can store a default in nvram, overriding the default entry in loader.conf. Does `bootctl set-default ""` change anything?
Comment by Jonas Witschel (diabonas) - Monday, 09 March 2020, 19:06 GMT
This happens because https://github.com/systemd/systemd/pull/13953 changed the behaviour of the "default" option: in systemd 245, you need to use the full file name of the configuration you want to boot, so in your case "default archlinux" needs to be changed to "default archlinux.conf".
Comment by jason ryan (jasonwryan) - Thursday, 12 March 2020, 15:25 GMT
  • Field changed: Percent Complete (100% → 0%)
Changing the loader conf to use `default option1.conf`, and using `bootctl set-default option1.conf` still boots option2.
Comment by freswa (frederik) - Thursday, 12 March 2020, 15:25 GMT
Could you please attach your full boot configuration? Thank you
Comment by jason ryan (jasonwryan) - Thursday, 12 March 2020, 16:32 GMT
I updated my conf file to use the .conf suffix for the default value.

I ran `bootctl set-default option2.conf` and then `bootctl list` to confirm that option2 was the default entry (of four).

Rebooted and it autoselected option 4.

Changed the loader default to option2 (removed the .conf) and rebooted and the correct image, option2 was autoselected.

Can someone please confirm that the .conf is in fact not necessary, as per the man page, and when used in conjunction with bootctl set-default actually breaks the intended functionality?

systemd 245-3

Working loader.conf:

default jwr
timeout 2
Comment by mark (qinohe) - Thursday, 12 March 2020, 18:47 GMT
@jason, I cannot confirm .conf is unnecessary, without it the last option (in my case) is chosen as default and so I need to add the .conf suffix(bootctl)
I say .conf does not need to be in loader.conf at all.
By that I mean entries in 'loader/entries' don't need to be in loader.conf, not even 'default'

As said in https://bbs.archlinux.org/viewtopic.php?pid=1891504#p1891504

edit: you can try by installing a new kernel, create a *.conf in entries and setting it default with bootctl without adding any *.conf to loader.conf.
Comment by jason ryan (jasonwryan) - Thursday, 12 March 2020, 19:54 GMT
@mark - yes, bootctl has priority. But the interaction between the two seems to be an, admittedly upstream, bug. I'm just trying to understand it (and ensure the wiki documents it correctly).
Comment by mark (qinohe) - Thursday, 12 March 2020, 20:29 GMT
@jason, Clear, I will keep an eye on how things evolve the next couple of weeks and let you know if anything changes here.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.