Adom Hydrogen (Linux)
Public Made by Adomby adom
The Linux platform layer for Adom Hydrogen: Ubuntu, Debian and Fedora, the workspace and the computer.
d8a45ab
name: hydrogen-screen-lock description: >- Hydrogen screen capture and the display wake-lock on Linux: why Hydrogen's screenshots never keep the display awake or block the screensaver, and what to check when something does. Use when the display won't sleep, the screensaver or screen lock is blocked, or before adding a screenshot or recording feature.
Hydrogen screen capture & the display wake-lock
A browser screen share (getDisplayMedia) keeps the display awake for as long as the stream
lives: no screensaver, no blank, no auto-lock, and on some screens burn-in. Web Hydrogen keeps
such a stream alive all session, so it can hold the display on.
Hydrogen on Linux holds no wake-lock
- Screenshots are a one-shot WebKit snapshot of Hydrogen's own window (
POST /screenshot,adom-cli hydrogen screenshot). No media stream, nothing to release. Seehydrogen-self-screenshot. - Native recording does not run on Linux (
/recording/native/startanswers that it is not available here), so there is no recorder to forget. - Hydrogen takes no idle or screensaver inhibitor of its own.
So if the display will not sleep, the holder is something else.
Rules for any new capture feature
- Screenshots: grab the frame → done. Never hold a capture between shots.
- Anything long-running needs a hard maximum duration, a visible "recording" indicator, and a
reasonto extend the cap.
If you DO find the display pinned on
In a terminal on the desktop (not in the workspace):
systemd-inhibit --listshows logind inhibitors (look foridle).- On GNOME,
gnome-session-inhibit --listshows apps that asked the session to stay awake. - A browser holding it is usually a screen share: a web Hydrogen tab or a pup capture.
Stop it at the source:
adom-cli hydrogen sharing stop, close the tab, orpup_record_stop. - If it names Hydrogen (
adom-hydrogen), that is unexpected: save the output and file it as a bug.
A screensaver cannot clear another process's inhibitor, so release at the source is the fix.
Separate concern: capture contention
Another thread's screenshot must never silently fail. With no native recorder on Linux this
rarely matters; if the adom-cli path answers capture_busy, read its alternatives and use
POST /screenshot. GET /capture/availability lists the methods.
Related skills
hydrogen-recording: why native recording is not on Linux, and what to use insteadhydrogen-self-screenshot: WebKit screenshots of Hydrogen's window (no wake-lock)- hydrogen-notifications — OS toasts + the in-app
/ui/toast
---
name: hydrogen-screen-lock
description: >-
Hydrogen screen capture and the display wake-lock on Linux: why Hydrogen's
screenshots never keep the display awake or block the screensaver, and what
to check when something does. Use when the display won't sleep, the
screensaver or screen lock is blocked, or before adding a screenshot or
recording feature.
---
# Hydrogen screen capture & the display wake-lock
A browser screen share (`getDisplayMedia`) keeps the display awake for as long as the stream
lives: no screensaver, no blank, no auto-lock, and on some screens burn-in. Web Hydrogen keeps
such a stream alive all session, so it can hold the display on.
## Hydrogen on Linux holds no wake-lock
- **Screenshots** are a one-shot WebKit snapshot of Hydrogen's own window (`POST /screenshot`,
`adom-cli hydrogen screenshot`). No media stream, nothing to release. See
`hydrogen-self-screenshot`.
- **Native recording** does not run on Linux (`/recording/native/start` answers that it is not
available here), so there is no recorder to forget.
- Hydrogen takes no idle or screensaver inhibitor of its own.
So if the display will not sleep, the holder is something else.
## Rules for any new capture feature
- **Screenshots:** grab the frame → done. Never hold a capture between shots.
- Anything long-running needs a hard maximum duration, a visible "recording" indicator, and a
`reason` to extend the cap.
## If you DO find the display pinned on
In a terminal on the desktop (not in the workspace):
1. `systemd-inhibit --list` shows logind inhibitors (look for `idle`).
2. On GNOME, `gnome-session-inhibit --list` shows apps that asked the session to stay awake.
3. A **browser** holding it is usually a screen share: a web Hydrogen tab or a pup capture.
Stop it at the source: `adom-cli hydrogen sharing stop`, close the tab, or
`pup_record_stop`.
4. If it names **Hydrogen** (`adom-hydrogen`), that is unexpected: save the output and file it
as a bug.
A screensaver cannot clear another process's inhibitor, so release at the source is the fix.
## Separate concern: capture contention
Another thread's screenshot must never silently fail. With no native recorder on Linux this
rarely matters; if the adom-cli path answers `capture_busy`, read its `alternatives` and use
`POST /screenshot`. `GET /capture/availability` lists the methods.
## Related skills
- `hydrogen-recording`: why native recording is not on Linux, and what to use instead
- `hydrogen-self-screenshot`: WebKit screenshots of Hydrogen's window (no wake-lock)
- [hydrogen-notifications](../hydrogen-notifications/SKILL.md) — OS toasts + the in-app `/ui/toast`