https://bugs.kde.org/show_bug.cgi?id=377152
Martin Gräßlin <mgraess...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
Latest Commit| |https://commits.kde.org/ksc
| |reenlocker/06917c1253eb644e
| |139c28427f4fc4b8f3e0a41b
--- Comment #2 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit 06917c1253eb644e139c28427f4fc4b8f3e0a41b by Martin Gräßlin.
Committed on 16/03/2017 at 18:34.
Pushed by graesslin into branch 'master'.
[ksld] Don't unset greeter connection on destroy unconditionally
Summary:
If the greeter exits the Wayland connection gets destroyed and a new
greeter with a new Wayland connection gets created. As the destroying
of the Wayland connection is async it can happend that the destroy
signal is emitted after the new connection is created. So far our code
unconditionally reset the connection on destroy which resulted in KWin
not being able to recognize the new greeter and only presenting a black
screen. After unlock with loginctl unlock-session the session shows a
dead greater window. Which can be explained by the connection never
getting destroyed.
This change verifies that the greeter connection is actually the one
which is currently in use. If the greeter dies the new greeter is shown
properly in the Wayland session and no dead greeter is shown after
unlock.
Test Plan: killed kscreenlocker_greet 6 times, always properly restarted
Reviewers: #plasma
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D5008
M +4 -1 ksldapp.cpp
https://commits.kde.org/kscreenlocker/06917c1253eb644e139c28427f4fc4b8f3e0a41b
--
You are receiving this mail because:
You are watching all bug changes.
