Help needed, desktop not working anymore

Hello guys! To developers: please fix this situation with your mirrors. I’ve got all my system ruined just because for some reason my upgrade was not full.. and no pacman is not seeing new versions of packages. I tried many things.. including adding cdn77 manually to mirrors list as the first option. and still no proper packages for me.

cachyos-extra-znver4/plasma-workspace 6.5.3-1.1 (plasma) [installed]
KDE Plasma Workspace
extra/plasma-workspace 6.5.3-2 (plasma) [installed: 6.5.3-1.1]
KDE Plasma Workspace
extra/plasma-workspace-wallpapers 6.5.3-1 (plasma) [installed]
Additional wallpapers for the Plasma Workspace

same with qt and other components.

cachyos-extra-znver4 - is just old

so long story short part of update was done from “extra” repository and other packages just didn’t decide to update from “extra” and are waiting for cachyos-extra-znver4 to get updated versions.

That would seem to be something of a local issue .. not a Cachy one.

As znver4 is nominally even more updated than the others at this exact moment and should be providing plasma-workspace-6.5.3-2.1.

sudo pacman -Syu
:: Synchronizing package databases…
cachyos-znver4 is up to date
cachyos-core-znver4 is up to date
cachyos-extra-znver4 is up to date
cachyos is up to date
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade…
warning: libcups: local (2:2.4.15-1) is newer than extra (2:2.4.14-1)
warning: power-profiles-daemon: local (0.30-2) is newer than extra (0.30-1)
warning: zsh: local (5.9-6) is newer than extra (5.9-5)
resolving dependencies…
looking for conflicting packages…

Package (1) Old Version New Version Net Change

extra/qt6-base 6.10.0-3 6.10.1-1 0.02 MiB

Total Installed Size: 64.32 MiB
Net Upgrade Size: 0.02 MiB

if it’s local? what it could be? I refreshed keys.. done sudo pacman -Syy.. whatever. nothing helps.

Why would keys have any impact?

The most obvious and likely thing would be your mirror(s).

The repositories show versions more up to date than what you have access to.

Which means that either your mirror is not serving it or that you have some other issue like the local network.

So have you sorted mirrors?

You could also show the contents of /etc/pacman.d/cachyos-znver4-mirrorlist.

I don’t have “my mirrors” , I used cachyos-rate-mirrors.
Didn’t get about local network.

If there is no way to impact mirrors - I get it.. at least what it’s possible to fix is to make sure that every package is ready to update from extra repository if nothing in optimized repository.. or no packages will do this.

make them all choose one option.

as of cachyos-v4-mirrorlist:
I have removed everything from there but cdn77 - it fixed the problem…
I had yandex CDN as the first one before.

?

Those are your mirrors.
Not everyone uses the same ones and/or they are not in the same order, etc, because people are in different places around the world. Or may have configured it one way or another for any number of reasons.

?

You gave an example of a script that affects the configured mirrors and I also listed the exact file path.

And here we have an example of affecting mirrors.

Finding that a locally configured (and crappy) mirror was out of date. Much like anticipated.

( For further example - I have no yandex entries in any of my mirrorlist files. )

On the one hand you can say that Yandex Mirror was outdated. Ok. It’s true.
But what I offer to focus on is that the real reason was the partial upgrade which happened because some packages (qt6- for example) updated znver4 version to v1 version.. and some packages (plasma-*) - decided not to upgrade znver4 version with v1 version.

In my case extra repository was newer than znver4 and if all packages upgraded from extra repository - it would be ok (I checked with “sudo downgrade” v1 versions of needed packages like plasma-workspace were available)

So in the end it’s just a flaw of upgrade policy in pacman (maybe it’s an issue of package naming)

plasma-workspace extra/plasma-workspace 6.5.3-2

was not considered newer than 6.5.3-1.1
and the same for other packages

This thread has deviated quite a bit from the original topic. @Gherry was your problem fixed by the update?

Hi, sorry if I didn’t reply, but once I updated in the afternoon, everything went back to normal and I forgot to check back the forum!

Thank you again for the help

Congratulations! In that case, please mark your last answer as the solution so that others can find it quicker.

off topic a bit, but

  • Don’t want to or can’t download lots of data at the time (i.e. traveling with a laptop)
  • Don’t want to reboot (or delay rebooting following system package updates
  • Don’t want to (or can’t) deal with the chance that an upgrade results in needing to fix something inmediately

are all pretty common cases for a lot of people.