Bug 1413 - plyomouth glitch during the boot step
Summary: plyomouth glitch during the boot step
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Atelier Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 18:32 CEST by Marcello Anni
Modified: 2013-04-09 11:52 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
plymouth glitch (815.91 KB, image/jpeg)
2011-05-24 18:32 CEST, Marcello Anni
Details
New set of progress bar (28.84 KB, application/x-gzip)
2011-05-24 18:59 CEST, Thorsten vanLil
Details

Description Marcello Anni 2011-05-24 18:32:04 CEST
Description of problem:

hi,

i attach the screenshot of the boot phase, i have this behaviour since quite a lot of time but i couldn't attach the photo.

here it is


cheers,
Marcello
Comment 1 Marcello Anni 2011-05-24 18:32:40 CEST
Created attachment 462 [details]
plymouth glitch
Comment 2 Thorsten vanLil 2011-05-24 18:59:14 CEST
Created attachment 464 [details]
New set of progress bar

I've created a new set of progress bar.
Comment 3 Thorsten vanLil 2011-05-24 19:00:54 CEST
This should fix the issue. But I'm curious, how this is could happen.

Marcello, can you please make a picture of the whole screen. I'd like to check if the rest is ok.

Greetings,
Thorsten

CC: (none) => tvl83

Comment 4 Marcello Anni 2011-05-24 19:28:01 CEST
it's quite difficult as i should use the e-mail to send the image from the phone to the pc. anyway the rest is ok.


cheers,
Marcello


PS= i'm waiting for testing the update :)
Comment 5 Anne Nicolas 2011-05-26 11:39:24 CEST
committed, will be submitted with fixed backgrounds soon

CC: (none) => ennael1

Comment 6 Anne Nicolas 2011-05-26 16:05:23 CEST
fixed in 1.5.0.16

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

Nicolas Vigier 2013-04-09 11:52:44 CEST

Assignee: mageia-artwork => atelier-bugs


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