I'm still not able to reproduce this problem locally. There are two patches that may be causing this problem: 09_close_pipes.patch and 11_quit_timeout.patch (the others seem unlikely to have caused a problem like this).
What would be very useful is if someone who is reproducing the problem can: - Try building a package without either of the above patches and see which one is causing the problem. The packaging is in lp:~robert-ancell/lightdm/1.2.3-0ubuntu2.6 and can be built with bzr-buildpackage. - Try building from lp:lightdm/1.2 with bzr-buildpackage. This contains more patches not SRU'd - perhaps one of these fixes this loop? - Use gdb to find where in lightdm it is looping More detailed instructions for building locally: $ bzr branch lp:~robert-ancell/lightdm/1.2.3-0ubuntu2.6 lightdm-lp1431654 $ sudo apt-get build-dep lightdm $ cd lightdm-lp1431654 (disable patches in debian/patches) $ bzr-buildpackage $ sudo dpkg -i ../build-area/lightdm_1.2.3-0ubuntu2.6_amd64.deb ../build-area/liblightdm-gobject-1-0_1.2.3-0ubuntu2.6_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431654 Title: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
