Sync Updates for Week 33, 2024

EbonJaeger

Heya folks! It's Friday, and that means it's time for the weekly Solus roundup!

@ReillyBrogan updated KDE Frameworks to 6.5.0 this week. This release has many fixes and improvements, including critical fixes for BluezQt and Breeze Icons. KArchive and KAuth now have improved file handling and authorization features, facilitating better inter-process communication. The full list of changes can be found here.

GNOME has been updated by @joebonrichie to 46.4. This is a simple bugfix release. Notably, this version includes improvements to overview startup notification, keyboard navigation in app folders, and nested popovers on Wayland. Also in this release are improvements for connecting to WPA2 enterprise networks. The full changelog is here.

The new version of the ProtonVPN GTK app (proton-vpn-gtk-app) has landed in the repository this week. It has been rewritten from the ground up, making it more efficient, and easier to develop new features. It does conflict with the old CLI and GUI client, so they are not co-installable.

Gleam made its way into our repository this week. It is "a friendly language for building type-safe systems that scale". It features a type system, function programming, and reliability from the Erlang runtime, with familiar and modern syntax.

Our Solus Cleanup Crew:tm: has been hard at work this week bringing the repository up to current standards:

Adding appstream metainfo - 204 packages (down 7) need appstream metainfo added
Adding homepage key - 131 packages (down 76) left without homepages
Fixing packages that do not build - 21 packages (up 6) do not build
Replacing obsolete macros in recipes
- cargo: 6 (no change) packages
Tagging packages for deprecation - 42 packages (down 1) tagged

Most of these tasks are beginner-friendly, and can be a great way to learn Solus packaging. We invite anyone that has the time and inclination to join us!

If you would like to join:

Join Solus Packaging Room on Matrix
Read and practice our packaging documentation
Submit your first Pull Request. We recommend doing the homepage task
Follow along the review process until your PR gets merged
Continue on contributing!

Security updates

There are a couple of security fixes this week. Be sure to install all available updates!

bubblewrap was updated to 0.10.0-20 (@ReillyBrogan). Includes security fixes for CVE-2024-42472.
flatpak was updated to 1.14.10-79 (@ReillyBrogan). Includes security fixes for CVE-2024-42472.

General updates

The full list of updated packages can be found here.

That’s all for this week, folks! We'll be here same time, same place next week for another roundup of the news!

palto42

I'm facing an issue that the upgrade was blocked by an unresolved dependency for perl-xmlsimple.
In my case perl-xml-simple was used by gcstar and after removing it, I could upgrade.

If I try to re-install gcstaror just it's dependency perl-xmlsimple I get below error:

sudo LANG=C eopkg it perl-xmlsimple
System error. Program terminated.
perl-xml-sax - perl-xml-sax-expat dependency of package perl-xmlsimple is not satisfied
Please use 'eopkg help' for general help.
Use --debug to see a traceback.

Harvey

palto42
Apologies, formatting error in listing dependencies lead to incorrect package name resolution. Fix for perl-xmlsimple has been cherry-picked.

palto42

palto42 As a workaround, I had re-built the perl-xmlsimple package from main branch against stable and installed manually.

Harvey Thanks a lot, works now with package from repo 🙂

AhmedBenhamouda

Sound is back but after rebooting, no sound again!!

AlphaElwedritsch

Did the Update right now.

Did it with Discover and not with "Software Center".

Worked well, as expected.
No issues so far.

WetGeek

Bluetooth now works as it should. I no longer need to do anything special to reconnect my mouse and keyboard after I reboot. That wasn't a serious issue, but an annoyance for sure. Thanks!

UncleSlacky

Update went well, but this issue persists (now only works about 10% of the time) - any idea if/when it might get looked at again?

EbonJaeger

Cherry-picked curl to fix a crash with other programs.

brent

this is the unheralded dirty work that will make transitions easier as we turn the corner. A cold one 🍻 for this crew:tm.

