Comments

410 Comments
BZ#1875742 digikam-7.1.0 is available
BZ#1952208 digikam: symbol lookup error: /lib64/libdigikamcore.so.7.2.0: undefined symbol: _ZN2cv3dnn14dnn4_v202011178NMSBoxesERKSt6vectorINS_5Rect_IiEESaIS4_EERKS2_IfSaIfEEffRS2_IiSaIiEEfi

Situation improved (though still not perfect) in my testing so far, I'll report details in the bug once I verify/reproduce a couple more times.

BZ#1930514 Plasma System Monitor don't show neither History nor System Stats
karma

Fixes bug #1925346 for me, yay

BZ#1925346 Screen glitches after updating to Kernel 5.10.10

We really need more than 2 days of testing between submission and when big updates like this go stable (may need to disable autokarma for plasma updates for posterity).

BZ#1900983 plasma-pa and pipewire dependencies
BZ#1912517 Audio control gone in KDE after pipewire-pulseaudio installation
BZ#1900983 plasma-pa and pipewire dependencies
BZ#1912517 Audio control gone in KDE after pipewire-pulseaudio installation

True, rpmfusion items typically can only get updated after fedora's (this one) goes to stable updates first.

Good thing I checked, looks like plasma-discover offline updates worked this time.

I'll verify, but the reason why I didn't want this pushed as-is was because it breaks offline updates using plasma-discover.

Yes. alternatively can wait until the next updates push/sync, and do : dnf distro-sync

This update has been unpushed.

Revoking update, no immediate movement or ETA to fix outstanding issues

The version is correct, this is the last version that shipped kde4 support. kde4 support was dropped in newer plasma releases.

Yup, breakage, offline updates are broken for me too.

This update was only one small step to fix the aforementioned bug, in that it should ensure baloo_file processes get shutdown on logout. Are you saying those processes continue to persist after logout for you?