i'd like to better understand how having bootupd installed would have "magically" saved us... it's n

i'd like to better understand how having bootupd installed would have "magically" saved us... it's not clear to me yet since i'm not aware of us directly requesting it to do anything

j0rge•4/8/24, 10:03 PM

🎮bazzite

j0rge•4/8/24, 10:04 PM

only error that matches here

j0rge•4/8/24, 10:04 PM

"Fedora Atomic systems (rpm-ostree based systems) do not update the BIOS / EFI bootloaders files by default on updates as this operation may fail and leave the system in an un-bootable state.
The bootupd project has been created to fix this issue, creating a user/administrator triggered process to update the bootloader."

Jj0rge https://discord.com/channels/1072614816579063828/1087140957096517672/11947581306...

bshermanOP•4/8/24, 10:05 PM

on bazzite there's a different issue from stock atomic or even ublue, given the fully custom signed kernel, i don't think bazzite really relies on the shim given they don't use the fedora signed kernel

j0rge•4/8/24, 10:06 PM

yeah I'm just pointing out that we haven't had any reports yet

j0rge•4/8/24, 10:06 PM

So I'm thinking we keep an eye open and let the situation develop

Bbsherman i'd like to better understand how having bootupd installed would have "magically...

M2•4/8/24, 10:23 PM

It has a socket and service that is running by default?

MM2 It has a socket and service that is running by default?

bshermanOP•4/8/24, 10:24 PM

sure, but if rpm-ostree wasn't directed to use it and bootupctl wasn't being used, how would it be activated?

M2•4/8/24, 10:25 PM

Fair. I honestly don't understand how grub updates are supposed to work here if rpm-ostree isn't doing them either

bshermanOP•4/8/24, 10:25 PM

I'm open to maybe it did save us, I'm just ignorant of how.

j0rge•4/9/24, 12:27 AM

@RoyalOughtness here's a juicy one: https://github.com/ublue-os/config/issues/247

Jj0rge @RoyalOughtness here's a juicy one: https://github.com/ublue-os/config/issues/24...

Gerblesh•4/9/24, 12:27 AM

fpaste

Gerblesh•4/9/24, 12:27 AM

cat foo | fpastecat foo | fpaste should do the trick

j0rge•4/9/24, 12:27 AM

yes, that's what the issue says

Gerblesh•4/9/24, 12:28 AM

I see now

j0rge•4/9/24, 12:28 AM

I mean it as a convenience wrapper, auto put the rpm-ostree status and whatever else we need

j0rge•4/9/24, 12:28 AM

so like, they run one command, paste it in, then we don't have to be like "please stop cutting out the most important lines" in discord, lol

Gerblesh•4/9/24, 12:29 AM

so just pipe

rpm-ostree status

rpm-ostree status

into fpastefpaste?

j0rge•4/9/24, 12:29 AM

while digging through the man page for fpaste I found --sysinfo.

j0rge•4/9/24, 12:30 AM

so like, if we know we can get all the hw info + rpm-ostree status + whatever else we may think is useful then users would only ever have to worry about the one command

Gerblesh•4/9/24, 12:31 AM

j0rge•4/9/24, 12:34 AM

and by default

j0rge•4/9/24, 12:34 AM

oooooooooo

Gerblesh•4/9/24, 12:35 AM

playing around with --sysinfo--sysinfo, problem is that I don't know how to combine the sysinfo and the rpm-ostree status

j0rge•4/9/24, 12:38 AM

can also just do that in a followup.

j0rge•4/9/24, 12:38 AM

just fixing the truncating status would do us a solid

j0rge•4/9/24, 12:38 AM

plus the nice thing is people can start socializing it now, so as we figure out new things to ask for it can be totally flexible in that way, but the command will remain the same for the users, which will pay off dividends over time

j0rge•4/9/24, 12:50 AM

j0rge•4/9/24, 12:50 AM

forum growth is visible now

j0rge•4/9/24, 12:51 AM

j0rge•4/9/24, 12:51 AM

j0rge•4/9/24, 12:51 AM

This is nice, scientific evidence of @nickname 's awesomeness.

Original message was deleted

Gerblesh•4/9/24, 12:54 AM

not currently no

Gerblesh•4/9/24, 12:54 AM

go for it

j0rge•4/9/24, 1:05 AM

or just displaying on the terminal is fine

j0rge•4/9/24, 1:06 AM

if the sysinfo is too excessive maybe a simpler combo from existing tools might do the trick

j0rge•4/9/24, 1:06 AM

no rush, was just thinking about it as this happened to me today

j0rge•4/9/24, 1:20 AM

yeah I learned a bunch too

fiftydinar•4/9/24, 12:28 PM

Can this simple change get approved?
https://github.com/ublue-os/config/pull/239

GitHub

chore(just): Message the user that rebooting to Legacy BIOS from OS...

systemctl reboot --firmware-setup doesn't support this.
That command calls: org.freedesktop.login1.Manager SetRebootToFirmwareSetup, which is the DBUS interface of systemd-logind.

Robert•4/9/24, 1:31 PM

@jstone You may want to check your F40 builds now. I was receiving the same tar error as you, but today they seem to be working.

jstone•4/9/24, 1:55 PM

Thanks for the heads up

jstone•4/9/24, 1:55 PM

Still seems to be failing though https://github.com/joshua-stone/rose-os/actions/runs/8532577191/job/23614998501?pr=18

GitHub

Add F40 branch · joshua-stone/rose-os@423c43d

ublue-os with fewer downstream modifications. Contribute to joshua-stone/rose-os development by creating an account on GitHub.

Noel•4/9/24, 3:28 PM

@M2 do you have some free time sometime today to review your PR? I'm trying to reconcile how I can get it added to the testing branch to actually test your code.

M2•4/9/24, 3:28 PM

I could hop into a voice chat around 4pm EST

Noel•4/9/24, 3:30 PM

unfortunately I am booked from 2PM - 4PM CST. Is 1PM CST possible? over lunch?

M2•4/9/24, 3:31 PM

I'm busy 12:45 PM - 2 PM EST. Are you available later today? 4 PM CST I think is 5 PM EST and I could do a call then

Noel•4/9/24, 3:32 PM

I can do 4PM CST.

M2•4/9/24, 3:32 PM

Okay, I'll hop on around then

Noel•4/9/24, 3:32 PM

I have a meeting that bumps up right against that time, but hopefully shouldn't go over.

i'd like to better understand how having bootupd installed would have "magically" saved us... it's n

Similar Threads

Similar Threads

Similar Threads