Merge lp:~mterry/lightdm/activate-after-unlocking into lp:lightdm
Proposed by
Michael Terry
Status: | Merged |
---|---|
Merged at revision: | 1932 |
Proposed branch: | lp:~mterry/lightdm/activate-after-unlocking |
Merge into: | lp:lightdm |
Diff against target: |
32 lines (+20/-0) 1 file modified
src/login1.c (+20/-0) |
To merge this branch: | bzr merge lp:~mterry/lightdm/activate-after-unlocking |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Ancell | Approve | ||
PS Jenkins bot | continuous-integration | Approve | |
Review via email: mp+211235@code.launchpad.net |
Commit message
Call Activate() after Unlock() when unlocking a logind session. This ensures that no matter the display server, the session will be active.
Description of the change
Call Activate() after Unlock() when unlocking a logind session. This ensures that no matter the display server, the session will be active.
X11 does it automatically because logind seems to track VT switches. But for Mir or some other display server, we need to make sure it happens. Since it's good to be explicit even for X11, we just unconditionally do it here.
To post a comment you must log in.
PASSED: Continuous integration, rev:1932 jenkins. qa.ubuntu. com/job/ lightdm- ci/256/ jenkins. qa.ubuntu. com/job/ lightdm- trusty- amd64-ci/ 50 jenkins. qa.ubuntu. com/job/ lightdm- trusty- armhf-ci/ 50
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/lightdm- ci/256/ rebuild
http://