-
Notifications
You must be signed in to change notification settings - Fork 195
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
SIGSEGV during labeling when importing RPMs #4966
Comments
|
Hmm, looks like a segfault in SELinux-related bits. |
@jlebon, the only thing I tried was I'm also wondering if it wasn't something HW related, I found out later that the same PC (with 14900KS CPU) was rather unstable on MS Windows (ASUS motherboard set some crazy limits) and CPU needed some tuning. Unfortunately I don't have a way to retest this ticket on this specific PC at the moment. |
Can either of you upload the coredump file? |
As for me, I did not touch selinux sins I installed Silverblue to my machine so its in its default enforcing mode. |
Did @elewarr not post a coredump in his first reply? if not I don't know how to make a coredump file |
Never mind I'm unfamiliar with core-dump's I believe I have found my last core-dump of rpm-ostree from upgrading today. here it is: https://file.io/6hZCSP2PYdXT (jlebon edit: re-uploaded at https://jlebon.fedorapeople.org/core.rpm-ostree.0.7982e15cb32048c0a6eb6c9d572dcdcb.3725.1716835330000000.zst for now so it doesn't expire) |
Hey @jlebon just for confirmation, the file I linked in my previous comment is the file you ask for, right? |
Can not reproduce on FCOS testing stream Steps:
|
|
@HuijingHei can you reproduce with my instructions? ( #4975 ) |
@HuijingHei and I tried to debug this a bit today. Oddly, opening the core dump in gdb goes down to But anyway, from what we could tell, this doesn't for now seem caused by something on the ostree side. We should have SELinux folks take a look at this. |
@jlebon alright, should I go open a issue on selinux's Github? Or will you handle communication? |
No, can not reproduce using the same steps on FCOS 40.20240611.20.0. |
Also can not reproduce with silverblue (using libvirt, and update os with Not sure if still exists on latest os with new rpm-ostree, could you have a try when you have time? Thanks! |
@HuijingHei yeah seems to have been fixed in the latest release! Appreciate your guys time and help! |
Thanks @boooooooaq very much for your time and testing. Also much appreciated for @jlebon's debug guidance, really learn a lot! Hope the new release will also fix @elewarr's issue, if not, feel free to reopen and upload coredump file, thanks! |
Thank you for the review and analysis of the issue. I had a chance to test this issue back on the same PC I had initially the problem with - unfortunately, it still exists - same
|
I did not give up this time - I limited core multiplier for performance clock from 62 to 52 and the installation passed. |
Describe the bug
I installed Fedora Silverblue on my PC. I was following Fedora Docs for installing NVidia drivers and RPM Fusion repos. Unfortunately I'm unable to do this because the command fails always.
I have a laptop and it's perfectly fine there.
I tried to install system from scratch about 3 times - and can reproduce the issue each time for every command execution.
Reproduction steps
rpm-ostree upgrade
and rebootedrpm-ostree install kmod-nvidia xorg-x11-drv-nvidia
or:
sudo rpm-ostree update \ --uninstall rpmfusion-free-release \ --uninstall rpmfusion-nonfree-release \ --install rpmfusion-free-release \ --install rpmfusion-nonfree-release
or actually most of the
rpm-ostree install
tries for different packages.Expected behavior
Command finishes successfully.
Actual behavior
For the first command:
For the 2nd:
System details
Additional information
The text was updated successfully, but these errors were encountered: