This bug was closed 5 years ago.
If you're experiencing any issues at all today then please open a new
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% C
Didn't help after all. Plymouth is still using 100% CPU on reboot.
Now trying all the suggestions in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1536771
Disabled plymouth in Grub and dpkg-reconfigured it.
--
You received this bug notification because you are a
I found the conflict with the eGalax Touch Daemon driver.
I moved the driver startup from /etc/init.d/eGtouch.sh
to userspace as I don't need the touchscreen at login.
The strange thing is I have 17 machines with this configuration and only
one is exhibiting this behaviour with plymouthd
--
Y
I've attached an apport report of the runaway process
** Attachment added: "apport.plymouth.b8ut5mm8.apport"
https://bugs.launchpad.net/lightdm/+bug/1192051/+attachment/5103196/+files/apport.plymouth.b8ut5mm8.apport
--
You received this bug notification because you are a member of Ubuntu
Bug
There is a regression of this bug in 16.04.4LTS
Linux computer 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
PID USER PR NIVIRTRES
** Changed in: lightdm
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notification
** Branch linked: lp:~robert-ancell/lightdm/ubuntu-1.7.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notifications about thi
This bug was fixed in the package lightdm - 1.7.6-0ubuntu1
---
lightdm (1.7.6-0ubuntu1) saucy; urgency=low
* New upstream release:
[ 1.7.6 ]
- Restore greeter hints that were regressed in 1.7.5.
- Don't run greeters through session wrapper - regression in 1.7.5
[ 1.7
** Branch linked: lp:ubuntu/saucy-proposed/lightdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notifications about this bug
** Changed in: lightdm (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notification
Fix committed into lp:lightdm at revision None, scheduled for release in
lightdm, milestone Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after
** No longer affects: plymouth (Ubuntu)
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning
Fix committed into lp:~mir-team/lightdm/unity at revision 1636,
scheduled for release in lightdm, milestone Unknown
** Changed in: lightdm
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Branch linked: lp:~robert-ancell/lightdm/unity-plymouth-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notifications abo
** Branch linked: lp:~townsend/lightdm/fix-plymouthd-spin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notifications about th
Ok, after a couple of false starts on root causing this, I believe I
found the issue causing the spin:)
- In the Xmir startup, nothing is calling "plymouth quit", so that is why
plymouthd keeps running. I know this because I enabled logging in both Xmir
and X only, and in X only, I can see a ca
Sigh...I made a lightdm package that reverted this hack to see the 100%
CPU state, but didn't realize that it got reverted from the latest Mir
updates today. Anyways, as Steve pointed out, plymouth is *not*
respawned in this case, so my last update is bogus for this particular
bug.
However, it's
> So I think when plymouthd crashes, a new plymouthd is spawned,
The upstart job never does this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I
Thanks Daniel.
I have also discovered that plymouthd is crashing sometime during
boot/log in (not sure exactly when). I built a version of plymouth with
symbols and have a stack trace that shows that it's falling over at
on_deactivate w/ a segfault. So I think when plymouthd crashes, a new
plymo
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: plymouth (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Oops, I forgot to post my original findings here. You might find them
helpful...
plymouthd is spinning on an fd of "/dev/tty7" with errno==EIO. Waiting
for the "plymouth deactivate" to properly complete (hence
drmDropMaster), avoids the bug.
So it looks like plymouth's DRM code is not very clever
After some more investigation, I'm not sure what I said is exactly true,
but there is something that is (obviously) not telling plymouth to quit
with this setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
On Thu, Jul 11, 2013 at 08:26:31PM -, Christopher Townsend wrote:
> I've been investigating the plymouth part of this and what I have
> discovered is that plymouth is waiting on an event from lightdm on VT
> 7(tty7) to tell it to stop. However, with Xmir, as far as I can tell,
> nothing is hap
I've been investigating the plymouth part of this and what I have
discovered is that plymouth is waiting on an event from lightdm on VT
7(tty7) to tell it to stop. However, with Xmir, as far as I can tell,
nothing is happening onVT 7, so the event never occurs causing plymouth
to spin out of contr
** Changed in: lightdm
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notifications about this
The fix in lightdm is enough right now. No need to fix plymouth,
especially if a Mir-native-plymouth would never have the bug anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
ply
Verified Fix Released in lightdm 1.7.2bzr1621saucy0.57
https://launchpad.net/~mir-team/+archive/system-compositor-testing
** Changed in: lightdm
Status: Fix Committed => Fix Released
** Changed in: plymouth (Ubuntu)
Importance: High => Medium
** Changed in: plymouth (Ubuntu)
Assig
Fix committed into lp:~mir-team/lightdm/unity at revision 1619,
scheduled for release in lightdm, milestone Unknown
** Changed in: lightdm
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Changed in: plymouth (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notific
** Branch linked: lp:~vanvugt/lightdm/fix-1192051
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notifications about this bug g
** Also affects: lightdm
Importance: Undecided
Status: New
** Changed in: lightdm
Status: New => In Progress
** Changed in: lightdm
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: plymouth (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
WORKAROUND:
sudo plymouth deactivate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU after I log in
To manage notifications about this bug go to:
https:/
** Summary changed:
- plymouthd spinning at 100% CPU
+ plymouthd spinning at 100% CPU after I log in
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192051
Title:
plymouthd spinning at 100% CPU afte
** Description changed:
- plymouthd spinning at 100% CPU
+ plymouthd spinning at 100% CPU. Probably triggered by use of this PPA:
+ https://launchpad.net/~mir-team/+archive/system-compositor-testing
+ although that does not change Plymouth.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Pac
Spinning where, you ask?
root@think:~# ./dstack plymouthd
Process ID: 186
Program name: plymouthd
Program path: /sbin/plymouthd
Thread count: 1
81 ../sysdeps/unix/syscall-template.S: No such file or directory.
Dstack of plymouthd pid 186 (/sbin/plymouthd)
[Switching to thread 1 (Thread 0x
36 matches
Mail list logo
