Solseek Now Available

Axios

I ran the tools and everything except eopkg and flatpk updates and had no issues
everything worked.
Will try the other later.
Dunno if cleaning caches had any effect when I was having problems the other day.
(just info) Budgie

Note: did have one broken package (libinput)

elfprince

Solseek cache generation on my Solus Budgie also takes about 5 seconds.

brent

Original-Syn Package installation status in the Info pane.

nice 🙂

elfprince Solseek cache generation on my Solus Budgie also takes about 5 seconds.

about the same for me. not 10 but more like 4 if I had guess

Original-Syn

Yep tested it on all the different editions. I did notice on one (Budgie) the first cache initialization took about 15 seconds after the big update, but subsequent were back to normal which should be ₅ seconds. The rest were all normal. I will keep an eye on it and just let me know if you guys keep seeing really long times. Solseek basically does the following on launch, all using native tools.

pkcon refresh (checks for updates)
flatpak list and flatpak remote-ls(flatpak cache)
eopkg la -U -N and eopkg li

It does these in parallel. None of this has changed in the last few versions of Solseek. I did a quick profile of each and it was timing about the same as before. It does not seem to be pointing to Solseek itself, but as mentioned will keep an eye on it.

Thanks for letting me know!!

Xoph

I did the big update and after the reboot, it did take a bit to generate the cache. However, next time I started Solseek it launched normally. I am guessing the eopkg cache or something. I rebooted and even did eopkg dc before launching Solseek to recreate the issue and I could not.

AlphaElwedritsch

I made a quick screen recording. that happens on my laptop.
Not only the first time. everytime when i start solseek.
It's 29 seconds. Somethings not correct here...

https://jumpshare.com/s/zy1GxCdhLDTKNO8fYjmE

brent

AlphaElwedritsch I counted that twice: approx 25 seconds. mine is a livable 5 sec but I wonder what circumstances would make it 25 sec...unless it's indexing over a massive amt of space? (guessing)

Original-Syn

AlphaElwedritsch

If you could. Run the following commands one at a time and see if any of them are taking a long time. These are what run on load and would like to see what is holding yours up. could also tell if there are any issues. It seems like a eopkg cache issue at first glance, but hard to tell...

Update Checks
pkcon refresh force
pkcon get-updates --plain | grep -E -c "\(Solus\)|\(Unstable\)"

Flatpaks
flatpak list --app --columns=application,name
flatpak remote-ls --system flathub --columns=application,name

Solus
eopkg li
eopkg la -U -N

The last one should be the longest as it is what gets all the packages, not installed on the system.

I am looking at having the last one first look at the local index cache, if it is available at the time of checking and only going to full check if needed. But that will need to be tested so may be an experimental setting in the near future. It would drastically speed things up.

Axios

I think everyone is trying make something fast that is going to be
uhhh how should I say it so-so thing depending on what it has to download and all
to many variables.
But thats kinda how I see it.
If it falls in a range thats about the best anyone can ask for.

Shrugs
Note I can live with the so-so as long as it works and is dependable

AlphaElwedritsch

Original-Syn @Original-Syn do you still need my help from here?

AlphaElwedritsch

Original-Syn If you could. Run the following commands one at a time and see if any of them are taking a long time.

If I run them one after the other, each one seems to take a long time. But in total, it could well be the time Solssek needs to generate the cache.

Axios

Just ran a flatpak update and no issues
I ran the above commands to me on first run the update check seems slowest at least for me
but of course ran again it was fast
It appear to be like slow as the other two combined. (When first run)
(Just info)

Original-Syn

I am noticing some irregularities on the pkcon commands. Sometimes fast, sometimes really slow. I am already working a bit on that part to speed it up. Will wait to see some other data before going beyond that.

@Axios thanks for the info

Original-Syn

What I have found so far is that it is not Solseek as the cause of the "generating cache" issue, that I should be able to work around it and make the overall launch must faster. I have been playing around with it on my test system.

Modularizing the distinct areas so that they do not impact each other as much, even in parallel.
Improved the on-launch update checks so that when launching it will not be required to finish before launching. It will finish when it finishes and update the display when needed.
Created a new method to use the local eopkg index file, if it exists to create the cache file for Solseek. This is MUCH faster. If the index file cannot be found it will automatically fall back to the eopkg la call It will be disabled by default at the next Solseek update, but you will be able to enable it in the config file. This will be considered experimental at this time until better tested.
Even if you do not try out the local cache file option, I have also made some changes that should speed up the caching through eopkg la as well.

Other things I am also working on are adding a few more eopkg tools, delete-cache and update-repo.

I would also like to get started creating the config file and adding the auto-update checks built in to help set everything up. This may wait until after the next update so I can help work around the cache generation time.

I really do appreciate everyone testing and letting me know when they see issues. This tool is still extremely young.

Original-Syn

AlphaElwedritsch Got it thanks.

pomon Thanks that does help.

New changes I am making should help with this area, especially the pkcon refresh and eopkg la.

pomon

These are the results of my commands. Maybe they will be helpful.

==================================================
            COMMAND EXECUTION TIMES
==================================================
Date: 2025-12-02 10:40:14

+--------------------------------+----------------+
| COMMAND                        | TIME (seconds) |
+--------------------------------+----------------+
| pkcon refresh force            |      11,000000 |
|--------------------------------+----------------|
| pkcon get-updates              |       0,000000 |
|--------------------------------+----------------|
| flatpak list apps              |       0,000000 |
|--------------------------------+----------------|
| flatpak remote-ls              |       2,000000 |
|--------------------------------+----------------|
| eopkg list-installed           |       5,000000 |
|--------------------------------+----------------|
| eopkg list-updates             |      17,000000 |
+--------------------------------+----------------+

==================================================
SUMMARY
==================================================
Total execution time: 37,000000 seconds
==================================================

I do not have any Flatpak packages installed.

Original-Syn

Alright, I have pushed a new release to Unstable that will hopefully reduce the launch time.

Here is the release announcement for more details.

I appreciate the information and feedback!! It was very much needed since I could not replicate on my end.

Axios

Original-Syn No problem thats what our group does.
We prob get little to energetic at times tho...lol

Original-Syn

Axios Yeah, but it is actually one of the things I love about this community. People care and that is important.

Original-Syn

Quick note to those having loading time issues. You can add SS_EOPKG_LCACHE=1 to ~./config/solseek/config to try out the local cache option after updating to 0.6.0. It is experimental, but it has been working for me this week. Please let me know if you have issues.

Even though v0.6.0 is just made available today, I have been sick this week.
And ignoring my wife's logic of me staying in bed, I brought a blanket into my office with some hot tea and was bored. So I have been working on some things for the 0.7.x release. Don't ask ETA 😉 . Some of it is just boring stuff, but should really help the future.
One kind of cool thing I did, again I was bored, was add some basic theme support. It is pretty basic, using fzf's theme support. But I created a new default theme called "solus" to bring a hint of Solus coloring into the app. Now for those that like the basic theme (more grayscale), I have also made this an option in the config file.

I am also adding eopkg history recall support built in. You will be able to not only see your history, but perform the rollback command straight from the tool to restore after issues. Info about eopkg history rollbak

Beyond that the big thing that no one will notice, other than those wanting to contribute to language support, is that I have moved from multiple text files per language to one. This should make it much easier for translators.

I also added a section in the tools menu for Solseek. The only entry currently is the ability to click to edit the config file.

Anyway, as mentioned I am sick, feel like crap, but bored. So figured I would give you a sneak peek at whats to come.

Axios

Original-Syn Yup get well its hard to turn it off sometimes and just rest.

« Previous Page Next Page »