mountall: Plymouth command failed

Bug #557161 reported by Dennis Schridde
106
This bug affects 21 people
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

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 border.)
The spam stops at about the time when KDE has finished loading. Before it appeared (just observed it once until now), Kubuntu was checking my disks.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Wed Apr 7 11:42:03 2010
DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
InstallationMedia: Kubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N140
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=3ac375c4-4f3c-4d79-8f40-623392173493 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
dmi.bios.date: 09/30/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04CU.M010.20090930.CYH
dmi.board.name: N140
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04CU.M010.20090930.CYH:bd09/30/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnN140:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN140:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N140
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Dennis Schridde (devurandom) wrote :
Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathew Cairns (mat-cairns) wrote :

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 to confirm whether mountall was/is still running after KDE has loaded?

Revision history for this message
Dennis Schridde (devurandom) wrote :

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 "... broken pipe". Might be that the "command failed message had something to do with the disk-check. Mathew: Do you see any relation to that on your side?

Revision history for this message
Dennis Schridde (devurandom) wrote :

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...

Revision history for this message
Sandeep (sandys-gmail) wrote :

I'm getting a lot of these messages as well

I have Dell XPS 1210 - nvidia 7400, nvidia-current installed

Joel Ebel (jbebel)
tags: added: glucid
Revision history for this message
abgalphabet (abgalphabet) wrote :

I got the same messages as this bug reported.
I am using fujitsu S6420 notebook

Revision history for this message
Melvin Garcia (virtualspectre8) wrote :

I get the same error. I have a Gateway ec1440u notebook.

Revision history for this message
Łukasz Dudziński (lukasz-dudzinscy) wrote :

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.

description: updated
Revision history for this message
Lobel (lobel-strmecki) wrote :

Same problem on HP Compaq 6720s laptop.

Revision history for this message
Erik de Castro Lopo (erikd) wrote :

Same problem on a Dell Latitude X1 notebook.

Revision history for this message
Sergei Vorobyov (svorobyov) wrote :

Same problem with Lucid server amd64 run as Xen virtual guest under CentOS 5.4

[root@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

Steve Langasek (vorlon)
affects: plymouth (Ubuntu) → mountall (Ubuntu)
Revision history for this message
hippocanjump (hippocanjump) wrote :

I can confirm the same error on 64bit dual core AMD and a P4 intel Dell.

Revision history for this message
Òscar Mateo Martínez (informatica-roycan) wrote :

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.

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.