Solus Update Post for Week 45, 2025

Axios

The only strange thing i encountered when updating is it went really fast and crazy
download speed. (like maybe twice or 3 times normal speed)
Of coarse besides the 2 issues I had.
When I did the package repair they downloaded at normal speed.
I havent updated my kde yet
(just info)

brent

THE GOOD:
rollback successful
THE BAD:

No more EOPKG. Please help. What is the sync to shannon/polaris command again?

diagnostics0

brent

list-repo (lr) - List repositories
eopkg rebuild-db (rdb) - Rebuild Databases

brent

diagnostics0 https://help.getsol.us/docs/user/package-management/repo-management/#repository-management-commands
according that ^^ in help center this is the right command: sudo eopkg add-repo https://cdn.getsol.us/repo/polaris/eopkg-index.xml.xz

but that did not work. will try your RDB right now, thank you

EDIT: that followed by add repo command still did not work

yikes

brent

diagnostics0 list-repo (lr) - List repositories

listed as active let me keep playing. thank you

brent

my plan was to rollback and install everything but the Budgie stuff and troubleshoot from there.

this sucks

will keep trying to establish connection with repo. there were no warnings in rollback.

diagnostics0

brent

Are you still on Shannon or on Polaris?

Axios

brent Try eopkg ur
update-repo (ur) - Update repository databases
Cant rebuild them if are not their.

Shrugs

brent

diagnostics0 polaris.
my add-repo was correct command.
not even that Help page link ^^ mentions Shannon anymore in the repos to add

brent

Axios
sudo eopkg ur
Updating repository: Solus
Disabling keyboard interrupts for file operations.
eopkg-index.xml.xz.sha1sum (40.0 B)100% 0.00 --/- [--:--:--] [complete]
Solus repository information is up-to-date.

that looks good let me try to make a move:
sudo eopkg update ffmpeg
Program terminated.
Unrecognized command: update
Please use 'eopkg help' for general help.
brent@budgie ~ $ sudo eopkg it ffmpeg
System error. Program terminated.
[Errno 2] No such file or directory: '/var/lib/eopkg/package/baselayout-1.9.0-84/metadata.xml'
Please use 'eopkg help' for general help.
Use --debug to see a traceback.

no I got issues. thanks though 🙂

brent

more fabulous borkage!!

alfisya

brent sudo eopkg delete-cache

https://discuss.getsol.us/d/12053-solus-update-post-for-week-43-2025/53
https://discuss.getsol.us/d/12082-strange-behaviour-with-updating-via-discover/7

pomon

brent If the *.xml file is missing, I described a fix to get eopkg working again. You just need to visit the Solus repository online and copy the path to the specific *.eopkg package (either my method or the script by @NigelGreenway below).

brent

alfisya ran the dc
works!
but

$ sudo eopkg it ffmpeg
Updates available, checking reverse dependencies of runtime dependencies for safety.
The following package(s) are already installed and are not going to be installed again:
ffmpeg
No packages to install.
brent@budgie ~ $ sudo eopkg update ffmpeg
Program terminated.
Unrecognized command: update
Please use 'eopkg help' for general help.

never in my time with solus have I updated a single package before. how do I update ffmpeg?

and thanks for the fast response.

Axios

brent There is no update command
I type it wrong to from time to time..

Harvey

brent
Do not try an upgrade individual packages, partial updates are not supported and are a great way to break things. If you decide to roll back then you roll back, not cherry-pick what you will or will not update.

brent

Harvey If you decide to roll back then you roll back, not cherry-pick what you will or will not update

lesson learned, thanks Harvey

brent

somehow I don't think my Operation-Reinstall-1-Package-At-A-Time-Til-You-Find-The-Problem plan is very well thought out 🙂

Buddies of B gave me the old panel reset command. Maybe that will be next.

Or wait for 4.8 but I won't ask the eta 😉

Back to Endeavour to finish some work. Thanks all who rushed to help me. That's what I LOVE about Solus. You all rock.

TraceyC

elfprince Too many components + weekly updates = potential problems and breakage. Not enough time for testing.

This is why we test things in unstable before rolling them out to Polaris. For contrast, I've been running on unstable for a number of years now and rarely run into major bugs.

And, of course, the best way to make sure we have as little disruption as possible is to have more people testing with unstable. Everyone is welcome to test, if their situation allows. We welcome bug reports for bugs and packaging issues.

Original-Syn

TraceyC Same. Only my systems at my office and in the vm lab are on stable as a precaution. The rest are on Unstable. Try to report what I do find and so far nothing serious.

EbonJaeger

Budgie users who are experiencing the crashing issue, please keep discussion about it to this thread so the information is all in one place, and that other replies don't get missed in this thread. Thank you.

TraceyC

palto42 On Solus Budgie I get an error when Signal desktop starts.

Have a look at the known issues

palto42

TraceyC In my view the workaround proposed for Signal in known issues is sub-optimal, since it need to be applied per application and only fixes the key access and not the proper desktop detection (e.g. tray icon looks still different).
The root cause of the issue is the change of XDG_CURRENT_DESKTOP in Budgie from Budgie:GNOME to just Budgie which affects all Electron based apps. So the better workaround for me is to revert this change as posted here palto42 (only XDG_CURRENT_DESKTOP needs to bet set).

« Previous Page Next Page »