This bug was fixed in the package lightdm - 1.5.1-0ubuntu1
---
lightdm (1.5.1-0ubuntu1) raring; urgency=low
* New upstream release:
[ 1.5.0 ]
- Add man page for lightdm-set-defaults (LP: #1044485)
- Use xzip for distribution, don't distribute old metadata
-
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
**
** Branch linked: lp:~robert-ancell/lightdm/ubuntu-1.5.1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1128474
Title:
LightDM fails to start/stop after adding script parameter
** Branch linked: lp:ubuntu/raring-proposed/lightdm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1128474
Title:
LightDM fails to start/stop after adding script parameter
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glib2.0 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
** Project changed: glib = glib2.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1128474
Title:
LightDM fails to start/stop after adding script parameter