Console <-> Upstart bridge shows very confusing and unhelpful "Starting" and "Stopping" with no descriptions

Bug #1185560 reported by Clint Byrum
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
Dimitri John Ledkov

Bug Description

I will attach a screen shot as well. It seems that jobs which have no description field are not displaying the name of the job in the upstart<->plymouth bridge.

This was seen on an Ubuntu 12.10 server with a text console forced by passing nomodeset vga=normal in GRUB_CMDLINE_LINUX

ii plymouth 0.8.4-0ubuntu3 i386 graphical boot animation and logger - main package
ii upstart 1.5-0ubuntu9 i386 event-based init daemon

Related branches

Revision history for this message
Clint Byrum (clint-fewbar) wrote :
Revision history for this message
James Hunt (jamesodhunt) wrote :

Hi Clint - thanks for reporting. This is an issue with the plymouth-upstart-bridge which is part of the plymouth package.

affects: upstart (Ubuntu) → plymouth (Ubuntu)
Changed in plymouth (Ubuntu):
status: New → Fix Committed
assignee: nobody → Dimitri John Ledkov (xnox)
importance: Undecided → Medium
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Clint, or anyone else affected,

Accepted plymouth into trusty-proposed. The package will build now and be available at in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at . Thank you in advance!

tags: added: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 0.8.8-0ubuntu16

plymouth (0.8.8-0ubuntu16) trusty; urgency=medium

  [ Steve Langasek ]
  * Fix debian/patches/tty1-after-boot.patch: when we have multiple
    non-default console options on the kernel commandline,
    local_console_terminal will not be set, so we should avoid the resulting
    assert. LP: #1160079, LP: #1235231.

  [ Dimitri John Ledkov ] LP: #1292458
  * debian/patches/use-upstart-private-socket.patch: instead of using
    system dbus, use private upstart socket in the plymouth-upstart-bridge.
  * debian/plymouth.plymouth-upstart-bridge.upstart: start
    plymouth-upstart-bridge on startup, and thus gather a more complete
  * debian/patches/dont-bail-on-dummy-terms.patch: don't bail
    plymouth-upstart-bridge if TERM is not set and/or running on a dummy
    terminal, as we can run on those. This makes console-log useful in
    lxc-containers and actually contain messages from upstart jobs
    starting and stopping.
  * debian/patches/no-print-empty-description.patch: do not store
    description when dbus returns empty string, and thus stop printing
    empty "Starting... done" messages. LP: #1185560.
  * debian/plymouth.plymouth-upstart-bridge.upstart: update stop on
    conditions to stop when plymouth-shutdown finishes.
  * Make ubuntu-logo theme support scale factor, provide one plymouth
    theme with scale 1 and another with scale 2, until scale factor can be
    dynamically detected.
  * Mark plymouth-upstart-bridge to respawn.
 -- Dimitri John Ledkov <email address hidden> Thu, 03 Apr 2014 16:37:29 +0100

Changed in plymouth (Ubuntu):
status: Fix Committed → Fix Released
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.