Skip to content

[Bug]: SnapShot GNOME extension is "out of date" on GNOME 51 #16881

Closed

Description

@jay-tau

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

  1. Upgrade to GNOME Shell 51.0 (Wayland) with T3 Code 0.0.45 and its bundled [email protected] extension (version 2) installed and enabled.
  2. Sign out and back in.
  3. Run gnome-extensions info [email protected].

Expected behavior

The bundled extension loads on GNOME 51 and is available as an active-window SnapShot backend.

Actual behavior

GNOME refuses to load it and reports State: OUT OF DATE (output below).

apps/desktop/gnome-extension/metadata.json lists "shell-version": ["45", "46", "47", "48", "49", "50"]. T3 Code's own setup check rejects 51 for the same reason: GnomeCaptureSetup.state() returns status unsupported when the bundled shell-version doesn't include the session's major version (GnomeCaptureSetup.ts#L172).

Impact

Major degradation or frequent failure

On my GNOME 51 setup, the unmodified bundled version-2 extension is marked OUT OF DATE and unavailable as a capture backend.

Version or commit

0.0.45 (t3code-bin from the AUR). The same metadata and setup checks are present at commit 611132c171f3a821bd2e32f22261135cef6330ac.

Environment

CachyOS (Arch), GNOME Shell 51.0, Wayland, kernel 7.2.9-1-cachyos, xdg-desktop-portal 1.22.1 with xdg-desktop-portal-gnome 51.0. AMD HawkPoint iGPU and NVIDIA RTX 4060 Laptop GPU.

Logs or stack traces

$ gnome-extensions info [email protected]
[email protected]
  Name: T3 Code SnapShots
  ...
  Enabled: Yes
  State: OUT OF DATE

$ gdbus call --session --dest org.freedesktop.portal.Desktop --object-path /org/freedesktop/portal/desktop \
    --method org.freedesktop.DBus.Properties.GetAll org.freedesktop.portal.Screenshot
({'AvailableTargets': <uint32 0>, 'version': <uint32 2>},)

Screenshots, recordings, or supporting files

No response

Workaround

Add "51" to shell-version in the installed extension's metadata.json under ${XDG_DATA_HOME:-$HOME/.local/share}/gnome-shell/extensions/[email protected]/, then sign out and back in. This edits only the installed copy; T3 Code's setup check still uses its bundled metadata.

I tested this locally:

  • The extension is ACTIVE, with no errors from it in the gnome-shell journal.
  • A SnapShot (Ctrl+Shift+2) of another window succeeded in about 100 ms, with the window's app name and title attached.
  • It went through the extension, not the portal. This system's Screenshot portal reports version 2 and AvailableTargets 0 (above), so backend selection falls through to gnome-extension (LinuxSnapShot.ts#L196-L211).

Static review of extension.js, captureService.js, captureFeedback.js and feedbackGeometry.js found no use of the removed, changed or deprecated APIs listed in the GNOME Shell 51 porting guide. Together with the local result, this suggests a metadata compatibility update. It is not a full GNOME 51 regression test.

Proposed fix

Add "51" to shell-version and bump metadata version from 2 to 3. The bump makes existing version-2 installations eligible for replacement through T3 Code's setup flow: state() requires a higher bundled version for update-required (L189), and perform("install-extension") accepts only not-installed or update-required (L229). Adding "51" while keeping version 2 would not make those installations eligible through this flow. Installing the update still requires signing out and back in.

In apps/desktop/gnome-extension/metadata.json:

-  "shell-version": ["45", "46", "47", "48", "49", "50"],
+  "shell-version": ["45", "46", "47", "48", "49", "50", "51"],
-  "version": 2,
+  "version": 3,

The tests need updating too:

  • GnomeCaptureSetup.test.ts currently uses { shell: "51.0" } as its unsupported example (L126). It also has current-version fixtures at version: 2.
  • LinuxSnapShot.dbus.test.ts has a metadata-version fixture at 2 (L97).
  • A test for the version-2-to-3 upgrade would cover this case.

Keep the capture service's D-Bus protocol version (get Version() in extension.js) at 2. LinuxSnapShot.ts accepts only protocol 1 or 2, and this metadata revision doesn't change the protocol.

Activity

  1. juliusmarminge commented on Oct 7, 2026

    @juliusmarminge
    Member

    Note

    Grok responding on behalf of Julius.

    Thanks for the detailed report. Confirmed on current main (611132c).

    Root cause

    • gnome-extension/metadata.json sets "shell-version": ["45" … "50"] and "version": 2, so GNOME Shell 51 marks the extension OUT OF DATE.
    • GnomeCaptureSetup.ts#L171-L175 uses the same bundled list, so state() returns unsupported on 51.
    • GnomeCaptureSetup.ts#L189 only reports update-required when the bundled version is higher than the installed one, and L229 only allows install-extension from not-installed or update-required. Adding "51" without a version bump won't replace existing v2 installs.

    Fix

    1. Add "51" to shell-version and bump metadata version from 2 to 3.
    2. Update GnomeCaptureSetup.test.ts#L120-L127: the { shell: "51.0" } → unsupported case needs a different unsupported version (for example "52.0"). The version: 2 installed fixtures (L121-L125, L144, L160, L175, L182) should become 3, otherwise they'll report update-required. Add a version: 2 → update-required case.
    3. Keep the extension's D-Bus Version property at 2 (extension.js#L143). LinuxSnapShot.ts#L209-L210 only accepts D-Bus versions 1 and 2, and LinuxSnapShot.dbus.test.ts tests against 2. The metadata version and the D-Bus protocol version are separate numbers.

    Users still need to sign out and back in after the update installs.

    Workaround (from the reporter)
    Add "51" to shell-version in the installed copy at ${XDG_DATA_HOME:-$HOME/.local/share}/gnome-shell/extensions/[email protected]/metadata.json, then sign out and back in. The reporter says the extension then went ACTIVE and window capture worked through it. T3 Code's setup screen will still show unsupported because it checks the bundled metadata. That result comes from their local test plus a static check against the GNOME 51 porting guide. We haven't run a full GNOME 51 regression test.

  2. added
    bugSomething is broken or behaving incorrectly.
    via-triageFiled through npx t3 triage
    on Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.via-triageFiled through npx t3 triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions