Comment 13 for bug 1192051
Revision history for this message
| Christopher Townsend (townsend) wrote | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
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...