[Bug 1298938] Re: grep: /etc/init/plymouth-shutdown.override: No such file or directory

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.12.1-0ubuntu4

---------------
upstart (1.12.1-0ubuntu4) trusty; urgency=medium

  [ Adam Conrad ]
  * Disable chroot sessions by default, add an option to enable chroot
    sessions. (LP: #1277594)
 -- Dimitri John Ledkov <xnox at ubuntu.com>   Fri, 11 Apr 2014 22:31:21 +0100

** Changed in: upstart (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

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

Title:
  grep: /etc/init/plymouth-shutdown.override: No such file or directory

Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * Unnecessary bogus harmless messages printed to the user in the
  default configuration.

  [Test Case]

   * Execute wait-for-state against any job that does not have an override
   * Make sure no log / grep error messages from not finding .override file are printed for the wait-for-state job

  [Regression Potential]

   * minimal output from $ grep, was already suppressed with '-q', now
  the stderr is redirected as well, exit / result from grep is checked.

  [Other Info]
   
   * Original bug report:

  I'm using Ubuntu 14.04 dev with plymouth 0.8.8-0ubuntu15 and on every
  boot I'm seeing another line of the warning "grep: /etc/init/plymouth-
  shutdown.override: No such file or directory" in the file
  /var/log/upstart/wait-for-state-rcplymouth-shutdown.log

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