Bug 473548 - plasma-pk-updates applet doesn't load under Fedora 37 KDE desktop
Summary: plasma-pk-updates applet doesn't load under Fedora 37 KDE desktop
Status: RESOLVED DUPLICATE of bug 473642
Alias: None
Product: plasma-pk-updates
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-19 22:05 UTC by ND
Modified: 2023-08-25 06:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ND 2023-08-19 22:05:06 UTC
In my Fedora 37 system, since a recent update with more than 350 packages the PackageKit (“Software Updates”) applet in the system tray doesn’t load anymore.

STEPS TO REPRODUCE
1.  Start KDE session in Fedora 37
2. Click the Software Updates icon in the system tray and observe the error message.

OBSERVED RESULT
Message of Software Updates (Get software updates) icon:
Sorry! There was an error loading Software Updates.

file:///usr/share/plasma/plasmoids/org.kde.plasma.pkupdates/contents/ui/main.qml:25:1: plugin cannot be loaded for module “org.kde.plasma.PackageKit”: Cannot load library /usr/lib64/qt5/qml/org/kde/plasma/PackageKit/libplasmapk_qmlplugins.so: (/usr/lib64/qt5/qml/org/kde/plasma/PackageKit/libplasmapk_qmlplugins.so: undefined symbol: _ZN5Solid3Job16staticMetaObjectE)


EXPECTED RESULT
- The loaded applet, updates info.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 37
KDE Plasma Version: 5.27.6
version: plasma-pk-updates-1:0.3.2-13.fc37.i686
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
- Updating via the command line does work.
- I asked on discuss.kde.org whether this is a bug or just my configuration, but in lack of an answer there I am reporting it as a bug here. https://discuss.kde.org/t/plasma-pk-updates-doesnt-load-in-f37/3801?u=andy
Comment 1 Nate Graham 2023-08-22 20:47:02 UTC

*** This bug has been marked as a duplicate of bug 473642 ***