Bug 19665

Summary:	sddm background appears mixed with white before dialog appears
Product:	Mageia	Reporter:	Barry Jackson <zen25000>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	bequimao.de, ghibomgx
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	sddm	CVE:
Status comment:

Description Barry Jackson 2016-10-27 13:44:50 CEST

Description of problem:
After plymouth at the start of sddm the background now looks as if is transparent overlaid on a white background.

This has appeared since the last updates around 23 Oct 2016

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Rémi Verschelde 2016-10-27 13:45:42 CEST

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

Ulrich Beckmann 2016-10-27 15:29:15 CEST

CC: (none) => bequimao.de

Comment 1 Giuseppe Ghibò 2016-10-27 18:55:49 CEST

Can you try to edit the file /etc/sddm.conf and changing the current theme from mga-coffee to elarun, like this:

Current=mga-coffee

to

Current=elarun

and see whether you get the same?

Comment 2 Barry Jackson 2016-10-27 21:45:02 CEST

(In reply to Giuseppe GhibÃ² from comment #1)
> Can you try to edit the file /etc/sddm.conf and changing the current theme
> from mga-coffee to elarun, like this:
> 
> Current=mga-coffee
> 
> to
> 
> Current=elarun
> 
> and see whether you get the same?

Well the problem is unchanged, in that there are periods of our background diluted with white, but the sddm login dialog now appears with a KDE background, not ours.

I think two videos are needed here.

Comment 3 Barry Jackson 2016-10-27 22:36:36 CEST

Original 
http://mtf.no-ip.co.uk/pub/linux/barjac/video/mga-coffee.mp4

Problem occurs at 11secs before login and at 18secs just after login.

with elarun:
http://mtf.no-ip.co.uk/pub/linux/barjac/video/elarun.mp4
Same issue - just wrong theme.

Comment 4 Ulrich Beckmann 2016-12-18 17:10:30 CET

I had the same issue here. It looks as if it has gone now. Anyone can confirm this?

Ulrich

Comment 5 Giuseppe Ghibò 2016-12-18 18:28:55 CET

This has been fixed in xinitr-2.14.21-22.mga6

Comment 6 Giuseppe Ghibò 2016-12-18 18:29:23 CET

I meant xinitrc-2.14.21-22.mga6

Comment 7 Barry Jackson 2016-12-19 18:57:31 CET

I confirm that this seems fixed on two machines recently updated here so closing.

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