Sync Update for Week 44, 2023

EbonJaeger

Heya folks! It’s time for another round of update news! Let’s get started.

@GZGavinZhao landed LLVM 16 last Saturday. This is a major step to landing ROCm and enabling hardware-accelerated machine learning to Solus. When that work finishes, we will be among the first distros to support open-source machine learning on AMD hardware, including PyTorch and Tensorflow support OOTB. Furthermore, the maintainers have taken particular care to extend the hardware compatibiltiy and create a seamless developer experience by using a system LLVM instead of a bundlded one. LLVM 16 has been packaged in a way that is co-installable with LLVM 15 for developers and applications that may still require that version.

@ZachBacon is continuing his work on bringing XFCE4 to Solus! He cleared a significant hurdle in working out how to apply our desired styles, or branding, to the XFCE environment. Our XFCE edition will be using the Qogir GTK theme by default with the Papirus icon theme. Starting the session should now be faster, too. Here is a little preview of what he's cooking:

XFCE4 Teaser

We're all looking forward to the official release of the Solus XFCE4 edition!

Hacktoberfest concluded this week. We received and merged 270 pull requests to our packaging repository during the month of October! Some of these will have been made by team members, but many more were made by contributors who aren't on the Solus team. Thank you to everyone who contributed to the project, and we look forward to more contributions in the future! If you have ever wondered about contributing to the Solus, check out our packaging section of the Help Center. You can find everything you need to get started there.

Other updates this week include:

That’s all for this week, folks! Check back next week for more delicious sync news!

craigtoyoracer

EbonJaeger Thank you and team.
Reading the LLVM update jogged the memory about a curious article (to me)
https://www.phoronix.com/news/Ryzen-AI-For-Linux-Requests

EbonJaeger

Known issues

There is an issue with Blender when you try to open a project that uses GPU Subdivision acceleration, it crashes. The current workaround is to disable GPU Subdivision in the Viewport section of the Blender preferences. This was already broken, and we are working to address the issue.

Due to a Chromium bug, some Chromium/Electron based applications may have broken rendering due to trying to use an invalid shader cache. See our Troubleshooting article for a fix.
Due to build issues, intel-compute-runtime likely has a problem, it's actively being worked on.

unclemez

EbonJaeger Shared Thanks for super job done!

brent

EbonJaeger are we still on for an update today, 11/10, or deferred to next week? forgot! edit typo

brent

XFCE looky beautiful!
appreciate the info.
no updates til next week, right? my sudo eopkg up layeth barren, as it were.

ermo

brent no updates til next week, right? my sudo eopkg up layeth barren, as it were.

Try again now.

brent

ermo oo la la🙂

Solarmass

The only issue I found is qBittorrent theme. It's now forced to dark after Solus Budgie update. And some selected items are not visible, when you move window, many items became white.

ReillyBrogan

Solarmass We imported a bunch of patches from Fedora to better integrate qt5 applications into GTK environments (GNOME/Budgie). qt5 now tries to determine if you're using a dark theme and if so will set itself to use the dark color palette. You may need to adjust some theme settings on your end to make it look better now, but this is generally considered a positive change for most applications.

penny-farthing

I thought that the problem mentioned on Friday by @EbonJaeger with the intel-compute-runtime package would result in the Solus updates being postponed for a week. As users, we could have understood that.

And then, this Sunday at 8.53pm (French time), 67 updates (509,08 MiB) arrived, and so far so good since their validation.

You're really great, thank you. 👏

presianbg

Hi,

Am I the only one having:

Qt FATAL: Cannot mix incompatible Qt library (5.15.10) with this library (5.15.11)

after the upgrade?

Looks like the QT based apps (keepassXC, VB, Qbittorrent) are affected and not being able to run them (core dumped).

any suggestions how to fix ?

EDIT: I think I found the issue - the package python3-qt5 is still on 5.15.10 and this package is a dependency of:
autokey-py3-qt polychromatic python-qscintilla hplip torbrowser-launcher python-qtwebengine

EDIT2: even after removing python3-qt5 and all packages from above + system reboot, the problem still persist.
Can't find what other package causes the version mismatch.

EDIT3: Managed to trace the coredump to this shared object /usr/lib64/qt5/plugins/styles/libqgtk2style.so which is provided by qtstyleplugins.
If I remove the shared object, the application is starting, but it's ugly / messy / gui unusable.
Removed qtstyleplugins and the dependent packages:

budgie-desktop-branding-livecd budgie-desktop-branding

EDIT4:
~~Looks like my system install is waaaay too old (5+ years) and something along all customizations I made broke after the latest patch.~~

Maybe rebuilding the qtstyleplugins against the newest qt5-base will fix the issue ?

EDIT5: rebuilding the qtstylesplugins with latest qt5-base really fixes the issue. I guess no PR will be needed, because it's just rebuild and no changes were made to the package.

Cheers,
PY

ReillyBrogan

Rebuilt qtstyleplugins cherry-picked to stable, thanks for the report!

Solarmass

ReillyBrogan I applied this update and rebooted. qBittorrent still uses the same (half-broken) dark theme. I also tried to switch Budgie dark/light toggle, no effect 🙁

ReillyBrogan

Solarmass The qtstyleplugins update has nothing to do with that issue. Can you please open an issue on our package issue tracker for your issue?

presianbg

ReillyBrogan

Actually I noticed the same (odd theme behavior in qbittorrent when moving the window) after deleting qtstylesplugins and it's shared objects.

Solarmass

Try to delete the ~/.cache folder and double check if /usr/lib64/qt5/plugins/styles/libqgtk2style.so is the rebuilt one (check the timestamp on the file).

EDIT: also try to start it like that QT_QPA_PLATFORMTHEME="gtk2" qbittorrent and check if it makes any better.

ReillyBrogan

Also, just cherry-picked an update to our broadcom drivers that should fix a reported issue with failed boots.

plutuplutu

ReillyBrogan
Thanks for working on that! No more freezes indeed, but no wifi yet with lts and current kernels here.

ReillyBrogan

presianbg Try to delete the ~/.cache folder and double check if /usr/lib64/qt5/plugins/styles/libqgtk2style.so is the rebuilt one (check the timestamp on the file).

The .cache folder is used for a TON of things. Please don't give advice to people to delete it.

Instead, people should delete the subfolder that contains the cache they actually want to delete.

Solarmass

presianbg Try to delete the ~/.cache folder and double check if /usr/lib64/qt5/plugins/styles/libqgtk2style.so is the rebuilt one (check the timestamp on the file).

I have actually deleted ~/.cache 😃

libqgtk2style.so seems fine

EDIT: also try to start it like that QT_QPA_PLATFORMTHEME="gtk2" qbittorrent and check if it makes any better.

qbittorrent starts with a very long delay, but it makes it better, tho now we have a scaling problems like huge context menus paddings and some weird icons. This scaling problem I had before.

Solarmass

presianbg EDIT: also try to start it like that QT_QPA_PLATFORMTHEME="gtk2" qbittorrent and check if it makes any better.

I wonder if there an option to start with a forced light theme 🤔

ReillyBrogan

Solarmass qbittorrent starts with a very long delay, but it makes it better, tho now we have a scaling problems like huge context menus paddings and some weird icons. This scaling problem I had before.

This is why qtstyleplugins is disabled by default.

Look, I'm going to be real here. I've asked to see an issue for this on our issue tracker with full reproduction steps to re-create the issue. I tested it in a Budgie VM and it was fine during testing. Other people in this thread are more than welcome to help you debug the issue but I'm not going to spend any further time on it without that issue being created.