Pjol

After sync and reboot audio output device is gone on lenovo laptop, so no sound. Added my details to the open gh issue

Edit: My hp mini 400 g6 (i5-10400T) sync done without issues

Edit 2: Both are running Plasma

AlphaElwedritsch

Are these audio issues on all DEs?
I have and had No problems on my KDE

mouse_AUS

Other than still having to downgrade the kernel for audio everything else appears OK!

WetGeek

Oh no! I thought everything had gone well, but after awakening from a night of hibernation, various problems manifested, mostly browser-related. This has happened twice now. A reboot doesn't help, but a shutdown and restart seemed to cure it. There appears to be nothing wrong with Vivaldi, as it works quite well once the laptop was restarted - tab stacks and all. But when I checked for broken packages, I found this:

I remembered that apparmor has issues, but I don't use it, so I ignored that one. But the broken kernel appears to be more significant. So I tried to eopkg it --reinstall it, and got two more errors, for which I obviously couldn't get a screenshot.

Does this sound familiar to anyone else? I've never had a reason to regress to an earlier version of a package. I believe I may need to do that here, unless there's a simpler solution, and if so, I'd appreciate a quick review of how to do that.

I remember eopkg history to locate the previous version, but I'm not sure of what comes next. Also, would that generate problems because of all the KDE updates this week? Are they likely to require the newer kernel? Thanks!

brent

WetGeek these are false positives and not actually broken. still think they are trying to remedy that message. my current is 'broken' too. it;'s a symlink thing I think

alfisya

WetGeek I am not sure I follow what the problems are. It seems you said it is mostly browser related (So Vivaldi?) and a "Shutdown and Restart" solves it (?). So the problem does not occur anymore ? Or it keeps occuring after a Reboot?

If you wan to rolback and update, first check eopkg history to see which point (check the number order) do you want to rollback to. Then run sudo eopkg hs -t ***. "*" being the order number.

WetGeek

WetGeek Oh no! I thought everything had gone well, but after awakening from a night of hibernation, various problems manifested, mostly browser-related. This has happened twice now.

@"EbonJaeger: I'm sorry if my message wasn't clearer, but that's the problem. And it's cured by regressing to the last previous update. I'd try to narrow it down to root cause, but right now certain medical issues require me to keep Vivaldi available to schedule appointments. Maybe when some of those issues are sorted, I can update again and try using Firefox and see if it's really just Vivaldi that's affected, or returning from any hibernation is an issue for another browser.

WetGeek

brent these are false positives and not actually broken

Thanks for reminding me of that. But that apparently means my beloved Vivaldi might be the source of the problem, despite its appearing to work fine after a restart. So after I find the previous version number of it, whats next? Is eopkg it --reinstall all that's needed, or is there more to it?

ssr14

nice keet it up, i use XFCE edition run smoothly thank you

WetGeek

alfisya Or it keeps occuring after a Reboot?

Thanks for your help. Yes, various assorted problems continue after a reboot. Only a complete shutdown and restart allowed me to restart Vivaldi and continue working with it, after which all worked as it should.

But after the next wake-up from hibernation, the problem repeated. Again, reboot did nothing to help, but after a complete shutdown and restart, everything worked as expected.

Although I've never had a need to regress to a previous build, I remembered the first part of the process from reading other posts on the subject. But I'd forgotten what to do after that. That is, the history -t part. I've successfully regressed now, and loaded my virtual desktops with their usual contents. I'll try a hibernate/wake-up now to make sure, but I had no such probems before the update, so I'm confident that it will work.

Maybe whatever is wrong will be corrected in the next sync.

WetGeek

Yes, hibernating and then waking up works perfectly, and everything is exactly where it was originally. So it's definitely something to do with the update - first time this has happened to me. Thanks again, @alfisya.

EbonJaeger

WetGeek the problem repeated.

What problem? I don't think you said in your posts what's actually going on, which makes it impossible to have any ideas.