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 strange that plymouth segfaults in the hacked lightdm case. Also, if I send a "plymouth deactivate", the spinning plymouth segfaults the same way, but that is a different 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% CPU after I log in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
