7 May
2018
7 May
'18
10:27 a.m.
From the OpenSuSE KDE3 folks.
Leslie
---------- Forwarded Message ----------
Subject: [opensuse-kde3] plymouthd - takes continual 6% CPU with kdm
Date: 2018-05-07, 03:32:08
From: "David C. Rankin" <drankinatty(a)suddenlinkmail.com>
To: "suse-kde3" <opensuse-kde3(a)opensuse.org>
All,
There is an issue, that this is more to document than anything else. I've
done 2 Leap 42.3 installs. On this last one, after a minimal X install via the
Net-Install CD, I kept an eye on plymouth. In my 1st install, I checked with
top in konsole, more-or-less on a whim, and found plymouthd churning away at
6%.
On this second Leap 42.3 install (again 1st to minimum X via yast
net-install, because you cannot configure outside repos during install, only
community OSS, OSS-Debug, etc...) -- anyway, I decided to keep a closer watch
on plymouth and find out when it started behaving badly.
On the initial setup and with the xdm "Default" display manager (that clunky
old thing with the system console window running in bottom-left corner),
plymouthd behaved, no problems. I spent the better part of a day, moving
documents over, .kde, etc.. and installing kde3 and the rest of the normal
things I install. All the while, plymouthd was fine.
However, after setting kdm3 in /etc/sysconfig/displaymanager and kde as the
default WM, after rebooting and launching kde via kdm, plymouthd was again
churning away at 6% continually.
So there is a definite issue with plymouth and kdm. I don't know exactly
why. This 2nd install was to an older laptop, so I didn't have 6% to spare and
just rpm -e all plymouth.... Problem gone.
If anyone else still has plymouth installed and can check with top to
confirm plymouth is hogging CPU, that would be worth investigating. I can
confirm this on 2 boxes.
--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org
-------------------------------------------------------
7 May
7 May
11:09 a.m.
New subject: [trinity-users] Anyone noticed this with Trinity and plymouthd?
Hi,
On PCLinuxOS this is not the case, but it might uses a much older version of Plymouth.
Thanks!
-Alexandre
________________________________
De : Leslie Turriff <jlturriff(a)mail.com>
Envoyé : 7 mai 2018 06:27:29
À : trinity-users(a)lists.pearsoncomputing.net
Objet : [trinity-users] Anyone noticed this with Trinity and plymouthd?
From the OpenSuSE KDE3 folks.
Leslie
---------- Forwarded Message ----------
Subject: [opensuse-kde3] plymouthd - takes continual 6% CPU with kdm
Date: 2018-05-07, 03:32:08
From: "David C. Rankin" <drankinatty(a)suddenlinkmail.com>
To: "suse-kde3" <opensuse-kde3(a)opensuse.org>
All,
There is an issue, that this is more to document than anything else. I've
done 2 Leap 42.3 installs. On this last one, after a minimal X install via the
Net-Install CD, I kept an eye on plymouth. In my 1st install, I checked with
top in konsole, more-or-less on a whim, and found plymouthd churning away at
6%.
On this second Leap 42.3 install (again 1st to minimum X via yast
net-install, because you cannot configure outside repos during install, only
community OSS, OSS-Debug, etc...) -- anyway, I decided to keep a closer watch
on plymouth and find out when it started behaving badly.
On the initial setup and with the xdm "Default" display manager (that clunky
old thing with the system console window running in bottom-left corner),
plymouthd behaved, no problems. I spent the better part of a day, moving
documents over, .kde, etc.. and installing kde3 and the rest of the normal
things I install. All the while, plymouthd was fine.
However, after setting kdm3 in /etc/sysconfig/displaymanager and kde as the
default WM, after rebooting and launching kde via kdm, plymouthd was again
churning away at 6% continually.
So there is a definite issue with plymouth and kdm. I don't know exactly
why. This 2nd install was to an older laptop, so I didn't have 6% to spare and
just rpm -e all plymouth.... Problem gone.
If anyone else still has plymouth installed and can check with top to
confirm plymouth is hogging CPU, that would be worth investigating. I can
confirm this on 2 boxes.
--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org
-------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
2:19 p.m.
New subject: [trinity-users] Anyone noticed this with Trinity and plymouthd?
Leslie Turriff composed on 2018-05-07 05:27 (UTC-0500):
If anyone else still has plymouth installed and can
check with top to
confirm plymouth is hogging CPU, that would be worth investigating. I can
confirm this on 2 boxes.
I don't get why anyone thinks Plymouth's basic purpose is more desirable than
the bloat it represents, or useful at all. I've never had it installed on an
openSUSE installation unless maybe when it first appeared I didn't notice to
taboo it. If I did, it was too long ago to remember. Anywhere else, e.g. Mageia,
where Plymouth was not optional, plymouth.enable=0 went on those kernel
cmdlines. At boot time, I don't need rainbow fluff and spindly or no text
instead of nice bold, legible white on black racing so fast it can't all be read.
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
3:14 p.m.
New subject: [trinity-users] Anyone noticed this with Trinity and plymouthd?
On May 7, 2018 10:19 AM, Felix Miata <mrmazda(a)earthlink.net> wrote:
I don't get why anyone thinks Plymouth's basic
purpose is more desirable than
the bloat it represents, or useful at all. I've never had it installed on an
openSUSE installation unless maybe when it first appeared I didn't notice to
taboo it. If I did, it was too long ago to remember. Anywhere else, e.g. Mageia,
where Plymouth was not optional, plymouth.enable=0 went on those kernel
cmdlines. At boot time, I don't need rainbow fluff and spindly or no text
instead of nice bold, legible white on black racing so fast it can't all be read.
It is exactly this -- the pursuit of fluff over function -- that drove me and I suspect
others away from KDE and to TDE. Somewhere it got into people's minds that we'll
all scream in horror and run away if we ever see anything in text mode. Sad.
dep
Sent withProtonMailSecure Email. Because privacy matters.
6:41 p.m.
New subject: [trinity-users] Anyone noticed this with Trinity and plymouthd?
On Monday 07 May 2018 11:14:12 dep wrote:
On May 7, 2018 10:19 AM, Felix Miata
<mrmazda(a)earthlink.net> wrote:
And I'll nominate that "sad" statement as statement of the month.
I don't get why anyone thinks Plymouth's
basic purpose is more
desirable than
the bloat it represents, or useful at all. I've never had it
installed on an
openSUSE installation unless maybe when it first appeared I didn't
notice to
taboo it. If I did, it was too long ago to remember. Anywhere else,
e.g. Mageia,
where Plymouth was not optional, plymouth.enable=0 went on those
kernel
cmdlines. At boot time, I don't need rainbow fluff and spindly or no
text
instead of nice bold, legible white on black racing so fast it can't
all be read.
It is exactly this -- the pursuit of fluff over function -- that drove
me and I suspect others away from KDE and to TDE. Somewhere it got
into people's minds that we'll all scream in horror and run away if we
ever see anything in text mode. Sad.
dep
Sent withProtonMailSecure Email. Because privacy matters.
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
9:19 p.m.
New subject: [trinity-users] Anyone noticed this with Trinity and plymouthd?
On Monday 07 May 2018 11:41:42 Gene Heskett wrote:
On Monday 07 May 2018 11:14:12 dep wrote:
Is there a Trump threshold in an online thread? Just wondering ...
Bill
On May 7, 2018 10:19 AM, Felix Miata
<mrmazda(a)earthlink.net> wrote:
And I'll nominate that "sad" statement as statement of the month.
> dep
> I don't get why anyone thinks Plymouth's
basic purpose is more
desirable than
the bloat it represents, or useful at all. I've never had it
installed on an
openSUSE installation unless maybe when it first appeared I didn't
notice to
taboo it. If I did, it was too long ago to remember. Anywhere else,
e.g. Mageia,
where Plymouth was not optional, plymouth.enable=0 went on those
kernel
cmdlines. At boot time, I don't need rainbow fluff and spindly or no
text
instead of nice bold, legible white on black racing so fast it can't
all be read.
It is exactly this -- the pursuit of fluff over function -- that drove
me and I suspect others away from KDE and to TDE. Somewhere it got
into people's minds that we'll all scream in horror and run away if we
ever see anything in text mode. Sad.
8 May
8 May
7:01 a.m.
New subject: [Users] Anyone noticed this with Trinity and plymouthd?
On 2018-05-07 09:19:59 Felix Miata wrote:
Leslie Turriff composed on 2018-05-07 05:27
(UTC-0500):
I agree. I wouldn't mind these folks adding
such new stuff to the distros,
except that (as KDE did) they tend to make them at best default, and at worse
mandatory, removing the features we're used to and (sometimes) replacing them
with "improved" ones. :-(
Leslie
If anyone else still has plymouth installed and
can check with top to
confirm plymouth is hogging CPU, that would be worth investigating. I can
confirm this on 2 boxes.
I don't get why anyone thinks Plymouth's basic purpose is more desirable
than the bloat it represents, or useful at all. I've never had it installed
on an openSUSE installation unless maybe when it first appeared I didn't
notice to taboo it. If I did, it was too long ago to remember. Anywhere
else, e.g. Mageia, where Plymouth was not optional, plymouth.enable=0 went
on those kernel cmdlines. At boot time, I don't need rainbow fluff and
spindly or no text instead of nice bold, legible white on black racing so
fast it can't all be read. 
7:21 a.m.
New subject: [trinity-users] Re: [Users] Anyone noticed this with Trinity and plymouthd?
Am Dienstag, 8. Mai 2018 schrieb Leslie Turriff:
On 2018-05-07 09:19:59 Felix Miata wrote:
The funny part with plymouth begins, when X11 fails to start.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
Leslie Turriff composed on 2018-05-07 05:27
(UTC-0500):
I agree. I wouldn't mind these folks adding
such new stuff to the distros,
except that (as KDE did) they tend to make them at best default, and at worse
mandatory, removing the features we're used to and (sometimes) replacing them
with "improved" ones. :-(
Leslie If anyone else still has plymouth installed and
can check with top to
confirm plymouth is hogging CPU, that would be worth investigating. I can
confirm this on 2 boxes.
I don't get why anyone thinks Plymouth's basic purpose is more desirable
than the bloat it represents, or useful at all. I've never had it installed
on an openSUSE installation unless maybe when it first appeared I didn't
notice to taboo it. If I did, it was too long ago to remember. Anywhere
else, e.g. Mageia, where Plymouth was not optional, plymouth.enable=0 went
on those kernel cmdlines. At boot time, I don't need rainbow fluff and
spindly or no text instead of nice bold, legible white on black racing so
fast it can't all be read. 
6:32 p.m.
New subject: [Users] Anyone noticed this with Trinity and plymouthd?
Leslie Turriff wrote:
$ dpkg -l | grep plymou
ii libplymouth4:amd64 0.9.2-4
amd64 graphical boot animation and logger - shared libraries
ii plymouth 0.9.2-4
amd64 boot animation, logger and I/O multiplexer
ii plymouth-themes 0.9.2-4
amd64 boot animation, logger and I/O multiplexer - themes
ii plymouth-x11 0.9.2-4
amd64 boot animation, logger and I/O multiplexer - X11 renderer
works great - no issues
AFAIR there was a problem when systemd does not complete/close the target.
I use
ii sysv-rc 2.88dsf-59.9
all System-V-like runlevel change mechanism
ii sysvinit-core 2.88dsf-59.9
amd64 System-V-like init utilities
ii sysvinit-utils 2.88dsf-59.9
amd64 System-V-like utilities
hope this helps
regards
Leslie Turriff
composed on 2018-05-07 05:27 (UTC-0500):
I agree. I wouldn't
mind these folks adding such new stuff to the
distros, except that (as KDE did) they tend to make them at best default,
and at worse mandatory, removing the features we're used to and
(sometimes) replacing them with "improved" ones. :-( If anyone else still has plymouth installed and
can check with top to
confirm plymouth is hogging CPU, that would be worth investigating. I
can confirm this on 2 boxes.
I don't get why anyone thinks Plymouth's basic purpose is more desirable
than the bloat it represents, or useful at all. I've never had it
installed on an openSUSE installation unless maybe when it first appeared
I didn't notice to taboo it. If I did, it was too long ago to remember.
Anywhere else, e.g. Mageia, where Plymouth was not optional,
plymouth.enable=0 went on those kernel cmdlines. At boot time, I don't
need rainbow fluff and spindly or no text instead of nice bold, legible
white on black racing so fast it can't all be read. 
7 May
7 May
2:36 p.m.
New subject: [trinity-users] Anyone noticed this with Trinity and plymouthd?
On Monday 07 May 2018 12:27:29 Leslie Turriff wrote:
From the OpenSuSE KDE3 folks.
Leslie
---------- Forwarded Message ----------
Subject: [opensuse-kde3] plymouthd - takes continual 6% CPU with kdm
Date: 2018-05-07, 03:32:08
From: "David C. Rankin" <drankinatty(a)suddenlinkmail.com>
To: "suse-kde3" <opensuse-kde3(a)opensuse.org>
All,
There is an issue, that this is more to document than anything else. I've
done 2 Leap 42.3 installs. On this last one, after a minimal X install via
the Net-Install CD, I kept an eye on plymouth. In my 1st install, I checked
with top in konsole, more-or-less on a whim, and found plymouthd churning
away at 6%.
On this second Leap 42.3 install (again 1st to minimum X via yast
net-install, because you cannot configure outside repos during install,
only community OSS, OSS-Debug, etc...) -- anyway, I decided to keep a
closer watch on plymouth and find out when it started behaving badly.
On the initial setup and with the xdm "Default" display manager (that
clunky old thing with the system console window running in bottom-left
corner), plymouthd behaved, no problems. I spent the better part of a day,
moving documents over, .kde, etc.. and installing kde3 and the rest of the
normal things I install. All the while, plymouthd was fine.
However, after setting kdm3 in /etc/sysconfig/displaymanager and kde as
the default WM, after rebooting and launching kde via kdm, plymouthd was
again churning away at 6% continually.
So there is a definite issue with plymouth and kdm. I don't know exactly
why. This 2nd install was to an older laptop, so I didn't have 6% to spare
and just rpm -e all plymouth.... Problem gone.
If anyone else still has plymouth installed and can check with top to
confirm plymouth is hogging CPU, that would be worth investigating. I can
confirm this on 2 boxes.
--
David C. Rankin, J.D.,P.E.
i think it's supposed to shutdown when tdm starts.
that's the actual bug.
https://bugs.trinitydesktop.org/show_bug.cgi?id=2806
i think the CPU usage is an after effect
If you notice, you can't access the tty's either....
you can stop it in a normal session with this command
sudo plymouth --quit
you can also, deactivate the splash option in grub
edit /etc/default/grub
change this line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT=""
save
and run
sudo update-grub
7:37 p.m.
wofgdkncxojef(a)gmail.com wrote:
i think it's supposed to shutdown when tdm
starts.
that's the actual bug.
https://bugs.trinitydesktop.org/show_bug.cgi?id=2806
i think the CPU usage is an after effect
If you notice, you can't access the tty's either....
you can stop it in a normal session with this command
sudo plymouth --quit
you can also, deactivate the splash option in grub
edit /etc/default/grub
change this line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT=""
save
and run
sudo update-grub
this is the best answer IMO, although I wonder if it has to do something
with systemd. Are you using systemd and can you try without.
2190
days inactive
2191
days old
10 comments
9 participants
participants (9)
-
Alexandre Couture -
deloptes -
dep -
Dr. Nikolaus Klepp -
Felix Miata -
Gene Heskett -
Leslie Turriff -
William Morder -
wofgdkncxojef＠gmail.com