** Tags removed: utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189) terminated with status 1 at
boot
To manage notifications about
to #37
Insert instead 'sleep 2' this line: 'post-stop exec sleep 2'
Message about plymouth disappeared.
Ubuntu 14.04.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
I never experienced any significant problems because of this bug. It
only results in those error messages. If your system fails to boot or
other things crash, that is probably due to a different unrelated issue.
The "sleep" in /etc/init/plymouth-upstart-bridge.conf does make these
error messages
this is also an issue for me. im not sure if the general instability of
the system has anything to do with this. this is the only logged error
i have found so far. it seemed like a good place to start to get the
system running healthily..
ubuntu 14.0.4.3 with the full Ubuntu-Mate added
--
Here is how to fix it.
http://www.unrelatedshit.com/2014/07/30/kvm-too-fast-for-plymouth-
upstart-bridge/
But I used sleep 1 and it works just fine. But I think this needs to be
fixed in ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug affects me as well, but only one of my several servers, and
about 20% of the time when I reboot, it crashes trying to mount the root
fs on startup. I tried booting to the 3.13.0-24 kernel, fully
uninstalling the 3.13.0-68 kernel, then reinstalling it, but the
Plymouth issue still
Has this been fixed? New install of Ubuntu server 64 14.04, and I cannot
boot the machine at all due to this. I get messages about plymouth-
upstart-bridge trying to spawn repeatedly and terminating with status 1,
and then the entire machine stops responding. Cannot boot at all, the
machine is
Adding sleep 2 results in a different error: init: /etc/init
/plymouth-upstart-bridge.conf:18: Unknown stanza. I wonder if this
causes plymouth-upstart-bridge to not run at all? I have not encountered
any problems running like that for many months, but I wonder if some
situations could lead to
I was having this problem with plymouth-upstart-bridge respawning repeatedly
during boot. Machine still came up, but boot seemed to be delayed.
Here's a very simple solution I found here:
http://www.unrelatedshit.com/2014/07/30/kvm-too-fast-for-plymouth-upstart-bridge/
To fix it, simply add a
Same here, don't know if this the problem, but the laptop doesn't get to
the graphical session. Stays stuck on the 4 dots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
Upgraded to Ubuntu version 14.10 and now it wouldnt even boot with
kernel 3.11.0-20-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189)
After 3 days of trying to install Ubuntu Server on an older computer I
finally did it. So, the problem was that after the installing process
was finished, the system required a reboot. On reboot, the system kept
freezing on a line with adding XX to swap or during the plymouth
stuff.
So the key
** Tags added: amd64 utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189) terminated with status 1 at
boot
To manage notifications about
Now its a show stopper on Utopic (fresh installation from mini.iso)
The boot process goes well until that plymouth-bridge respawning madness, and
then the swap partition is mounted. That's all, nothing more.
Trying to tweak /etc/init/plymouth-upstart-bridge ( recovery boot, root
console: to add
#26 follow up
be able to add sleep 3 from the user session that time. The respawning
seems to be gone, but the system still fails to boot.
So i've added init=/lib/systemd/systemd to /etc/default/grub, then
update-grub; and also take care of mtab: ln -fs /proc/self/mounts /etc/mtab
(cf:
Hello,
the same problem here:
Ubuntu 14.04 LTS 64b - Linux kernel 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13
15:45:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
GRUB_CMDLINE_LINUX_DEFAULT=noplymounth and update-grub did not work.
BTW, is there typo in post #11 ? I used noplymouth in my
Hello,
I am having the same issue here with Plymouth..
There is no practical sense for me to post the same information that is in post
#8 and others.
I am running a fresh install of Ubuntu 14.04 Trusty 64Bit and the usual
updates.
What is totally annoying is not only is there an issue with
The same problem at boot time, but eventually the system boots normally
Fresh install Ubuntu 14.04.1 64 bit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main
added the patch and found a lot of time is waiting after 3.760234
second to start another process
** Attachment added: dmsg
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1309617/+attachment/4172955/+files/dmsg
--
You received this bug notification because you are a member of
On 26 July 2014 02:33, Steve Langasek steve.langa...@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
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189) terminated with status 1 at
boot
To manage notifications about this
Have the same issue. Tried to specify to the kernel
ro console=tty0 console=ttyS2,115200n8
and see attachment. The boot process hangs.
** Attachment added: Selection_114.png
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1309617/+attachment/4163953/+files/Selection_114.png
--
You
the bridge is suppose to run during startup (boot) and shutdown, when there is
also plymouthd running.
However plymouthd can be started from initramfs or via upstart job.
In the case when plymouthd has been started from the initramfs, we can be
running the bridge straight away, otherwise it
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
After 3.753881 the system waiting long time to start another process
30.974493
** Attachment added: report
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1309617/+attachment/4159790/+files/report
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After 3.753881 the system waiting long time to start another process
30.974493
** Attachment added: report
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1309617/+attachment/4159789/+files/report
--
You received this bug notification because you are a member of Ubuntu
Bugs,
certainly this is needed in the server installs, so why not disable?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189) terminated with status 1
Edit /etc/init/plymouth-upstart-bridge.conf
# plymouth-upstart-bridge - Bridge Upstart state changes into 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
#13, how is it different from the default and why would it fix the
problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189) terminated with
The real problem is that the boot splash screen is not working. Where is
the logfile for plymouth-upstart-bridge to see what's the problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
I don't know if it fix the problem or just hide it out, but I manage to
stop the plymouth messages in boot by editing /etc/default/grub and
setting the GRUB_CMDLINE_LINUX_DEFAULT=noplymounth. (and updating grub
after that)
--
You received this bug notification because you are a member of Ubuntu
same probleme in lenovo Z510
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189) terminated with status 1 at
boot
To manage notifications
I have same problem on my Lenovo u310
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189) terminated with status 1 at
boot
To manage
Same problem here after an upgrade from precise to trusty.
Jun 5 10:48:20 li148-39 kernel: init: plymouth-upstart-bridge main process
(6985) terminated with status 1
Jun 5 10:48:20 li148-39 kernel: init: plymouth-upstart-bridge main process
ended, respawning
Jun 5 10:48:20 li148-39 kernel:
I see those lines in the console during boot on Ubuntu Server 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189) terminated with status 1
I experience this too on Ubuntu Desktop 14.04 when using the kernel
3.13.0-24-generic. However if I go into Advanced options and select
kernel 3.11.0-20-generic it boots fine. I had upgraded from 13.10 64
bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I am experiencing this on Ubuntu Server 14.04. I see this in the
console during boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
plymouth-upstart-bridge main process (189)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plymouth (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309617
Title:
Dimitri, since you touched this code last I guess you might have some
idea what's causing plymouth-upstart-bridge to die/respawn. Could you
have a look?
Bruno, to be clear: are you seeing these messages on the console during
boot, or are you only seeing them in the dmesg output?
** Changed in:
During boot.
Here's a screen capture from the vmware ESXi console thing.
I'm not sure if there's could be a link but just in case. After I
upgraded to 14.04 some of my own upstart jobs where starting, stopping
and starting again in a loop (I guess upstart gave up after a number of
iterations).
40 matches
Mail list logo
