Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

flathub: move to the latest GNOME runtime (48 is end-of-life)

Open
  • Is something wrong?
#1,579 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
54/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
dart, flutter, linux
Domain
desktop, devops

Research direction

Start with the Flatpak manifest and run flatpak-builder-lint manifest to confirm the runtime version offered at submission time. Check whether GTK 3, libsecret, and libayatana-appindicator are available in that runtime, then retest the window, theming, file chooser, secrets, SSH tunnels, and MCP server. Done means the manifest uses the latest available GNOME runtime and the listed checks pass.

Written by the indexing model from the issue text.

Description

enhancement flathub

Part of #1060. Reviewer: "It's not the latest runtime." Linter: runtime-is-eol-org.gnome.Platform-48 (error), runtime-update-available-to-org.gnome.Platform-51 (warning).

Rules: the runtime "must be the latest version at that time of submission"; "Submissions using an end-of-life runtime ... will not be accepted."

Work

  • Switch runtime-version to the latest GNOME runtime offered by the linter at submission time
  • Check GTK 3 / libsecret / libayatana-appindicator (if used) availability in that runtime
  • Re-test: window, theming, file chooser, secrets, SSH tunnels, MCP server
  • Re-run flatpak-builder-lint manifest
Dominant language
Dart
Stars
23
Forks
1
Avg merge
45m
Merged PRs (30d)
529

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from QueryaHub/Querya-Desktop

All issues in QueryaHub/Querya-Desktop

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.