Session remains after wayland-logout when a running app is session leader
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 237
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 1
Description
Describe the bug
Session still shows on loginctl list-sessions as state=Closing if a session leader app is running before wayland-logout is called. One such app is wallock, which ps aux lists as STAT=RLsl and continues running even as wayfire is exited.
To Reproduce
Steps to reproduce the behavior:
- Run an app that is a session-leader
- Use wayland-logout (or something else that calls SIGTERM)
Expected behavior
Session should exit
Wayfire version
Current master
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with a session-leader app such as wallock running, then invoke wayland-logout or another SIGTERM-based logout and inspect loginctl list-sessions. Trace the session shutdown behavior around the compositor exit; done means the session no longer remains in state=Closing after logout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100