[Bug 1093313] [NEW] plymouth-stop.conf needs "instance" because it may need to be run multiple times

[J G Miller]

Public bug reported:

PRETTY_NAME="Ubuntu quantal (12.10)"
VERSION="12.10, Quantal Quetzal"

Package: plymouth
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Architecture: i386
Version: 0.8.4-0ubuntu3


Currently, the init job plymouth-stop will only run once during the bootup sequence, but in cases where the user has installed more than one display manager, it will need to be run more than once.

Consider this example.

xdm is installed and made the default-display-manager.

plymouth-stop is called on  stopped rc RUNLEVEL=[2345]  (JOB is rc), xdm
runs and Xorg starts.

lightdm is then installed but xdm is left as the default-display-
manager.

plymouth-stop is now called on starting lightdm (JOB is lightdm) but the
case statement results in exit 0 with no action as lightdm is expected
to take care of stopping plymouth.

However in the lightdm init configuration file, the lightdm job stops
without doing anything because lightdm is not the default-display-
manager.

The boot sequence continues and xdm finally gets to run.  plymouth is
still running and is never stopped because plymouth-stop has already run
and is only allowed to run once.

In some cases this prevents the Xorg server from starting with
"setversion 1.4 failed" and " [drm] failed to set drm interface version,
Kernel modesetting setup failed', presumably because plymouth is
hogging the virtual console on which X is to be started.

Thus the problem is rectified by allowing plymouth-stop to be run
multiple times for each display manager installed by adding the line

instance    ${JOB}

to the plymouth-stop.conf file.

This may cure some bug reports that other users have reported of
plymouth not stopping when running other display managers eg slim

** Affects: plymouth (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1093313

Title:
  plymouth-stop.conf needs "instance" because it may need to be run
  multiple times

Status in “plymouth” package in Ubuntu:
  New

Bug description:
  PRETTY_NAME="Ubuntu quantal (12.10)"
  VERSION="12.10, Quantal Quetzal"

  Package: plymouth
  Origin: Ubuntu
  Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
  Architecture: i386
  Version: 0.8.4-0ubuntu3

  
  Currently, the init job plymouth-stop will only run once during the bootup sequence, but in cases where the user has installed more than one display manager, it will need to be run more than once.

  Consider this example.

  xdm is installed and made the default-display-manager.

  plymouth-stop is called on  stopped rc RUNLEVEL=[2345]  (JOB is rc),
  xdm runs and Xorg starts.

  lightdm is then installed but xdm is left as the default-display-
  manager.

  plymouth-stop is now called on starting lightdm (JOB is lightdm) but
  the case statement results in exit 0 with no action as lightdm is
  expected to take care of stopping plymouth.

  However in the lightdm init configuration file, the lightdm job stops
  without doing anything because lightdm is not the default-display-
  manager.

  The boot sequence continues and xdm finally gets to run.  plymouth is
  still running and is never stopped because plymouth-stop has already
  run and is only allowed to run once.

  In some cases this prevents the Xorg server from starting with
  "setversion 1.4 failed" and " [drm] failed to set drm interface
  version,  Kernel modesetting setup failed', presumably because
  plymouth is  hogging the virtual console on which X is to be started.

  Thus the problem is rectified by allowing plymouth-stop to be run
  multiple times for each display manager installed by adding the line

  instance    ${JOB}

  to the plymouth-stop.conf file.

  This may cure some bug reports that other users have reported of
  plymouth not stopping when running other display managers eg slim

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1093313/+subscriptions