Activity log for bug #1293906

Date Who What changed Old value New value Message
2014-03-18 03:06:37 Franz Hsieh bug added bug
2014-03-18 03:07:10 Franz Hsieh bug task added plymouth
2014-03-18 03:08:48 Franz Hsieh affects plymouth (Ubuntu) oem-priority
2014-03-18 03:09:20 Franz Hsieh tags oem-priority
2014-03-18 12:11:34 Ara Pulido oem-priority: status New Incomplete
2014-03-19 01:50:54 Franz Hsieh nominated for series oem-priority/precise
2014-03-19 01:50:54 Franz Hsieh bug task added oem-priority/precise
2014-03-19 01:53:26 Franz Hsieh description There might be race condition between plymouth-splash and plymouth-stop. Normally the calling sequence should be: plymouth ... plymouth-splash ... plymouth-stop On the fail unit it looks like: plymouth ... plymouth-stop ... plymouth-splash Therefore the splash screen can't be displayed. The timing that plymouth-splash would be executed relies on these conditions: (ref: /etc/init/plymouth-splash.conf) 1) plymouth should be executed and, 2) graphics-device-added or drm-device-added event has been emitted. Condition 1 is always satisfied, so the possible reason of why plymouth-splash is not executed might be the graphic takes too many time to initial. OS version: Ubuntu 12.04.4 Precise Package version: plymouth 0.8.2-2ubuntu31.1 There might be race condition between plymouth-splash and plymouth-stop. Normally the calling sequence should be: plymouth ... plymouth-splash ... plymouth-stop On the fail unit it looks like: plymouth ... plymouth-stop ... plymouth-splash Therefore the splash screen can't be displayed. The timing that plymouth-splash would be executed relies on these conditions: (ref: /etc/init/plymouth-splash.conf)   1) plymouth should be executed and,   2) graphics-device-added or drm-device-added event has been emitted. Condition 1 is always satisfied, so the possible reason of why plymouth-splash is not executed might be the graphic takes too many time to initial.
2014-05-05 11:12:52 Ara Pulido oem-priority: status Incomplete Invalid
2014-05-05 11:12:59 Ara Pulido oem-priority/precise: status New Invalid