-
Notifications
You must be signed in to change notification settings - Fork 300
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
Usroverlay causes (non-fatal) reference counting fail #3303
Comments
Can you get a stack trace here using |
Hm does not seem to generate one
|
This with that alternative hardened malloc? If so the fact we're seeing SIGTRAP here makes me think somehow it's hooking things earlier than the g_critical()? Or hmm is it changing what |
No, this is the stock version on bazzite. There is a chance we are patching rpm-ostree to fix the deployment error that is on next release but I don't think this would affect it. Malloc should be the same as the one in kinoite Trap was caused after adding the environment variable These errors happen only on usroverlay, normal updates are fine |
ran gdb on top. debuginfo does not work so I cannot see the symbols. |
Figured it out. Happens during checking out They have these args:
EDIT: Seems like 996d76ae160ea0e6512f4af45cbe76ac85c9594d99547b03356a1826a6b1853d is common in all of them. Could the ref count be caused by this missing? |
Unfortunately there's a ton of @antheas any chance you can run with a build of ostree with debuginfo? Even better, build with |
I tried to do that. But unfortunately compiling ostree on a system without dev packages is not particularly easy... I have a command you can use to reproduce it though:
I am pretty sure you don't need to boot that image, just pulling it should work Bootc looks a lot nicer to work with, really nice in F41. |
Probably the cousin of issue secureblue/secureblue#369
Running
sudo rpm-ostree usroverlay --hotfix
causes an assertion error to be emitted for invalid reference counting. But the command completes successfully.I think there is a chance the rpm-ostree version here is patched to fix the deployment bug that was found recently, but is not changed other than that.
The text was updated successfully, but these errors were encountered: