init: plymouth-upstart-bridge respawning too fast, stopped
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Since a while i get that issue with each cold boot logged inside dmesg:
init: plymouth-
[ 5.566839] init: plymouth-
[ 5.569252] init: plymouth-
[ 5.569332] init: plymouth-
Seen on a forum a proposed workaround: adding 'sleep 5' at the end of the script, but this is not accepted as a valid entry.
/etc/init/
# plymouth-
#
# This helper process receives Upstart state changes over D-Bus and sends
# corresponding messages to Plymouth.
description "bridge from Upstart state changes to Plymouth"
respawn
start on (startup
or runlevel [06])
stop on (stopping plymouth
or stopping plymouth-shutdown)
console output
exec plymouth-
seems similar as that oldish lp:1309617
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: plymouth 0.9.0-0ubuntu4
ProcVersionSign
Uname: Linux 3.16.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 18 08:56:13 2014
DefaultPlymouth: /lib/plymouth/
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcCmdLine: BOOT_IMAGE=
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5W DH Deluxe
dmi.product.
dmi.sys.vendor: ASUSTEK COMPUTER INC
Status changed to 'Confirmed' because the bug affects multiple users.