| Summary: | ugly launch screen when you have an encrypted partition | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Pierre Opter <p.opter> |
| Component: | RPM Packages | Assignee: | Donald <watersnowrock> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Normal | CC: | fri, mageia, sysadmin-bugs, watersnowrock |
| Version: | Cauldron | ||
| Target Milestone: | Mageia 6 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | MGA5TOO | ||
| Source RPM: | mageia-theme | CVE: | |
| Status comment: | |||
| Attachments: | picture of the launch screen | ||
|
Description
Pierre Opter
2015-06-28 19:13:39 CEST
Pierre Opter
2015-06-28 19:16:48 CEST
CC:
(none) =>
sysadmin-bugs
Sander Lepik
2015-06-28 19:18:34 CEST
CC:
(none) =>
mageia Could you provide a screenshot or a photo? Created attachment 6789 [details]
picture of the launch screen
picture taken with my Jolla Phone
Thanks, that's not pretty indeed :) Fixing it would imply changing the plymouth animation so that the Mageia logo is not on the center of the screen. The issue is that then it's harder to make sure that the logo won't be cropped or badly placed depending on the user's screen resolution, so I'm not sure if it's worth changing. I'll keep this in mind when working on the artwork for Mageia 6 at least. Assignee:
bugsquad =>
atelier-bugs
Rémi Verschelde
2015-06-28 21:57:46 CEST
Source RPM:
(none) =>
mageia-theme Yeah I'm with Remi on this, fix at mga6. Just off my head, it should be possible to move the logo placement such that it will always be visible. Something like: Max resolution we support is 1920x1440 for plymouth? Min res supported 800x600 I think Logo dimensions are 600x420 I think So there are 600 - 420/2 available pixels above and below that we can move the logo into that will never be cropped. THat being said, I bought it would solve the issue on all resolutions as the logo size increases as the resolution decreases last I checked. I'll have a look at this when I get some time. A plymouth overhaul is something we need to do for mga6 anyway, maybe we can backport some of the fixes to 5 if really needed. I've set target to 6 and assigned it to me for now. Status:
NEW =>
ASSIGNED This seem to be fixed now, right? CC:
(none) =>
fri (In reply to Morgan Leijström from comment #5) > This seem to be fixed now, right? Closing. Reopen if needed. Status:
ASSIGNED =>
RESOLVED |