Bug 19319

Summary:	SDDM logs into Mate, whatever DE i choose
Product:	Mageia	Reporter:	Morgan Leijström <fri>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	jyri2000, mageiatools
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	sddm-0.13.0-7.mga6.src.rpm	CVE:
Status comment:

Description Morgan Leijström 2016-09-09 10:55:59 CEST

Description of problem:

At the login screen top left i a selection box of different DE.
I have several installed.
Whatever i choose (at least fron Plasma or cinnamon, it always start Mate...

LXDM and LightDM works OK.

(XDM fail to log into any DE, I will post another bug on that)

Comment 1 Morgan Leijström 2016-09-09 12:19:08 CEST

Bug 19320 - XDM fail to log into any DE

Samuel Verschelde 2016-09-09 12:27:32 CEST

Assignee: bugsquad => kde

Comment 2 Jüri Ivask 2016-09-09 13:05:27 CEST

Hmm, strange... I'm daily using SDDM to start my Plasma5 session.
The only difference I could see is that I'm usind sddm.service instead of the default prefdm.service ...

CC: (none) => jyri2000

Comment 3 Rémi Verschelde 2016-09-09 13:10:41 CEST

CC'ing Mageia tools maintainers as I believe this might be another drakdm configuration issue.

I'm also using SDDM daily to start plasma5, with the default config AFAICT (though I've used drakdm twice to switch to LightDM for a time and then back to SDDM a couple months ago). My cauldron is quite old now though so it might not exhibit the same behaviour as yours, especially if some config files are involved.

CC: (none) => mageiatools

Comment 4 Morgan Leijström 2016-09-09 13:20:19 CEST

I normally use LXDM and log into Plasma - always worked, still works.
A couple months ago, I was briefly testing different DE and DM.
While there were quirks, it was not this bad then.
( After long time not tested other DM, today I tested different DM to see if it matters to Bug 19318: No )

Maybe the issue is worse when having several DM/DE installing and updating over time, and it is possible there have been a bug that now is fixed that wrecked some configuration - i dont know how these things work, just an idea...

Comment 5 Morgan Leijström 2016-10-05 13:46:38 CEST

This seem to be solved, at least for me.

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