Bug 12488 - MCC splash screen (Mageia 4RC) does not match anymore the default background
Summary: MCC splash screen (Mageia 4RC) does not match anymore the default background
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Anne Nicolas
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-31 10:33 CET by Jérôme Borme
Modified: 2014-02-02 18:01 CET (History)
1 user (show)

See Also:
Source RPM: drakconf
CVE:
Status comment:


Attachments
Screenshot of MCC launching on te default background (198.33 KB, image/png)
2014-01-31 11:47 CET, Jérôme Borme
Details

Description Jérôme Borme 2014-01-31 10:33:27 CET
Until days ago in Mageia 4RC, the Control Center had a splash screen which perfectly matched the default background (stylized blooming tree). The text «launching MCC» in white letters was then displayed seamlessly on the background. Since last update of the 4RC, the default background slightly changed (the tree branches are not at the same place), so the MCC splash screen now visibly mismatches.

Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2014-01-31 11:10:31 CET
scrrenshot ?
Comment 2 Jérôme Borme 2014-01-31 11:47:04 CET
Created attachment 4908 [details]
Screenshot of MCC launching on te default background

I drew a red frame to make more visible the actual limits of the splashscreen. It's "ok" like this, but few days ago (before a large update of Mageia 4RC), the flowers of the background matched exactly the MCC splashscreen, resulting in a beautiful result (just like the text would be drawn in transparency) that I found really great when I saw it first.
Thierry Vignaud 2014-01-31 21:29:43 CET

CC: (none) => thierry.vignaud
Assignee: bugsquad => ennael1
Source RPM: (none) => drakconf

Comment 3 Jérôme Borme 2014-02-02 18:01:38 CET
I reinstalled Mageia 4 RC (without any updates) and I cannot reproduce it the way I thought. I'm probably mistaken with this report so closing.

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


Note You need to log in before you can comment on or make changes to this bug.