Bug 32925 - since the last update for Mageia9 plasma-discover crashes
Summary: since the last update for Mageia9 plasma-discover crashes
Status: RESOLVED DUPLICATE of bug 32924
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-02 16:53 CET by Philippe Didier
Modified: 2024-03-02 17:23 CET (History)
0 users

See Also:
Source RPM: discover-5.27.10-1
CVE:
Status comment:


Attachments

Description Philippe Didier 2024-03-02 16:53:32 CET
Description of problem:

Since the last update in Mageia 9
plasma-dicover crashes when trying to list updates to install
(its icon appears meaning that there are updates... but when clicking on it, discover starts and crashes when looking for updates)

Here's what happens when launched from a console :

[philippe@localhost ~]$ plasma-discover
adding empty sources model QStandardItemModel(0xea8650)
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:288:18: QML QQuickItem*: Binding loop detected for property "implicitWidth"

** (process:1158965): WARNING **: 16:43:19.335: '' is not a valid XDG category name, search results might be invalid or empty.

** (process:1158965): WARNING **: 16:43:19.338: '\xc0\xdb$\u0011C\u007f' is not a valid XDG category name, search results might be invalid or empty.
no component found for "org.mageia.mageia"
packagekitqt.transaction: Unknown Transaction property: "Sender" QVariant(QString, ":1.325")
plasma-discover: symbol lookup error: /usr/lib64/qt5/plugins/discover/flatpak-backend.so: undefined symbol: _ZNK9AppStream4Pool20componentsByBundleIdENS_6Bundle4KindERK7QStringb

NB
Before the update Discover worked perfectly (I use it to update flatpak stuff)
Comment 1 sturmvogel 2024-03-02 17:23:07 CET
...

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

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.