Bug 20880

Summary:	Distribution Upgrade: Multi DE defaults to Plasma DE
Product:	Mageia	Reporter:	Ben McMonagle <westel>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	kde, mageiatools, marja11, ngompa13
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Ben McMonagle 2017-05-17 06:57:30 CEST

Description of problem: after the upgrade, Plasma DE is presented as the default DE, even if the upgrade is started from a different DE, and KDE is one of the installed DE.


Version-Release number of selected component (if applicable):


How reproducible: every time


Steps to Reproduce:
1. update a multi DE 5(.1) system to latest packages, logout to DE that is not KDE.
2. as per https://wiki.mageia.org/en/QA_process_for_testing_upgrades, How to do an upgrade: in a terminal run *killall mgaapplet*,then *mgaapplet --testing*
3. wait for the upgrade to complete, reboot
4.Plasma is the default DE presented

Comment 1 Marja Van Waes 2017-05-17 11:39:46 CEST

Did this ever work differently on upgrades?

(I think multi-DE installs always defaulted to KDE/Plasma too for me, if that DE was among the installed ones, maybe whichever setting causes that, causes this, too?)

I have no idea whether KDE4/Plasma5 rules, or whether there's a setting in installer somewhere.

Keywords: (none) => NEEDINFO
CC: (none) => kde, mageiatools, marja11

Comment 2 Rémi Verschelde 2017-05-17 12:51:24 CEST

I don't think there's any logic for that, it's just by chance that Plasma is selected as the default.

It depends on many factors, which are not covered in the initial report:
- the desktop manager installed (a KDM -> SDDM upgrade won't behave the same as a LXDM -> LXDM upgrade)
- the DEs installed
- the DE configured as main DE in the DM configuration

If your default DE was KDE, which no longer exists, the DM will have to pick another one, which could be Plasma, or could be something else (e.g. if it just picks the first of the list, or the one with the same order as KDE had).

If your DM was KDM, it might be that SDDM is configured to default to Plasma when no other directive is given, but that sounds sensible.

At any rate, it doesn't appear to be a bug to me. If you do an upgrade from Xfce using LightDM, and it starts Plasma after the upgrade, then yeah, something is off. But if the scenario was KDM -> SDDM, it seems fine to me.

Comment 3 Neal Gompa 2017-05-17 12:53:30 CEST

This is a consequence of how the KDE SC 4 to Plasma 5 upgrade works in this particular scenario, so I would also suggest that this isn't a bug.

CC: (none) => ngompa13

Comment 4 Marja Van Waes 2017-09-08 00:40:35 CEST

@ Ben

I'm now assuming that KDM was indeed the used display manager. I agree with Rémi and Neal that this is not a bug, then.

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