Comment 1 for bug 1674389

Might be a two-parter bug.

On the indicator-session side, we need to handle "challenge" as a response to CanSuspend / CanHibernate calls and, when calling suspend/hibernate, allow interactivity. This is in the fix-suspend-on-u8 branch.

Even after this is done, u8's challenge prompt is the lockscreen, so the unintuitive UX is that you have to (appear to) unlock in order to suspend. So in u8,
1. we should consider whether a password prompt should be necessary for suspend, and
2. if prompt is necessary, Calls to login1.Suspend(interactive=True) should probably be handled more elegantly than showing the lockscreen prompt