Bug 22828

Summary:	plasma-discover fails to start because org.kde.kirigami is not installed
Product:	Mageia	Reporter:	Mauricio Andrés Bustamante Viveros <neoser10>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fri, marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Mauricio Andrés Bustamante Viveros 2018-03-25 06:31:52 CEST

Description of problem:
When the end user tries to start plasma-discover (this app is 16.12 version)
the app fails to start because module org.kde.kirigami is not installed
The kirigami is installed and the version number is 5.42

Version-Release number of selected component (if applicable):
plasma-discover - 16.12
kirigami 5.42

How reproducible:
Every time the end user tries to start the app (using konsole because the app did not appear in kde menu)

Steps to Reproduce:
1. Execute the plasma-discover from konsole
2. Wait until the prompt returns, inmediatly before the prompt, the error message appears

Marja Van Waes 2018-03-25 18:08:01 CEST

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 1 Mauricio Andrés Bustamante Viveros 2018-04-17 06:00:48 CEST

Reinstalled the MGA6 VM

Testing all the packages installed in this new test, this app starts without issue, works without issue

This can be closed, if to the date of pushing this new plasma to the public no one reports the same

Comment 2 Morgan Leijström 2018-10-11 11:26:39 CEST

In that it crashes by itself a few seconds from start it is similar to Bug 23668 - plasma-discover crash: *** longjmp causes uninitialized stack frame ***

CC: (none) => fri

Comment 3 Aurelien Oudelet 2020-08-16 20:42:48 CEST

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Resolution: (none) => OLD
CC: (none) => ouaurelien
Status: NEW => RESOLVED