*** This bug is a duplicate of bug 559761 ***
https://bugs.launchpad.net/bugs/559761
I can confirm that bug as well. System is running as virtual machine on
Virtual BOX 3.2.8r64453. Kernel image: 2.6.32-24-generic-pae.
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/5571
*** This bug is a duplicate of bug 559761 ***
https://bugs.launchpad.net/bugs/559761
I can confirm the same error on 64bit dual core AMD and a P4 intel Dell.
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a membe
*** This bug is a duplicate of bug 559761 ***
https://bugs.launchpad.net/bugs/559761
** Package changed: plymouth (Ubuntu) => mountall (Ubuntu)
** This bug has been marked a duplicate of bug 559761
mountall needs to flush plymouth message queue before emitting upstart events
--
mountall:
Same problem with Lucid server amd64 run as Xen virtual guest under
CentOS 5.4
[r...@thor ~]# uname -a
Linux thor 2.6.18-164.el5xen #1 SMP Thu Sep 3 04:03:03 EDT 2009 x86_64 x86_64
x86_64 GNU/Linux
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug
Same problem on a Dell Latitude X1 notebook.
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
Same problem on HP Compaq 6720s laptop.
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
** Description changed:
Binary package hint: plymouth
On bootup VT1 is spammed with following message: "mountall: Plymouth command
failed".
(Additionally: This message seems to have no ending linebreak, the messages
are not lined up below each other, but are wrapping at the screen borde
I can confirm that bug as well. System is running as virtual machine on
Virtual BOX 3.1.6. Kernel image: 2.6.32-21-generic-pae.
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I get the same error. I have a Gateway ec1440u notebook.
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
I got the same messages as this bug reported.
I am using fujitsu S6420 notebook
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Tags added: glucid
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
I'm getting a lot of these messages as well
I have Dell XPS 1210 - nvidia 7400, nvidia-current installed
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
I subscribed to bug #559761, it seems very similar after a first glance.
My last question is obviously moot now, bug #559761 is about fsck, too...
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a member of Ubuntu
Bugs
I cannot check anymore whether the mountall process was running back then, of
course. But I can assure you that the "plymouth command failed" console spam
had stopped when I switched from X to VT1.
Last time I booted I did not seem to get the "command failed" message anymore,
but something like
I have a potential duplicate report of this bug as # 559761. In my
case, the "mountall: Plymouth command failed" message still loops on the
console. However, the mountall process fails to terminate properly, and
continues to use 100% CPU time after I've logged on.
Dennis, is it possible for you
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
--
mountall: Plymouth command failed
https://bugs.launchpad.net/bugs/557161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/43335854/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/43335855/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43335856/Dependencies.txt
** A
17 matches
Mail list logo
