LightDM GTK Greeter 1.9.0
Milestone information
- Project:
- LightDM GTK Greeter
- Series:
- 1.9
- Version:
- 1.9.0
- Released:
- Registrant:
- Sean Davis
- Release registered:
- Active:
- Yes. Drivers can target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- No bugs are targeted to this milestone.
Download files for this release
Release notes
Overview of changes in lightdm-gtk-greeter 1.9.0
* Drop Gtk2 support
Overview of changes in lightdm-gtk-greeter 1.8.6
* New features:
- Option to set monitor for displaying greeter windows: active-monitor
- Option to control usage of user's background: user-background (LP: #1306362)
- Panel layout now fully customizable
- New builtin indicator: ~layout (LP: #1240569)
- New accessibility menu item: screen reader (F4 hotkey) (experimental, LP: #1319848)
- Option to set initial state of accessibility tools: a11y-states (LP: #1319848)
* Bugs fixed:
- Handling laptop lid state (LP: #1273922)
- Lightdm greeter on dual monitor system has bad-sized background (LP: #1314603)
- Login screen wallaper doesn't fill screen (LP: #1325719)
- Use avatar set in config also without userlist (LP: #1317236)
- Don't use XInput2 to set the root cursor (LP: #1024482)
- Possible sigfault if sessions list is empty
* Additional fixes:
- Message "Failed to authenticate" do not overwrites the PAM error message now
- Do not display password entry if password is not required
- Passing all defined arguments to "onboard" in xembed mode
- Checking for libido version at build
* Updated translations
* Required configuration changes:
- host and clock labels are indicators now, new default panel layout:
- You need to mark laptop monitor with "laptop=true" key in lightdm-
to enable lid state handling (see the included lightdm-
template)
Changelog
This release does not have a changelog.
0 blueprints and 0 bugs targeted
There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.
