does anybody know how to fix them? just delete them? or do I need to install solus all over again and lose all my data?
broken .conf files
Why not just good old
sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
from https://getsol.us/articles/troubleshooting/general-troubleshooting/en/
Maasi I fubar'd my own system yesterday due to impatience and spent 10 hours in tty and live disk.
What Staudey gave you: https://getsol.us/articles/troubleshooting/general-troubleshooting/en/ saved my life.
I have a hard time believing you have no broken packages with that grep command.
try: sudo eopkg check | grep Broken
at least you can see what happened.
sudo eopkg rdb is fast and deletes another variable.
moreover----read that help article and use those two terminal commands to check your lts
how I wrapped this up in 12 hours? throwing everything at the wall until finally using that troubleshooting page...
- Edited
the comparison thing was just to see if version numbers matched, I belive. then there was a plan i the help page from there.
blank screen patience. my ctrl+alt+whatever took a lot longer to appear.
you are right about one thing: when it was close to come back to life for me, udisk and nvidia were prominent.
it took a LONG time but the grep command finally worked in TTY. I had to manually remove and reinstall a lot of broken stuff before command worked--I know it goes by fast but I wrote as muc broken down on paper as I could remember. then rdb. then reboot. then after 10 hours FINALLY the login greeter except the wrong one. then boot into a HIDEOUS pitch-black OS called openbox. It's like a pitch black room and the flashlight is the rightclick.
Apparently we nuked our display managers somehow. took forever to get lightdm to work. And budgie itself was gone as well as some necessay gnome apps.
then AFTER grep "fixed" all packages in TTY, I ran the same command in the UI/OS to find more broken. Once that was settled I am back in business with some minor installs.
Coinciding, for me, with the update, is me ripping a lot of programs out this week (for space) without considering deps. That's on me. Then I aborted a 200-package update while SYNCING Friday (accident).
I am whole again.. the reason this reply is so long is there might be on thing you can take away to get you further down the road while my trauma is still fresh
edit/fixed one typo, left the rest...
Ive been trying your post 3-4 times. Now when I do sudo eopkg up messege appears thag says
updating repositories
updating repository: Solus
Program terminated.
Could not fetch destination file "https://mirrors.rit.edu/solus/packkages/shannon/eopkg-index.xml.xz.sha1sum": [Errno 14] curl#6 - "Could not resolve host
: mirrors.rit.edu"
before sudo eopkg up was fine
Maasi the gist of my post was manually uninstalling/installing half the broken packages in tty, led me to finally being able to use the grep broken command. The packages, need to run the danged command I had somehow ripped out. Somehow that diligence got me to the operating system...
....as to your question, stalling out at RIT is not uncommon during update. It is 100% cured by trying it again until it sticks. Keep trying it will update.