Bug 1290 - Plymouth exists when encrypted partition password is asked.
Summary: Plymouth exists when encrypted partition password is asked.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: release_blocker critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-15 19:52 CEST by Jari S
Modified: 2011-05-23 14:18 CEST (History)
2 users (show)

See Also:
Source RPM: initscripts-9.21-10.mga1.src.rpm
CVE:
Status comment:


Attachments

Description Jari S 2011-05-15 19:52:30 CEST
Description of problem:
Plymouth exists when encrypted partition password is asked. Normally plymouth should just display password box.

Version-Release number of selected component (if applicable):
initscripts-9.21-10.mga1

How reproducible:
Always.

Steps to Reproduce:
1. just add encrypted partition that uses /etc/crypttab
2. reboot
3.

Correction:
replace line line 995
 [ "$splash_rc" = yes]  && [ -d /usr/share/plymouth ];
with
 if [ "$splash_rc" = "yes" ]  && [ -d /usr/share/plymouth ];
Comment 1 Jari S 2011-05-15 20:03:40 CEST
Another fix needed should be adding "--number-of-tries=3" to "plymouth ask-for-password..." -line (956). Otherwise it will loop forever.
Ahmad Samir 2011-05-15 21:28:12 CEST

CC: (none) => mageia, pterjan

Pascal Terjan 2011-05-20 17:11:25 CEST

Priority: Normal => release_blocker
Severity: normal => critical

Comment 2 Pascal Terjan 2011-05-23 13:51:57 CEST
Patches added

Please provide real patches next time, reading your report it seemed that you were reporting a missing if. But thanks for it anyway :)

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

Comment 3 Jari S 2011-05-23 14:18:18 CEST
It was not missing if just typo i.e. missing "" around yes and space between " ]. For some reason those are required. And next time I'll try to make a patch although it is not my specialty. And you're welcome.

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