Solus Updates for Week 40, 2024

joluveba

EbonJaeger When running eopkg check, linux-current and linux-lts show as broken. These are false positives, and can be disregarded.

I ran sudo eopkg check in my three computers, and all packages are ok, linux-current included. This issue, at least in my computers, has been solved. 🙂

Harvey

joluveba
Yes, the usr-merge now being complete on your system will result in this no longer being a problem.

bubba66

Gnome box updated with no problems 😎

sHAKaJaada

Lucien_Lachance maybe like this for me?

but after that everything went well....

Harvey

sHAKaJaada
Yeah that screen will appear when the usr-merge is in progress. However on some systems it may be possible to complete the process very quickly. Some of my systems did it in 2s but as the message suggests it could take much longer.

palto42

sHAKaJaada I also just got this message during boot and was a bit surprised.
In my view such message should provide a bit more context about what's going on, e.g. which tool/driver caused the "system maintenance".

Lucien_Lachance

sHAKaJaada i guess i was lucky
systemd-analyze blame | grep usr-merge
848ms usr-merge.service

brent

sHAKaJaada happened to me too I thought it was cool🙂

Sebastian

palto42 I would argue that it is hard to put some comprehensible info on such a screen. "For more info consult Solus Forum." would have been nice perhaps though for those folks that do not follow Solus development via blogposts, Forum and Matrix channels.
But overall I am grateful for that everyrthing seems to played out well and for the course we are heading.

ps: on my plus 10 years old test laptop with hdd it took 12 sec

sHAKaJaada

Lucien_Lachance by me a bit more: 21.526s usr-merge.service
but everything went fine... no worries at all...

UncleSlacky

sHAKaJaada Mine took a couple of minutes, had an error near the start, something about the AppArmor service failing, but everything seemed to go off OK afterwards.

penny-farthing

33 packages (167.22 MiB) have been updated today in Solus.

As mentioned above, following the deployment of usr-merge, there are no longer any broken packages, and the last remaining one (linux-current) is now OK:

administrateur@solus-pc ~ $ systemd-analyze blame | grep usr-merge
18ms usr-merge.service
administrateur@solus-pc ~ $ sudo eopkg check linux-current
[sudo] password for administrateur:
Vérification de l'intégrité de linux-current OK
administrateur@solus-pc ~ $

Even if it has already been said, thank you to the entire team of developers for their hard and quality work. Solus users are grateful to them... and good luck for the future!

All that remains for me is to watch for the next updates of the kernel and the NVIDIA driver to see if they will fix my hibernation problems. But I can use my computer without hibernating so far, so there is no rush.

WetGeek

penny-farthing But I can use my computer without hibernating so far, so there is no rush.

I got tired of restarting all my apps every morning, and decided to just try a different approach. When I'm finished with the laptop for the night, I just use META+L to lock the screen. It's not as satisfying as a complete shutdown, such as hibernate implements, but in the morning when I provide my password to unlock the screen, everything is in the same state as when I locked it the previous evening.

And a big difference is, the wifi still works well. There's no need to do a reboot to allow me to connect again. (Unlocking is also a lot faster than waking from hibernation, which is a small but welcome advantage.)

The downside, of course, is leaving the machine running all night, while it's not being used, but I can deal with that as a temporary workaound. I mention this in case it might help someone who hasn't tried this approach yet.

Axios

Sebastian Ya when all the dead wood gets resolved it will be an interesting journey.

Axios

I always make it a point to read the weekly updates before doing the updates.
Just gives info what I might expect.
And in the course of them being posted I probably skipped a couple and in the course saved myself some trouble
in the long run. (Because people started posting )
Just way I do it.

Axios

I updated my laptop last night It appeared to be snappier But just did my other laptop and
it also exhibits this so I say this was a great update with no issues.
Snappier=programs opening running.
Keep up the good work!

Gregor

Everything went smoothly for me, no problems, thanks to the team for a great job.

AlphaElwedritsch

WetGeek why not configuring to go to standby instead of hibernate when closing the lid?
Then laptop is not only locked and running all night.

penny-farthing

WetGeek

Just to make sure I understood you correctly: does the META key correspond to the SUPER (Windows) key on the keyboard or is it another key?
In any case, pressing SUPER+L effectively locks the session without turning off the computer.

Also, just for your information, I processed a final Solus update today (6:50 PM, French time) that concerned apparmor, kernel v 6.10.11-303 and NVIDIA driver 560.35.03.
Despite this new update, there is nothing new regarding the problems related to the hibernate and suspend functions.
So, wait and see... and as I said above, as long as it doesn't prevent us from working on the computer, we have to know how to be patient.

DJSupertel

sHAKaJaada I got exactly the same on my HP desktop after rebooting after updates.

WetGeek

AlphaElwedritsch why not configuring to go to standby instead of hibernate

I tried "sleep," which is available in the main menu (Plasma), and was disappointed to see that it responded the same as hibernate. I'm not sure what the difference is between that and "standby," but I'll look for the latter in the system settings, and give that a try if it's there. Thanks for the suggestion!

EDIT: This seems to be the only way to use "standby":

Apparently it requires entering "sleep" first, which I'm pretty sure didn't help me. I created a keyboard shortcut for "hibernate" a long time ago (invokes systemctl hibernate when I press Ctrl+H), but I just tried to do the same for "suspend," and that didn't work (command not found). So, it appears that my only alternative is to lock the screen until whatever causes this glitch can be fixed.

EbonJaeger

We just did a mini-sync so we could generate testing ISOs for OpenCollective backers.

brent

EbonJaeger We just did a mini-sync so we could generate testing ISOs for OpenCollective backers

that went fine this morning for me + reboot