Update applet crashes

ben79 · October 14, 2017, 7:10pm

OK that is Discover and we know that Discover is broken due to outdated kirigami2 package. Thanks for reporting.

There is an updated package in Main-testing repo to fix this issue here.

Please install that and let us know if that fixes problem.

alangea · October 15, 2017, 9:11am

Unfortunately coninues crashing.

ben79 · October 15, 2017, 5:21pm

I can’t read your mind. Still crashes after what? And please be specific and post code as code.

Anyway there are now packages in regular repos to fix discover including new Discover packages and new kirigami package so no need to go to main-testing repo. Just wait till the packages get to your mirror and update in Konsole with ‘urpmi --auto-update’.

alangea · October 15, 2017, 5:41pm

I followed your suggest, installed thtat package and tried to update packages by Discover; then the applet crashed, and I used uprmi – auto-updare to update packages.
At the moment kirigami-5.38 -1-omv version is installed.
I will wait for new packages as you suggested.

ben79 · October 15, 2017, 7:32pm

Arrrggghhh… That probably, almost certainly, is the updated package. So how you do this post code as code like:

$ rpm -qa kirigami
kirigami-5.38.0-1-omv2015.0.x86_64

and the updated Discover packages are:

$ rpm -qa | grep discover
lib64hpdiscovery0-3.16.10-1-omv2015.0.x86_64
discover-5.10.5-2-omv2015.0.x86_64
discover-backend-packagekit-5.10.5-2-omv2015.0.x86_64
discover-backend-flatpak-5.10.5-2-omv2015.0.x86_64
discover-backend-kns-5.10.5-2-omv2015.0.x86_64
discover-notifier-5.10.5-2-omv2015.0.x86_64

so if you do have all of those packages and Discover is still crashing then you have another problem. And you have to have all of the packages.

You could try re-installing the above packages with:

# urpmi --replacepkgs discover discover-backend-packagekit discover-backend-flatpak discover-backend-kns discover-notifier kirigami

But do note that for --replacepkgs to work the packages have to be installed already.

alangea · October 17, 2017, 7:46pm

root@localhost alangea]# rpm -qa kirigami
kirigami-5.38.0-1-omv2015.0.x86_64

[root@localhost alangea]# rpm -qa | grep discover
lib64hpdiscovery0-3.16.10-1-omv2015.0.x86_64
eclipse-p2-discovery-4.4.1-8.2-omv2015.0.x86_64
discover-5.10.5-2-omv2015.0.x86_64
discover-backend-packagekit-5.10.5-2-omv2015.0.x86_64
discover-backend-flatpak-5.10.5-2-omv2015.0.x86_64
discover-notifier-5.10.5-2-omv2015.0.x86_64
discover-backend-kns-5.10.5-2-omv2015.0.x86_6

[root@localhost alangea]# urpmi --replacepkgs discover discover-backend-packagekit discover-backend-flatpak discover-backend-kns discover-notifier kirigami

$MIRRORLIST: media/main/updates/discover-backend-kns-5.10.5-2-omv2015.0.x86_64.rpm
$MIRRORLIST: media/main/updates/kirigami-5.38.0-1-omv2015.0.x86_64.rpm                                                                                                                 
$MIRRORLIST: media/main/updates/discover-backend-flatpak-5.10.5-2-omv2015.0.x86_64.rpm                                                                                                 
$MIRRORLIST: media/main/updates/discover-5.10.5-2-omv2015.0.x86_64.rpm                                                                                                                 
$MIRRORLIST: media/main/updates/discover-backend-packagekit-5.10.5-2-omv2015.0.x86_64.rpm                                                                                              
$MIRRORLIST: media/main/updates/discover-notifier-5.10.5-2-omv2015.0.x86_64.rpm

installazione di discover-backend-flatpak-5.10.5-2-omv2015.0.x86_64.rpm discover-backend-packagekit-5.10.5-2-omv2015.0.x86_64.rpm discover-5.10.5-2-omv2015.0.x86_64.rpm discover-notifier-5.10.5-2-omv2015.0.x86_64.rpm discover-backend-kns-5.10.5-2-omv2015.0.x86_64.rpm kirigami-5.38.0-1-omv2015.0.x86_64.rpm da /var/cache/urpmi/rpms
In preparazione… #########################################################################################################################################################
1/6: kirigami #########################################################################################################################################################
2/6: discover #########################################################################################################################################################
3/6: discover-backend-flatpak
#########################################################################################################################################################
4/6: discover-backend-packagekit
#########################################################################################################################################################
5/6: discover-notifier #########################################################################################################################################################
6/6: discover-backend-kns #########################################################################################################################################################

STILL CRASHES

mandian · October 17, 2017, 8:18pm

Puoi provare ad avviare discourse da terminale e postare l’output?

ben79 · October 17, 2017, 8:36pm

Mi dispiace che tu continui ad avere problemi. Il suggerimento di Mandian di partire da Konsole e post out put è un ottimo. Si sta avvicinando al tempo per un rapporto di bug, a meno che tale output punti a qualcosa di semplice.

alangea · October 28, 2017, 7:23pm

