Lock-Screen: Unity falls-back to old screensaver lock if onscreen keyboard is enabled (Zesty)

[Khurshid Alam]

Unity falls-back to old lock from gnome-screensaver if accessibility is enabled because accessibility in the new lock-screen is partially broken. Please fix accessibility for new lock-screen

How to reproduce:
-------------------------
1. Go to system-settings ⟶ Universal Access ⟶ Seeing
2. Turn on Screen-Reader
3. Restart lightdm or reboot
4. Press CTRL+ALT+L

Current Behavior:
---------------------
It uses old screensaver lock instead of unity-greeter.

Expected Behavior:
------------------------
It should be using new lock-screen

Severity: High
---------------------------
This bug is pretty well hidden. Sometimes when app which depends on-screen keyboard (ex: orca) gets updated, it automatically turns on screen-reader. It can also get turned on if user accidentally press CTRL+ALT+S. User will have no clue whats hit him.

Reason:
----------------------------
Accessibility is enabled because accessibility in the new lock-screen is partially broken. It was supposed to be fixed for 16.04, but that didn't happen.

⇛ Please fix accessibility for new lock-screen. Thanks

Info:
------
OS: Ubuntu 17.04 (32 bit/64bit)

unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1

gnome-screensaver: 3.6.1-7ubuntu5

unity: 7.5.0+17.04.20170301-0ubuntu1

lightdm: 1.22.0-0ubuntu1

lignome-desktop-3-12: 3.24.0-0ubuntu1

[Khurshid Alam (khurshid-alam)]

out put of /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter:
------------------------------------------------------------------------------

unity-greeter.vala:80: Failed to connect to LightDM daemon: Unable to determine socket to daemon

Note: I tried installing gnome-flashback-session which installed gnome-settings-daemon. But even after completely gnome-settings-daemon didn't fix the issue. (Unity & flashback, both session worked side-by-side in all previous releases, so I don't know if it is related.)

[Khurshid Alam (khurshid-alam)]

Apparently, It's this issue- LP: #1310404

Few!

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Andrea Azzarone (azzar1)]

This is the wanted behaviour considering that Unity lockscreen does not support a11y and fixing this is too time-expensive.