Bug 20510

Summary:	Updating M6 STA2 with proposed packages breaks the start menu
Product:	Mageia	Reporter:	Vladimir Zawalinski <vzawalin1>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	High	CC:	mageia, marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Vladimir Zawalinski 2017-03-17 12:37:48 CET

After installing and rebooting (M6 STA2), I saw the three boxes with a question mark on a dark background as reported by others, but otherwise all was fine ....
until I accepted the invitation to apply updates. After some 800(?) updated
packages, I rebooted and found the Menu button on the left of the bottom
panel no longer worked, nor could I add panel widgets (a menu in
particular).  Instead, the menu button threw the following message:-

Error loading QML file:
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:73:9:
Type MenuRepresentation unavailable
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/MenuRepresentation.qml:303:5:
Type PlasmaComponents.TextField unavailable
file:///usr/lib64/qt5/qml/org/kde/plasma/components/TextField.qml:25:1:
module "org.kde.kconfig" is not installedescription of problem:

As the release without updates worked fine, the problem is in one of the many updates that are offered post installation.

Rémi Verschelde 2017-03-17 12:48:16 CET

Priority: Normal => High
Assignee: bugsquad => kde
Source RPM: Unknowm => (none)
Severity: normal => major

Comment 1 Marja Van Waes 2017-03-17 15:28:57 CET

A lot of KDE updates were pushed very few days ago, and yesterday all mirrors were struggling to get updated (also because of other updates that were pushed)

Today it's better, but there are still some mirrors that have a time stamp from yesterday or longer ago.

(The time stamp is usually the first file that gets updated when a mirror is being updated, so it's better to not use a mirror with an outdated time stamp. Having a good time stamp is, unfortunately, no guarantee all packages on the mirror are up-to-date)

Can you update your system again, preferably from a mirror that's "green" on this page http://mirrors.mageia.org/status
to see whether an additional update fixes the issue?

CC: (none) => marja11

Comment 2 Nicolas Lécureuil 2017-03-17 17:13:06 CET

just tested on cauldrons's konqueror and www.ssllabs.com told me that the user agent is not vulnerable.

 => closing

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

Comment 3 Nicolas Lécureuil 2017-03-17 17:13:25 CET

sorry wrong bug :)

Status: RESOLVED => UNCONFIRMED
Resolution: FIXED => (none)
Ever confirmed: 1 => 0

David Walser 2017-03-18 22:55:45 CET

Status: UNCONFIRMED => NEW
Ever confirmed: 0 => 1

Comment 4 Vladimir Zawalinski 2017-03-28 08:30:19 CEST

(In reply to Marja van Waes from comment #1)
> A lot of KDE updates were pushed very few days ago, and yesterday all
> mirrors were struggling to get updated (also because of other updates that
> were pushed)
> 
> Today it's better, but there are still some mirrors that have a time stamp
> from yesterday or longer ago.
> 
> (The time stamp is usually the first file that gets updated when a mirror is
> being updated, so it's better to not use a mirror with an outdated time
> stamp. Having a good time stamp is, unfortunately, no guarantee all packages
> on the mirror are up-to-date)
> 
> Can you update your system again, preferably from a mirror that's "green" on
> this page http://mirrors.mageia.org/status
> to see whether an additional update fixes the issue?

Hi Marja,

just updated from repo dated 210317 and all went well.  Sorry I couldn't do this earlier.

Please close this bug.

regards

Vlad

Comment 5 Rémi Verschelde 2017-03-28 08:40:50 CEST

Closing.

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