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
    - Correctly check if display is active when session quits
    - Relicense liblightdm to LGPL-2/LGPL-3 so GPL-2 code can link against it
    - Selectively lock memory rather than calling mlockall for main daemon
    [ 1.5.1 ]
    - QLightDM: Add Qt5 version of the library: liblightdm-qt5-2 (LP: #1117355)
    - QLightDM: Add some missing role names in UsersModel
    - QLightDM: Add a backgroundPath role to UsersModel
    - QLightDM: Fix potential crash in QLightDM::UsersModel closedown.
    - Improve guest session apparmor
    - Run each test in its own /tmp dir so they can't interfere with eachother
    - Fix script hooks no longer working with latest glib (LP: #1128474)
    - Fix display clean up code
  * debian/control:
    - Use standards version 3.9.4
    - Drop bzr branch
    - Build-depend on qtbase5-dev
    - Add new Qt 5 packages
  * debian/patches/08_lp1059510.patch:
  * debian/patches/09_lp577919-fix-chromium-launch.patch:
  * debian/patches/10_selective_mlock.patch:
  * debian/patches/11_runtime_dir_access.patch:
     - Applied upstream
  * debian/source/format:
    - Use 3.0
 -- Robert Ancell <robert.anc...@canonical.com>   Fri, 08 Mar 2013 11:06:52 
+1300

** Changed in: lightdm (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
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
  (lightdm.conf)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1128474/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to