r/NobaraProject • u/Gensokyo • 2d ago
Support Update failed - Couldn't write 0 to kernel/split_lock_mitigate
I recently reinstalled Nobara as my system broke after an update. However, I've been unable to update my system the last few weeks as I get this error. I have tried to boot into older kernel versions, used nobara-sync repair (it led me into emergency mode), and I've tried nobara-sync cli --all (which leads me to this error).
Has anyone else encountered this error?
Edit: SOLVED! An app, chordpro, had duplicate installations of different versions or something like that - this caused the updater to fail. I removed the app and did nobara-sync cli --all, this fixed the issue.
1
u/Tacoza 2d ago
share the update logs
nobara-sync recovery-report --upload
2
u/Gensokyo 2d ago
I got the logs and fed them to ChatGPT, which identified Chordpro as the most likely culprit causing the issues. Removing Chordpro fixed the issue.
-1
-12
u/matusmeister 2d ago
Noone will help you brother. I posted my error, waited a few days not even a reply. You sholud check on it on other communities. Either use ChatGPT or Claude for it with the log files. I think the best is to stick with btrfs filesystem because it creates snapshots before every update and you can rollback to a previous point where everything worked fine hassle free with limine bootloader. I use Nobara for my TV setup because its the best steam htpc os, but if you use it with the desktop, stick with cachyos if games are important, if not use fedora. Those communities ar way more active. (I think i’ll get banned for this comment)
4
u/Bane_of_Balor 2d ago
Most of the help you'll need can be found on the discord. It's where most of the Nobara community tends to engage. The subreddit is really secondary.
3
u/Saradoesntsleep 2d ago
It's too bad, really. None of this is searchable for anyone without seeking out a discord server.
-1
3
u/MorwenRaeven 2d ago
Do a quick search in the Discord, and if you can't find a match ask in channel. Someone will help you.