Temporary blocking of updates, now unblocked

elfprince

brent Rebooting tomorrow morning.

Dudel

[FAILED] Failed to start apparmor.service - Load AppArmor profiles.
[FAILED] Failed to start ufw.service - CLI Netfilter Manager.
[FAILED] Failed to start systemd-vconsole-setup.service - Virtual Console Setup.
[FAILED] Failed to start systemd-vconsole-setup.service - Virtual Console Setup.

Dudel

Dudel
Fridays update went fine btw.

Solarmass

Dudel [FAILED] Failed to start apparmor.service - Load AppArmor profiles.
[FAILED] Failed to start ufw.service - CLI Netfilter Manager.
[FAILED] Failed to start systemd-vconsole-setup.service - Virtual Console Setup.
[FAILED] Failed to start systemd-vconsole-setup.service - Virtual Console Setup.

I had the same problem after today's update. Fridays update went fine too.
I followed @EbonJaeger post above to fix it by chrooting:

https://help.getsol.us/docs/user/troubleshooting/boot-rescue/#mounting-your-system

you need A Live ISO or another system you can boot
Mounting your system
mount your EFI System Partition (in case of EFI)
Chrooting to your Solus system

here you will probably need this

sudo ln -srvf /target/usr/bin/bash /target/bin/bash
sudo ln -srvf /target/usr/bin/bash /target/bin/sh

I skipped Networking step
Repairing packages

sudo eopkg rebuild-db

I skipped sudo eopkg up and sudo eopkg check here

Re-run system-wide configuration triggers

sudo usysconf run -f

Regenerate UEFI boot entries

sudo clr-boot-manager update

Unmounting your system
and reboot.

This worked for me.

EbonJaeger

Please hold one moment.

brent

Solarmass you chrooted into your budgie? I thought today's update was made to prevent that?
My eopkg was not damaged in Friday's. Was yours? I'm confused but been a long day.

edit: I have not downloaded the updates today or installed them or rebooted.

johano

sudo ln -srvf /target/usr/bin/bash /target/bin/bash
sudo ln -srvf /target/usr/bin/bash /target/bin/sh

Solarmass, thanks this helped me get up and running again.

Friday week 19 updated with no issues, but the fix for that update broke the system, on reboot with

[FAILED] Failed to start apparmor.service - Load AppArmor profiles., etc

kintaeb

Solarmass So all of this worked for me, except the clr-boot-manager update step. That gives an error of "Cannot determine the currently running kernel" and I'm not quite sure why. Should I attempt to exit chroot anyway, reboot and see if the system is fixed?

Solarmass

brent I updated my system on Friday without any issues. Today's "hot" update borked it and I had to chroot. Interesting that my other Solus PC wasn't affected.

catfishsushi

ReillyBrogan My Monitors are not working right, every few minutes, they shuffle their arrangement at random intervals, and sometimes go hours just fine. I have combed over the settings many times and have them set the way i want/need, but they still shuffle. Any ideas? Please advise me 🙂 I usually run 4 monitors with primary mirrored, but since the issues started, have unplugged #4 but to no avail.

brent

Solarmass I updated my system on Friday without any issues. Today's "hot" update borked it and I had to chroot. Interesting that my other Solus PC wasn't affected.

trippy. thanks for clarifying

brent

Somehow, without announcement, the updates are blocked again.
Which is good since I can avoid the 'hot' fix. I hope.

Was going to face the music and update but:

Failed to fetch file, retrying 5 out of 5 "https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz.sha1sum": HTTP Error 403: Forbidden
Program terminated.
Hit max retry count when downloading: "https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz.sha1sum"
Please use 'eopkg help' for general help.

it's late afternoon/night in the USA.
Feels like I dodged a bullet?

EbonJaeger

More issues were discovered, and we're working on a plan forward. Sorry for the false hope, all.

alfisya

The staffs are still working on this (again), hence the shannon repo is blocked again. If you want to see the process, feel free to join the packaging room on matrix. Reilly, Evan, and many other staffs are discussing(working) the best move forward. Also as noted before if steps explained here doesn't solve your current problem, please go to support room on matrix for more personalized troubleshooting. Clearly, this is critical problem as we don't want anymore users end up in borked system. Thank you all for your patience. Cheers !

VTMarik

Thanks for posting this, I'd forgotten to hit the update button and was wondering why it was sitting on the Discombobulation step just now.

EbonJaeger

Okay, the stable repository is once again unblocked; we believe we now have a path forward.

If you still experience issues while updating, such as if an earlier update broke your system, please follow the steps in this Help Center article to chroot into your system from a live session, and run the following commands:

sudo ln -srvf /target/usr/bin /target/bin
sudo ln -srvf /target/usr/sbin /target/sbin

This will perform the "usr-merge" manually, creating symbolic links for /bin and /sbin. After that, exit the chroot and reboot your system.

Note: As a result of the fixes, eopkg check will fail on a bunch of packages. This is because of the symbolic links for /bin, /sbin, and /lib, and does not actually indicate a problem. This will be addressed at a later time.

Kuuchuu

~~My update script I threw together checks for broken packages each time after a system update, and at the~~ ~~moment it is listing the following packages as broken and reinstalling them every time I run it:~~
acl apparmor attr audit bash bzip2 coreutils cpio dash e2fsprogs fuse2 glibc golang grep iproute2 iptables kmod mdadm ntfs-3g sed shadow systemd tar util-linux wpa_supplicant zsh

~~I am also experiencing major lag spikes during most every operation, but I'm unsure how related to the current update that is as I just installed a new gpu (gtx 4060ti) & updated the bios version.~~

EDIT: I'm sorry! Missed the part where you said eopkg check will fail. Major system stuttering/freezing is due to the new GPU, so I'll make a new thread for that.

alfisya

Kuuchuu If your system is working, it is harmless. As noted on previous post

Note: As a result of the fixes, eopkg check will fail on a bunch of packages. This is because of the symbolic links for /bin, /sbin, and /lib, and does not actually indicate a problem. This will be addressed at a later time

Also please try update it normally using sudo eopkg upgrade, then reboot. Reinstalling all those "broken" packages over and over will not solve the issue until it is addressed on later date.

Sebastian

EbonJaeger If you updated previously, and now your system is broken

Do people who ran the initial update without experiencing any obvious issues need to take any action?

Harvey

Sebastian
Assuming you have updated again and rebooted, no there is nothing more you need to do.

« Previous Page Next Page »