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

External links not working in Linux AppImage

Open
#335 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
linux
Domain
desktop

Research direction

Start with the external-link opening path associated with backend/wails_logger.go:31 and reproduce the failure by running the Linux AppImage from a terminal. Check the Help, SMM GitHub, and mod-description links; done means external links open in the system browser without the kde-open symbol lookup error.

Written by the indexing model from the issue text.

Description

I've been trying out playing on Linux and for some reason the mod manager fails to open external links. For example, the "Help" and "SMM GitHub" buttons on the sidebar don't do anything and neither do links in mod descriptions (although direct links to other mods do work within the app). Other than this the mod manager seems to work just fine.

Running the AppImage from a terminal produces this output when clicking a link:

kde-open: symbol lookup error: /lib/x86_64-linux-gnu/libcurl-gnutls.so.4: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation
2025-12-06T16:37:52-05:00 ERR backend/wails_logger.go:31 Unable to open default system browser

I wouldn't be surprised if this is some issue on my end, but it's my understanding that AppImages are supposed to be distro-independent so I figured I'd bring it up here.

If it helps, I'm running Kubuntu 25.10 (KDE Plasma 6.4.5 on Ubuntu 25.10).

Dominant language
Svelte
Stars
500
Forks
94
Avg merge
9d 19h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

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 satisfactorymodding/SatisfactoryModManager

All issues in satisfactorymodding/SatisfactoryModManager

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.