session and seat management
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start by reviewing the current session and seat management documentation and its four option sections. Map which components each option provides, then reorganize the guidance so the recommended combinations, trade-offs, and possible desktop ISO default are explicit; done means users can choose a working setup without relying on the listed hacks.
Written by the indexing model from the issue text.
Description
The current documentation for session and seat management is pretty neutral and doesn't suggest any solution. It provides 4 sections with different options, where the user has to basically always choose dbus and then one or two other options, of which some overlap or conflict.
I think the core issues that should be addressed are:
- dbus session bus: turnstile
XDG_RUNTIME_DIR: turnstile or elogind- user services for pipewire, pipewire-pulse and wireplumber: turnstile
- Wayland: elogind or seatd
- polkit, rtkit: elogind
- power management (hooks, events and triggering (swayidle, gnome, kde)): elogind
If we want to solve them that makes turnstile a hard requirement, no more hacky dbus-run-session, no more xdg autostart bullshit for user services.
Then the next choice is between elogind and seatd, seatd only provides the bare minimum to make wayland work. elogind solves the core issues and provides additional features like uaccess udev device access and the logind dbus api for desktop environments.
Might also make sense to just make this default for the desktop ISOs.
- Dominant language
- CSS
- Stars
- 217
- Forks
- 212
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
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.
More from void-linux/void-docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
void-linux/void-docs#849 · 2 comments ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 75/100
void-linux/void-docs#595 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
void-linux/void-docs#532 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
void-linux/void-docs#899 · 5 comments · 2 reactions ·
-
Difficulty 2/5 1-2 days Newbie friendliness 57/100
void-linux/void-docs#894 ·
All issues in void-linux/void-docs
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
A11y ♿️
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
documentation improve or update documentation priority/low triage
Difficulty 2/5 Half a day Newbie friendliness 86/100
warpdotdev/docs#782 · 1 comment ·