[Bug 1309617] Re: plymouth-upstart-bridge main process (189) terminated with status 1 at boot
Dimitri John Ledkov
launchpad at surgut.co.uk
Mon Jul 28 09:42:36 UTC 2014
On 26 July 2014 02:33, Steve Langasek <steve.langasek at canonical.com> wrote:
>> In the case when plymouthd has been started from
>> the initramfs, we can be running the bridge straight
>> away, otherwise it needs to wait for plymouthd to start.
>
> I had assumed that the plymouth-upstart-bridge was designed to wait for
> plymouth to become available. Otherwise, it will lose events from
> anything that starts before plymouth does. Granted, that's very little,
> so *maybe* we don't care about this - in that case, the bridge should
> just be 'start on started plymouth'. However, otherwise the current
> start condition is correct and the daemon should simply be fixed to wait
> for plymouthd to start (probably using inotify).
>
plymouth-upstart-bridge returns exit code 1, if
ply_boot_client_connect or ply_upstart_monitor_new fail.
Plymouthd uses abstract socket, so we can't be doing inotify watch on
the socket file.
How about this instead, see patch. Add start on or started plymouth,
or started plymouth-shutdown, and add pre-start exec to ping plymouth
and stop job from running if there is no plymouthd to talk to.
--
Regards,
Dimitri.
** Patch added: "plymouth-upstart.patch"
https://bugs.launchpad.net/bugs/1309617/+attachment/4164213/+files/plymouth-upstart.patch
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189) terminated with status 1 at
boot
Status in “plymouth” package in Ubuntu:
Confirmed
Bug description:
I see this when I boot (I got it by running the dmesg command):
[ 7.631865] init: plymouth-upstart-bridge main process (173) terminated with status 1
[ 7.632154] init: plymouth-upstart-bridge main process ended, respawning
[ 7.670080] init: plymouth-upstart-bridge main process (183) terminated with status 1
[ 7.670443] init: plymouth-upstart-bridge main process ended, respawning
[ 7.706173] init: plymouth-upstart-bridge main process (186) terminated with status 1
[ 7.706534] init: plymouth-upstart-bridge main process ended, respawning
I don't know if plymouth-upstart-bridge is supposed to be running at all time but it doesn't on my machine:
bbigras at ubuntunew:~$ ps ax | grep plymouth-upstart-bridge
8784 pts/2 S+ 0:00 grep --color=auto plymouth-upstart-bridge
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: plymouth 0.8.8-0ubuntu17
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
Date: Fri Apr 18 12:04:00 2014
DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
InstallationDate: Installed on 2014-01-21 (86 days ago)
InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.2)
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/hostname--vg-root ro
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/hostname--vg-root ro
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago)
dmi.bios.date: 10/13/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd10/13/2009:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
mtime.conffile..etc.init.plymouth.stop.conf: 2014-04-18T09:37:28.562680
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1309617/+subscriptions
More information about the foundations-bugs
mailing list