void-linux / void-linux/void-docs

session and seat management

Open
#897 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
217
Forks
212
Avg merge
2d 21h
Merged PRs (30d)
1

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:

  1. dbus session bus: turnstile
  2. XDG_RUNTIME_DIR: turnstile or elogind
  3. user services for pipewire, pipewire-pulse and wireplumber: turnstile
  4. Wayland: elogind or seatd
  5. polkit, rtkit: elogind
  6. 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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.