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

Flatpak build doesn't register as an nxm:// handler out of the box

Open Beginner friendly
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
linux
Domain
cli, desktop

Research direction

Look at the Flatpak manifest file (likely named io.github.Adda0.Stardrop.yml or similar) and the exported .desktop file. Add the MimeType entry and update the Exec line to include --nxm %u as described. Test by building the Flatpak locally and verifying that nxm:// links are associated.

Written by the indexing model from the issue text.

Description

The exported .desktop file for the Flatpak build (io.github.Adda0.Stardrop.desktop) has no MimeType entry and no %u placeholder in Exec:

Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=Stardrop io.github.Adda0.Stardrop

Since Stardrop advertises Nexus Mods integration as a core feature, I'd expect clicking "Mod Manager Download" on Nexus to just work after installing. Instead, nothing happens — there's no association at all between nxm:// and Stardrop unless the user manually writes their own .desktop file with MimeType=x-scheme-handler/nxm; and passes the link through with --nxm %u.

Suggested fix: Add to the manifest/exported desktop file:
MimeType=x-scheme-handler/nxm;
Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=Stardrop io.github.Adda0.Stardrop --nxm %u

Dominant language
No language data
Stars
0
Forks
0
Avg merge
2h 22m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 flathub/io.github.Adda0.Stardrop

All issues in flathub/io.github.Adda0.Stardrop

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.