-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bootupd: thread 'main' panicked at src/bios.rs:116:62 #739
Comments
Can you try the workaround from #738 to get a backtrace? |
Here the backtrace:
|
With debuginfo installed:
|
Reproduced on Silverblue Rawhide.20240930.n.0, UEFI only (does not happen with in a BIOS only VM). |
Looks like pttype can be null but we dont account for that case: Line 19 in 3e55890
|
travier
added a commit
to travier/bootupd
that referenced
this issue
Oct 2, 2024
zram, sr0 (CD/DVD) and LUKS devices generally don't use partitions, thus don't have a partition table and don't have a partition type so this field may be null. Fixes: coreos#739
cgwalters
pushed a commit
to travier/bootupd
that referenced
this issue
Oct 2, 2024
zram, sr0 (CD/DVD) and LUKS devices generally don't use partitions, thus don't have a partition table and don't have a partition type so this field may be null. Fixes: coreos#739 Signed-off-by: Colin Walters <[email protected]>
travier
added a commit
to travier/bootupd
that referenced
this issue
Oct 4, 2024
zram, sr0 (CD/DVD) and LUKS devices generally don't use partitions, thus don't have a partition table and thus don't have a partition table type so this field may be null. Fixes: coreos#739 Signed-off-by: Colin Walters <[email protected]>
travier
added a commit
to travier/bootupd
that referenced
this issue
Oct 4, 2024
zram, sr0 (CD/DVD) and LUKS devices generally don't use partitions, thus don't have a partition table and thus don't have a partition table type so this field may be null. Fixes: coreos#739 Signed-off-by: Colin Walters <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After updating bootupd, this bug appeared when trying to check the status of bootupd.
To Reproduce
Please describe the steps needed to reproduce the bug:
Screenshots
OS version:
Additional context
I ran it with RUST_BACKTRACE=full, but I didn't get any more information.
/boot/bootupd-state.json content:
The text was updated successfully, but these errors were encountered: