plymouth-upstart-bridge termination messages post installation

Bug #1428068 reported by bugproxy
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

---Problem Description---
plymouth-upstart-bridge termination messages post installation

---uname output---
3.18.0-13-generic

Machine Type = POWER8

---Debugger---
A debugger is not configured

---Steps to Reproduce---
 1) Install 15.04 on a Power VM LPAR
2) Post installation following plymouth related messages are seen in dmesg

[ 0.726139] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[ 1.281220] init: plymouth-upstart-bridge main process (199) terminated with status 1
[ 1.281229] init: plymouth-upstart-bridge main process ended, respawning
[ 1.282956] init: plymouth-upstart-bridge main process (206) terminated with status 1
[ 1.282965] init: plymouth-upstart-bridge main process ended, respawning
[ 1.284571] init: plymouth-upstart-bridge main process (207) terminated with status 1
[ 1.284579] init: plymouth-upstart-bridge main process ended, respawning
[ 1.286175] init: plymouth-upstart-bridge main process (208) terminated with status 1
[ 1.286183] init: plymouth-upstart-bridge main process ended, respawning
[ 1.287816] init: plymouth-upstart-bridge main process (209) terminated with status 1
[ 1.287824] init: plymouth-upstart-bridge main process ended, respawning
[ 1.289402] init: plymouth-upstart-bridge main process (210) terminated with status 1
[ 1.289411] init: plymouth-upstart-bridge main process ended, respawning
[ 1.291097] init: plymouth-upstart-bridge main process (211) terminated with status 1
[ 1.291106] init: plymouth-upstart-bridge main process ended, respawning
[ 1.292660] init: plymouth-upstart-bridge main process (212) terminated with status 1
[ 1.292668] init: plymouth-upstart-bridge main process ended, respawning
[ 1.294637] init: plymouth-upstart-bridge main process (213) terminated with status 1
[ 1.294646] init: plymouth-upstart-bridge main process ended, respawning
[ 1.296200] init: plymouth-upstart-bridge main process (214) terminated with status 1
[ 1.296209] init: plymouth-upstart-bridge main process ended, respawning
[ 1.297621] init: plymouth-upstart-bridge main process (215) terminated with status 1
[ 1.297630] init: plymouth-upstart-bridge respawning too fast, stopped

bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-122176 severity-medium targetmilestone-inin---
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1428068/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → plymouth (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Will Bryant (willbryant) wrote :
bugproxy (bugproxy)
tags: added: targetmilestone-inin1610
removed: targetmilestone-inin---
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2017-01-26 11:00 EDT-------
Last comment in Sep 2016 stated this was no longer reproducible. Closing...

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.