-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session remains after wayland-logout when a running app is session leader #2336
Comments
What makes you think this is a bug in Wayfire and not in wallock? (i.e what should Wayfire do that it doesn't?) |
Sorry, I don't have much to give on this except that wallock is shut down in Hyprland (kills app and allows it to do its socket removal cleanup). Sway also doesn't kill it. Actually, my "session leader" theory was wrong too because the app has a --no-daemonize flag that makes it run as RLl+ and it still isn't shut down in wayfire, and since it's the only L process I have running I'm inclined to think it's the memory lock. I did an interesting experiment though and ran a simple C app that locks the memory:
When I run this alongside wallock, they both get cleaned up when I do |
Describe the bug
Session still shows on
loginctl list-sessions
asstate=Closing
if a session leader app is running before wayland-logout is called. One such app is wallock, whichps aux
lists asSTAT=RLsl
and continues running even as wayfire is exited.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Session should exit
Wayfire version
Current master
The text was updated successfully, but these errors were encountered: