Bug 18686 - Plasma uses Kickoff by default
Summary: Plasma uses Kickoff by default
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-11 00:27 CEST by David Walser
Modified: 2016-07-29 17:04 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David Walser 2016-06-11 00:27:49 CEST 
I could have sworn we were going to use the very nice normal application menu by default, but in a VM I just upgraded to Mageia 6, it was using Kickoff by default.

A side note - all desktop settings were lost, which has never happened in a KDE update.  The closest was KDE1->KDE2 in which some settings were lost.  I seem to recall you saying this would be addressed too, but just making a reminder now.
Comment 1 David Walser 2016-06-11 23:36:36 CEST 
Should be fixed in plasma-desktop-5.6.4-3.mga6.  Thanks Nicolas!
Comment 2 David Walser 2016-06-11 23:37:02 CEST 
Plasma rules!

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

Comment 3 David Walser 2016-06-13 15:49:03 CEST 
I guess I'll reopen this one, since the fix didn't work and just broke Plasma :o(

Now the Panel doesn't run at all.  Even right-clicking the desktop and doing Add Panel > Default Panel doesn't give you the panel.  This has also broken the latest iteration of the Plasma Live DVD, as you may have already heard.

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

Comment 4 David Walser 2016-06-16 21:46:06 CEST 
I reverted the patch for now.  You can try again when you have time.
Comment 5 David Walser 2016-07-29 17:04:46 CEST 
The Default Panel appears to use the correct menu now.  Closing as fixed.  We still have the issue of Plasma starting with an empty panel though.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.