Bug 32924

Summary:	plasma-discover crashes on startup on flatpak-backend plugin
Product:	Mageia	Reporter:	Cyril Levet <cyril.levet0780>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	andrewsfarm, geiger.david68210, philippedidier, sysadmin-bugs
Version:	9	Keywords:	advisory, validated_update
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	MGA9-64-OK
Source RPM:	appstream-0.15.5-1.mga9	CVE:
Status comment:
Bug Depends on:	32885
Bug Blocks:

Description Cyril Levet 2024-03-02 07:44:42 CET

Description of problem: plasma-discover crashes at startup when checking for updates on the flatpak-backend plugin.

plasma-discover
adding empty sources model QStandardItemModel(0x18a7710)
Failed to refresh appstream metadata for  kdeapps :  "Error updating appstream2: No such ref 'appstream2/x86_64' in remote kdeapps; Error updating appstream: No such ref 'appstream/x86_64' in remote kdeapps"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:288:18: QML QQuickItem*: Binding loop detected for property "implicitWidth"

** (process:38215): WARNING **: 07:28:30.514: '' is not a valid XDG category name, search results might be invalid or empty.

** (process:38215): WARNING **: 07:28:30.517: '\xc0&\u0019\x8ep\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.127")
plasma-discover: symbol lookup error: /usr/lib64/qt5/plugins/discover/flatpak-backend.so: undefined symbol: _ZNK9AppStream4Pool20componentsByBundleIdENS_6Bundle4KindERK7QStringb

c++filt _ZNK9AppStream4Pool20componentsByBundleIdENS_6Bundle4KindERK7QStringb                                                                                                                                       
AppStream::Pool::componentsByBundleId(AppStream::Bundle::Kind, QString const&, bool) const

The configurated flatpak repositories are : flathub, kdeapps

Version-Release number of selected component (if applicable): discover-5.27.10-1.mga9


How reproducible: Always


Steps to Reproduce:
1. Launch plasma-discover when flatpak updates are available.

Comment 1 David GEIGER 2024-03-02 09:41:57 CET

Hmmm! there are missing pkgs which have not been moved with the big plasma update (bug 32885):

Package in 9/Core/Updates_testing:
=====================

appstream-0.16.4-1.mga9
libappstream-devel-0.16.4-1.mga9
libappstream-gir1.0-0.16.4-1.mga9
libappstream4-0.16.4-1.mga9
libappstreamqt-devel-0.16.4-1.mga9
libappstreamqt2-0.16.4-1.mga9

lib64appstream-devel-0.16.4-1.mga9
lib64appstream-gir1.0-0.16.4-1.mga9
lib64appstream4-0.16.4-1.mga9
lib64appstreamqt-devel-0.16.4-1.mga9
lib64appstreamqt2-0.16.4-1.mga9

From SRPMS:
appstream-0.16.4-1.mga9.src.rpm

Depends on: (none) => 32885
Assignee: bugsquad => qa-bugs
CC: (none) => geiger.david68210

Comment 2 sturmvogel 2024-03-02 17:23:07 CET

*** Bug 32925 has been marked as a duplicate of this bug. ***

CC: (none) => philippedidier

katnatek 2024-03-02 18:30:40 CET

Source RPM: discover-5.27.10-1.mga9.src.rpm => appstream-0.15.5-1.mga9

katnatek 2024-03-02 18:32:51 CET

CC: (none) => andrewsfarm

Comment 3 katnatek 2024-03-02 18:34:43 CET

Usually we reopen the previous bug, in this case bug#32885
So what we must do?

Comment 4 katnatek 2024-03-02 19:57:27 CET

Real Hardware Mageia 9 x86_64

rpm -qa|grep appstream
lib64appstream4-0.15.5-1.mga9
appstream-0.15.5-1.mga9
appstream-glib-i18n-0.8.0-2.mga9
lib64appstream-glib8-0.8.0-2.mga9
lib64appstreamqt2-0.15.5-1.mga9
appstream-util-0.8.0-2.mga9


LC_ALL=C urpmi --auto --auto-update
medium "QA Testing (32-bit)" is up-to-date
medium "QA Testing (64-bit)" is up-to-date
medium "Core Release (distrib1)" is up-to-date
medium "Core Updates (distrib3)" is up-to-date
medium "Nonfree Release (distrib11)" is up-to-date
medium "Nonfree Updates (distrib13)" is up-to-date
medium "Tainted Release (distrib21)" is up-to-date
medium "Tainted Updates (distrib23)" is up-to-date
medium "Core 32bit Release (distrib31)" is up-to-date
medium "Core 32bit Updates (distrib32)" is up-to-date
medium "Nonfree 32bit Release (distrib36)" is up-to-date
medium "Tainted 32bit Release (distrib41)" is up-to-date
medium "Tainted 32bit Updates (distrib42)" is up-to-date

installing //home/katnatek/qa-testing/x86_64/lib64appstreamqt2-0.16.4-1.mga9.x86_64.rpm                                             
//home/katnatek/qa-testing/x86_64/lib64appstream4-0.16.4-1.mga9.x86_64.rpm
//home/katnatek/qa-testing/x86_64/appstream-0.16.4-1.mga9.x86_64.rpm
Preparing...                     ##################################################################################################
      1/3: lib64appstream4       ##################################################################################################
      2/3: appstream             ##################################################################################################
      3/3: lib64appstreamqt2     ##################################################################################################
      1/4: removing lib64appstreamqt2-0.15.5-1.mga9.x86_64
                                 ##################################################################################################
      2/4: removing appstream-0.15.5-1.mga9.x86_64
                                 ##################################################################################################
      3/4: removing lib64appstream4-0.15.5-1.mga9.x86_64
                                 ##################################################################################################
      

Packages update without issue, I not use discover, so I can't test if these packages fix the reported issue

Comment 5 Philippe Didier 2024-03-02 19:59:31 CET

I have installed :

appstream-0.16.4-1.mga9
lib64appstream-gir1.0-0.16.4-1.mga9
lib64appstream4-0.16.4-1.mga9
lib64appstreamqt2-0.16.4-1.mga9

from mageia9/core/updates_testing

The bug is resolved for me !

Thanks to David !

When the appstream stuff will have been moved from updates_testing to updates this bug may be closed

Comment 6 katnatek 2024-03-02 20:02:28 CET

(In reply to katnatek from comment #4)
Related to mismatch of packages, I forgot disable 3rd parthy repositories and I get update of one of the packages I just not want to include in the report (I didn't must edit the terminal output)

Comment 7 Philippe Didier 2024-03-02 20:03:10 CET

Forgot to say discover works now for the flatpak stuff (I only use it for updating flatpak suff, I don't use it for mageia rpms, letting urpmi doing these updates)

Comment 8 katnatek 2024-03-02 20:03:36 CET

Due comment#5 I give OK

katnatek 2024-03-02 20:03:49 CET

Whiteboard: (none) => MGA9-64-OK

Comment 9 Thomas Andrews 2024-03-02 20:05:07 CET

You beat me to it. Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

katnatek 2024-03-02 20:27:34 CET

Keywords: (none) => advisory

Comment 10 Mageia Robot 2024-03-02 20:59:21 CET

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0090.html

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