Sync Updates for Week 1, 2024

brent

All good. I did install fastfetch. Needs configuring for sure. Not the color logo neofetch gives but like the variety of the default information.

Observation not complaint: after updates, and reboot, slick-greeter defaults to my current wallpaper instead of the budgie snowy mountains. This is fine with me, you saved me the trouble of learning how to do it.

lastly thanking the hard-working team in this new January, and @Harvey who did a big update to a tool I use everyday: yt-dlp

alfisya

EbonJaeger Fish shell (the best shell - Reilly) was updated to v3.7.0. -Reilly

Agreed, been using it for a week. It is definitely better than bash (anything is) and more simple than zsh. With fisher, customizing is easy.

WetGeek

alfisya Agreed, been using it for a week.

I've looked through @EbonJaeger 's post above several times carefully, and I see nothing about the Fish shell. Where did you find this reference?

Phiqu

0 problems this time.

alfisya

WetGeek you can click the "Detail" text.

WetGeek

alfisya you can click the "Detail" text.

Thanks. That's probably been there with every update, but I didn't realize it is a link.

MikeK61

For me it was a weird sync this week.
Rocminfo installed 3 times during the update but it wasn`t installed anyways.
I had to install it again from software centre.
The openCL package says OpenCL 2.2 but info centre still shows openCL 2.1 with the same driver number as before. (3558)

Is this normal ?

ReillyBrogan

Just cherry-picked an update for dbus-broker that was causing a crash (a bad one that could lead to the system showing a black screen on boot). Also, you may see some extra updates appear since there was a micro-sync before that with some appstream/icon changes. Nothing major in there those ones though.

fvlserevere

ReillyBrogan I was having an issue related to greeter in which I wasn't able to log in; when I typed in the password, greeter seemed to enter desktop and then goes back to its display. I was able to log in via tty. This mini-update fixed this issue. Thanks.

snowee

Hello Devs,

I have an issue with this week's sync.
I was unable to sync at all.

I did the usual "sudo eopkg up"
it shows updating the usual 2 files ... eopkg-index.xml.xz.sha1sum and the other one
it kind of "hung there" for 3 mins, I couldn't move my mouse.
it did not proceed to the download phase.
after which I had to reboot.

after rebooting, i did sudo eopkg up again.
this time round, it outputs :
"Updating repositories
Updating repository: Solus
eopkg-index.xml.xz.sha1sum (40.0 B)100% 0.00 --/- [--:--:--] [complete]
Solus repository information is up-to-date.
No packages to upgrade."

Kindly advise what is the issue here.
Thank you.

UPDATE 1 : I did a sudo eopkg dc

After which I did sudo eopkg up, it says
eopkg-index.xml.xz.sha1sum (40.0 B)100% 0.00 --/- [--:--:--] [complete]
Solus repository information is up-to-date.
Program terminated.
Error parsing repository index information. Index file does not exist or is malformed.

Please help.

UPDATE 2 : Thanks for pomon, Justin and stalebread over at Matrix, I managed to resolve the issue.
For my own reference, this is what I did (credits to pomon)

sudo eopkg rr Solus
sudo eopkg up

Justin mentioned that it could be an issue with the CDN server.

alternatively, we could also (credits to Justin)
sudo rm /var/lib/eopkg/index/Solus/eopkg-index*
sudo eopkg ur

Harvey

snowee it could be an issue with the CDN server.

Sounds like the download or the extraction of the index was interrupted for whatever reason, which resulted in a corrupt or missing index and eopkg is not smart enough to recover from that. Hence "Error parsing repository index information. Index file does not exist or is malformed." So its not clear that the CDN is to blame.

The solution deleted any index present and downloaded it again.

We should probably add the solution to the troubleshooting section of the help center because I have heard of this happening before. Thank you for reporting back and to the users who assisted you in finding the solution.

Harvey

discord 0.0.40 cherry-picked.

MikeK61

Rocminfo still doesn`t work.

hsa api call failure at: /home/build/YPKG/root/rocm-info/build/rocminfo-rocm-6.0.0/rocminfo.cc:289
Call returned HSA_STATUS_ERROR_INVALID_ARGUMENT: One of the actual arguments does not meet a precondition stated in the documentation of the corresponding formal argument.
hsa api call failure at: /home/build/YPKG/root/rocm-info/build/rocminfo-rocm-6.0.0/rocminfo.cc:1227
Call returned HSA_STATUS_ERROR_INVALID_ARGUMENT: One of the actual arguments does not meet a precondition stated in the documentation of the corresponding formal argument.