This bug was fixed in the package lightdm - 1.2.3-0ubuntu2.7
---------------
lightdm (1.2.3-0ubuntu2.7) precise; urgency=medium
* debian/patches/15_gsources.patch:
- Correctly remove GSources on finalize (LP: #1431654)
lightdm (1.2.3-0ubuntu2.6) precise; urgency=medium
* debian/patches/09_close_pipes.patch:
- Close pipes correctly (LP: #1190344)
* debian/patches/10_conf_section_name.patch:
- Correct section name in default users.conf (LP: #1069218)
* debian/patches/11_quit_timeout.patch:
- Destroy quit timeout when a process object is destroyed - fixes a crash
where a deleted Process object might be accessed after a timeout
(LP: #1207935)
* debian/patches/12_layout_no_x11.patch:
- Handle not getting an X connection when attempting to get X layouts
(LP: #1235915)
* debian/patches/13_introspection_makefile.patch:
- Fix introspection build with newer versions of g-ir-scanner
* debian/patches/14_compile_warnings.patch:
- Fix compile warnings
-- Robert Ancell <robert.anc...@canonical.com> Tue, 17 Mar 2015 14:21:43
+1300
** Changed in: lightdm (Ubuntu)
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/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