In che senso “avviare discourse” ?
Ciò che ho riportato è il risulato dei comandi suggeriti da ben79…

rugyada · October 28, 2017, 8:38pm

Credo che intendesse avviare discover, non discourse

alangea · October 28, 2017, 9:15pm

qual è il comando per avviare discover ?
se scrivo discover non riconosce il comando…

rugyada · October 28, 2017, 9:24pm

Prova con
$ plasma-discover

alangea · October 28, 2017, 9:27pm

da root console:

root@openmandriva alangea]# plasma-discover
No protocol specified
QXcbConnection: Could not connect to display :0
Annullato (core dump creato)

rugyada · October 28, 2017, 9:41pm

Discover si lancia da utente, non da root

alangea · October 28, 2017, 9:42pm

OK:

[alangea@openmandriva ~]$ plasma-discover
_IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain
_IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain
Qt: Session management error: Could not open network socket
QQmlApplicationEngine failed to load component
qrc:/qml/DiscoverWindow.qml:9 Type Kirigami.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop/ApplicationWindow.qml:25 Type Base.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ApplicationWindow.qml:97 Type AbstractApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:21 module “QtQuick.Controls” version 2.0 is not installed

Errors when loading the GUI

(process:12033): flatpak-WARNING **: Unable to create FlatpakInstallation for: Permesso negato
Failed to call flatpak_get_system_installations: Permesso negato

(process:12033): OSTree-CRITICAL **: ostree_repo_open: assertion ‘error == NULL || *error == NULL’ failed
Failed to setup flatpak installations: Permesso negato
invalid kns backend! “/etc/xdg/servicemenu.knsrc” because: “Config group not found! Check your KNS3 installation.”
invalid kns backend! “/etc/xdg/ksysguard.knsrc” because: “Config group not found! Check your KNS3 installation.”
Discarding invalid backend “flatpak-backend”
Discarding invalid backend “servicemenu.knsrc”
Discarding invalid backend “ksysguard.knsrc”

rugyada · October 28, 2017, 9:48pm

Ecco, qui però io mi fermo perchè l’output te lo avevano chiesto Ben e Mandian.
Per me è arabo

PS>
Ricordati di postare il codice come testo preformattato ( icona </> )

alangea · October 28, 2017, 10:25pm

Non ho capito cosa devo fare…

rugyada · October 29, 2017, 9:22am

Quando devi pubblicare parti di codice, come ad esempio l’output della console o i comandi dati nel terminale, dopo aver incollato il testo lo evidenzi tutto e lo formatti come codice usando l’apposita icona:

alangea · October 29, 2017, 10:40am

alangea:

[alangea@openmandriva ~]$ plasma-discover
_IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain
_IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain
Qt: Session management error: Could not open network socket
QQmlApplicationEngine failed to load component
qrc:/qml/DiscoverWindow.qml:9 Type Kirigami.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop/ApplicationWindow.qml:25 Type Base.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ApplicationWindow.qml:97 Type AbstractApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:21 module “QtQuick.Controls” version 2.0 is not installed

Errors when loading the GUI

(process:12033): flatpak-WARNING **: Unable to create FlatpakInstallation for: Permesso negato
Failed to call flatpak_get_system_installations: Permesso negato

(process:12033): OSTree-CRITICAL **: ostree_repo_open: assertion ‘error == NULL || *error == NULL’ failed
Failed to setup flatpak installations: Permesso negato
invalid kns backend! “/etc/xdg/servicemenu.knsrc” because: “Config group not found! Check your KNS3 installation.”
invalid kns backend! “/etc/xdg/ksysguard.knsrc” because: “Config group not found! Check your KNS3 installation.”
Discarding invalid backend “flatpak-backend”
Discarding invalid backend “servicemenu.knsrc”
Discarding invalid backend “ksysguard.knsrc”

[alangea@openmandriva ~]$ plasma-discover

_IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain
_IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain
Qt: Session management error: Could not open network socket
QQmlApplicationEngine failed to load component
qrc:/qml/DiscoverWindow.qml:9 Type Kirigami.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop/ApplicationWindow.qml:25 Type Base.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ApplicationWindow.qml:97 Type AbstractApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:21 module “QtQuick.Controls” version 2.0 is not installed

Errors when loading the GUI

(process:12033): flatpak-WARNING **: Unable to create FlatpakInstallation for: Permesso negato
Failed to call flatpak_get_system_installations: Permesso negato

(process:12033): OSTree-CRITICAL **: ostree_repo_open: assertion ‘error == NULL || *error == NULL’ failed
Failed to setup flatpak installations: Permesso negato
invalid kns backend! “/etc/xdg/servicemenu.knsrc” because: “Config group not found! Check your KNS3 installation.”
invalid kns backend! “/etc/xdg/ksysguard.knsrc” because: “Config group not found! Check your KNS3 installation.”
Discarding invalid backend “flatpak-backend”
Discarding invalid backend “servicemenu.knsrc”
Discarding invalid backend "ksysguard.knsrc"Preformatted text

Spero sia corretto…

mandian · October 30, 2017, 5:20pm

Puoi postare il risultato del seguente comando?

rpm -qa | grep qt5-qtquickcontrols