@Noel @j0rge @EyeCantCU https://github.com/ublue-os/akmods/pull/228
GitHub
Can be restored to extra when build issues are fixed
K^ there's your skew
Nyay!
EShould we force it?
KI'll look and see if i2c-piixbuf has been updated
Kand update that in akmods copr
Kthen it'll succeed
EAwesome 
KGitHub
Opposite of previous PR, merge me when this module is fixed upstream (Build will succeed).
Moved from common to extra.
Moved from common to extra.
G
G
GHelp please
GI can't see any logs as to what exactly is failing in the github build job.
Aprobably better to post in #
custom-image-support , also oot you got fortinet working in atomic fedora?
custom-image-support , also oot you got fortinet working in atomic fedora?
RFortnite? Or is fortinet something else
PI just want to say that yesterday Bluefin pulled update, I'm now on 560 NVIDIA drivers on an old Pascal, seems like all is working fine.
PThanks for the hard work. 
Aits a vpn
GI also got a post in #custom-image-support
custom-image-supportRoh lol mb
GI tried adding the repo to /etc/yum.repos.d/ and just doing rpm-ostree install forticlient
Gbut got the same error
GGitHub
Contribute to murdzheff/ublue-tessi development by creating an account on GitHub.
Abetter continue there, this is for ublue dev
GAre you by any chance from Bulgaria?
IWe just found an installation corruption error. Information: We base our images on ublue-os images. We deploy hardened_malloc. One variant (cosmic) has a permanent corruption issue. ostree is unable to do any image layering operations. The ostree filesystem also encounters errors (ostree fsck). We currently believe that the error is at ostree or rechunks. Our hardened_malloc seems to find this error but it is possible that more images are affected by this. I am unable to pinpoint the error. "ostree: fatal allocator error: detected write after free"
IGitHub![[BUG] rpm-ostree can't deploy on Cosmic images · Issue #369 · secur...](https://images-ext-1.discordapp.net/external/xSqebdFEXpPtRo275PkFd-byRq8uuRckPWOTDGNJ85s/https/opengraph.githubassets.com/e5bfaab463f0e91530c066026854191ddccfc7c2532099b1345bdb3d4d26572d/secureblue/secureblue/issues/369)
Describe the bug On the cosmic-main-hardened and cosmic-main-userns-hardened images (and probably nvidia images too), rpm-ostree can't write new deployments. Attempting to install or uninstall ...
II would like to help find the cause. But I do not know what combination is causing it. It looks related to rechunks + ostree.
AHi, slowly but surely we will fix jt
ACan you also find the line in ostree that emits this error
IIf you tell me how, yes. I am unsure what you mean
AI guess there is no line
AThis command is emitted by malloc
ASorry the error
IYes. Our malloc implementation does not like memory corruption bugs.
AWhat does filesystem corruption mean
IThe command: "sudo ostree fsck" finds issues in layers. "sudo ostree --delete" is unable to repair them. It may have nothing to do with the issue. Maybe just circumstance.
AAug 12 15:49:46 localhost rpm-ostree[13779]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
ASeems like the error is this
AThis is emitted by rpm ostree so we should be able to find the line
ACan you point to the file?
AThis causes the core dump
IPlease explain. I am unsure what exactly I should do. (Just FYI I need to reinstall to be able to debug this further, tried to repair it and may have caused more issues in ostree. Just to be able to pinpoint it I would need to reinstall to make sure that I do not find other issues that I caused myself.)
IThe github issue report is from an other user. I can confirm I had the same issue.
ACan you get some extra errors from ostree fsck?
AProbably rpm-ostree dying caused this
IYes, that is what I also believe. My working theory is that ostree + rechunks have one bug. Our malloc finds this issue. Nobody else sees it because everyone else uses the glic malloc instead of hardened_malloc. It is possible that we are affected because our malloc does not like memory corruption. It causes rpm ostree to crash. But that may also mean that ostree or rechunks have an issue that nobody else sees.
II will try to debug this again in a few hours and report back. I am busy right now.
Aas part of rechunk i replace some rpm-ostree files to make space
Athey never seemed to have made an issue with layering
Abut perhaps they do
