[Bug 1293906] [NEW] plymouth-splash can't be displayed due to race condition with plymouth-stop

[Franz Hsieh]

Public bug reported:

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.

** Affects: oem-priority
     Importance: Undecided
         Status: New

** Affects: plymouth
     Importance: Undecided
         Status: New

** Also affects: plymouth
   Importance: Undecided
       Status: New

** Package changed: plymouth (Ubuntu) => oem-priority

** Tags removed: oem-priority

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1293906

Title:
  plymouth-splash can't be displayed due to race condition with
  plymouth-stop

Status in OEM Priority Project:
  New
Status in The Plymouth splash screen:
  New

Bug 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1293906/+subscriptions