Skip to content

docs(linux): classic aw-qt bundle runs awatcher on Wayland from v0.14.2 - #218

Open
TimeToBuildBob wants to merge 1 commit into
ActivityWatch:masterfrom
TimeToBuildBob:docs/linux-qt-wayland-awatcher
Open

TimeToBuildBob wants to merge 1 commit into
ActivityWatch:masterfrom
TimeToBuildBob:docs/linux-qt-wayland-awatcher

Conversation

@TimeToBuildBob

Copy link
Copy Markdown
Contributor

Documents the classic Linux bundle's Wayland watcher, now that ActivityWatch/activitywatch#1531 (bundle aw-awatcher) and ActivityWatch/activitywatch#1532 (pin aw-qt with the ActivityWatch/aw-qt#142/#143 substitution) are both on master.

Merge when v0.14.2 is tagged: the text says "from v0.14.2"; v0.14.1 does not contain this.

Verification

Master build 71cdc78a (Release run 40363243991, artifact builds-ubuntu-22.04-py3.9, activitywatch-v0.14.2b1.dev-71cdc78-linux-x86_64.zip), unmodified bundled aw-qt (pin 5fb7634) under an isolated headless Sway session with a real foot window:

[INFO ]: Found 8 bundled modules
[INFO ]: Wayland session detected: substituted ['aw-watcher-window', 'aw-watcher-afk'] with aw-awatcher
[INFO ]: Starting module aw-awatcher

Both aw-watcher-window_<host> (app: wayland-259b, title: wayland-259b-proof) and aw-watcher-afk_<host> received events from client awatcher.

Only Sway was tested here. The KDE/GNOME wording is taken from awatcher's supported-environments table, not from a test, which is why the FAQ links to it. Local sphinx-build adds no new warnings; the wayland label added to the FAQ entry resolves from getting-started.

Git-Session-Id: 153ccb18-ce8a-4486-9453-991d51f99656
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant