I think this was caused by a change in glib that picked up us using the API
wrongly. Regression tests picked this up and should be fixed in this commit:
http://bazaar.launchpad.net/~lightdm-team/lightdm/trunk/revision/1601
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Triaged
** Changed in: lightdm (Ubuntu)
Importance: Undecided => High
** Changed in: lightdm (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: glib2.0 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1128474
Title:
LightDM fails to start/stop after adding script parameter
(lightdm.conf)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1128474/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
