syntax error in /etc/init/kdm.conf upstart file

Bug #1331426 reported by J G Miller
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kde-workspace (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

PRETTY_NAME="Ubuntu 14.04 LTS"
VERSION="14.04, Trusty Tahr"

Package: kdm
Origin: Ubuntu
Maintainer: Kubuntu Developers <email address hidden>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Architecture: i386
Source: kde-workspace
Version: 4:4.11.9-0ubuntu0.2

file /etc/init/kdm.conf contains the line

        $(plymouth quit && plymouth wait && sleep 1) || :

The syntax of this command for plymouth Version: 0.8.8-0ubuntu17 is invalid

 plymouth wait
Splash control client
USAGE: plymouth [OPTION...] [COMMAND [OPTION...]...]

It should be plymouth --wait

Thus the sleep 1 is never executed because the invalid plymouth wait returns 1( false) and never 0 (true).

So to keep the style consistent with both instances of calling plymouth, the line should read

        $(plymouth --quit && plymouth --wait && sleep 1) || :

-----------------------------------------------------------------------------------------------------------------------------------------
However, if plymouth has already been told to quit, how can the command to tell plymouth to wait do anything if plymouth is no longer running?
-----------------------------------------------------------------------------------------------------------------------------------------

Revision history for this message
J G Miller (jgmiller) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "Patch for /etc/init.d/kdm.conf for invocation of plymouth" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kde-workspace (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.