Plymouthd constantly using 5% of CPU time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubuntu PPA |
Expired
|
Undecided
|
Unassigned | ||
kde-workspace (Ubuntu) |
Incomplete
|
Low
|
Harald Sitter |
Bug Description
On fresh install of Kubuntu 12.04.3, a process named "plymouthd" always using 5% of CPU on working system, even after login. I asked this question on AskUbuntu, they recommends me to report a bug.
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
2) The version of the package you are using, via 'apt-cache policy pkgname'
plymouth package version: 0.8.2-2ubuntu31.1
3) What you expected to happen
plymouthd should'nt use any resources after i logged in to my desktop.
4) What happened instead
plymouthd always using 5% of CPU
Link to AskUbuntu question with screenshot of "top": http://
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu31.1
ProcVersionSign
Uname: Linux 3.8.0-31-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu17.5
Architecture: amd64
Date: Wed Oct 16 09:52:40 2013
DefaultPlymouth: /lib/plymouth/
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1604
dmi.board.
dmi.board.name: M5A99X EVO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To be filled by O.E.M.
dmi.product.
dmi.sys.vendor: To be filled by O.E.M.
Kubuntu 12.04 uses kdm as its login manager; kdm is responsible for stopping plymouthd before it launches X. Reassigning to kdm, since this problem has not been reported when using lightdm.
This may be related to bug #982889; it appears kdm has not implemented the corresponding changes to improve reliability of plymouth handling at boot.
You can check whether the fix for bug #982889 solves this for you by editing /etc/init/kdm.conf on your system and changing the 'start' rule to read:
start on ((filesystem
and runlevel [!06]
and started dbus
and plymouth-ready)
or runlevel PREVLEVEL=S)