hyprwm
/
hyprlock
mirror of https://github.com/hyprwm/hyprlock.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

core: handle ext_session_lock_v1::finished as defined in the protocol (#418)

This commit is contained in:
Maximilian Seidler 2024-07-11 16:15:32 +02:00 committed by GitHub
parent e5f0b56d07
commit b407128cae
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/core/hyprlock.cpp
View File

@ -959,8 +959,15 @@ void CHyprlock::onLockLocked() {
void CHyprlock::onLockFinished() { void CHyprlock::onLockFinished() {
Debug::log(LOG, "onLockFinished called. Seems we got yeeten. Is another lockscreen running?"); Debug::log(LOG, "onLockFinished called. Seems we got yeeten. Is another lockscreen running?");
g_pRenderer = nullptr; if (m_bLocked)
exit(1); // The `finished` event specifies that whenever the `locked` event has been recieved and the compositor sends `finished`,
// `unlock_and_destroy` should be called by the client.
// This does not mean the session gets unlocked! That is ultimatly the responsiblity of the compositor.
ext_session_lock_v1_unlock_and_destroy(m_sLockState.lock);
else
ext_session_lock_v1_destroy(m_sLockState.lock);
m_bTerminate = true;
} }
ext_session_lock_manager_v1* CHyprlock::getSessionLockMgr() { ext_session_lock_manager_v1* CHyprlock::getSessionLockMgr() {