Skip to content

Add Lynko - #11841

Open
probonopd wants to merge 1 commit into
masterfrom
discover/Lynko
Open

Add Lynko#11841
probonopd wants to merge 1 commit into
masterfrom
discover/Lynko

Conversation

@probonopd

Copy link
Copy Markdown
Member

Repository: https://github.com/ErfanBagheri404/Lynko

Mirror & control any Android phone from Windows, Linux, or macOS over Wi-Fi. Open-source Samsung Flow / AirDroid alternative. no USB, no ADB, no root, no cloud.

  • Stars: 5
  • Release with the AppImage: v0.1.0 (2026-10-27T05:32:32Z)
  • AppImage asset: Lynko_0.1.0_amd64.AppImage
  • License: Apache-2.0

Found by .github/workflows/discover-apps.yml, which looks for GitHub
repositories that publish AppImages but are not in the catalog yet. This
entry was not tested by a human; please review it before merging.

Discovered on GitHub as publishing AppImages on its releases, by
discover-apps.yml. Needs a maintainer's review.
@github-actions github-actions Bot added error-app-exits Test failed: the application quit or crashed right after starting error-not-executable Test failed: a file inside the AppImage is not executable labels Nov 11, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

@ErfanBagheri404: this pull request adds the AppImage from your GitHub repository to the AppImage catalog; the test reports the following. Could you have a look?

Tested:

Compatibility: not self-contained: uses the C library of the system; references glibc 2.39

  • A file inside the AppImage is not executable. Please check the file permissions before packaging the AppImage.
  • AppRun.wrapped (or the launcher it starts) could not be executed. This typically happens with Tauri and linuxdeploy builds when a cached launcher was packaged with mode 0770 and is owned by root, so that it is not executable for the test user. Please make the AppDir readable and executable for everyone before packaging, e.g. chmod -R a+rX AppDir (and chmod a+x on AppRun and AppRun.wrapped) before running appimagetool.
  • The application quit or crashed right after starting; the error below usually shows why. Note that the test runs the application without network access, on purpose, and that this is a requirement for the catalog: an AppImage must start without network (users are offline too). If the application needs a server, a login or an update check to start, please make it show its window (or at least a message) first and connect afterwards, and handle a failed connection instead of exiting.

First error in the log:

/run/firejail/appimage/AppRun: line 12: /run/firejail/appimage/AppRun.wrapped: Permission denied

The application showed no window, but may be a system tray application (usr/lib/girepository-1.0/AyatanaAppIndicator3-0.1.typelib: app_indicator_new); running it again with a system tray
/run/firejail/appimage/AppRun: line 12: /run/firejail/appimage/AppRun.wrapped: Permission denied
No icon appeared in the system tray either
ERROR: The application exited within 11 seconds instead of showing a window

What next: once the AppImage is fixed (e.g. in a new release), comment /retest here to test it again. If it should not be in the catalog after all, close this pull request; an app that is already in the catalog can be removed by a maintainer with /remove.

Commit fcd9231. Full log

@ErfanBagheri404

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Nov 15, 2026
@probonopd probonopd reopened this Nov 15, 2026
@github-actions github-actions Bot added error-glibc-too-new Test failed: built on a too new system (needs a newer glibc) and removed error-not-executable Test failed: a file inside the AppImage is not executable labels Nov 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

Tested:

Compatibility: not self-contained: uses the C library of the system; references glibc 2.43

  • The AppImage needs a newer C library (glibc, or the C++ library libstdc++) than the test system has; the error names the version that is missing (e.g. GLIBC_2.38). The test runs on the oldest Ubuntu LTS release that is still in standard support (see https://ubuntu.com/about/release-cycle), because an AppImage is meant to run on any current Linux distribution, including older ones, and glibc can only be as old as the system the AppImage was built on: a program built on a newer system links against symbols that older systems do not have. The fix is to build on the oldest still-supported LTS release (in GitHub Actions, the oldest ubuntu-* runner still offered, or a container of that release), not on the newest system. If the program itself needs a newer compiler, build in a container of the old release with a newer toolchain (e.g. the toolchain PPAs), statically link what needs it, or bundle the C library together with its dynamic loader (ld-linux) in the AppImage: then the host's glibc does not matter at all (the test reports X-AppImage-Libc=bundled). See https://docs.appimage.org/reference/best-practices.html#binaries-compiled-on-old-enough-base-system
  • The application quit or crashed right after starting; the error below usually shows why. Note that the test runs the application without network access, on purpose, and that this is a requirement for the catalog: an AppImage must start without network (users are offline too). If the application needs a server, a login or an update check to start, please make it show its window (or at least a message) first and connect afterwards, and handle a failed connection instead of exiting.

First error in the log:

lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by lynko)
lynko: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by lynko)
lynko: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgdk-3.so.0)
lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgdk-3.so.0)
lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.43' not found (required by /run/firejail/appimage/usr/lib/libglib-2.0.so.0)
lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libglib-2.0.so.0)
lynko: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libdbus-1.so.3)
lynko: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.43' not found (required by /run/firejail/appimage/usr/lib/libwebkit2gtk-4.1.so.0)
lynko: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libwebkit2gtk-4.1.so.0)
lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.42' not found (required by /run/firejail/appimage/usr/lib/libwebkit2gtk-4.1.so.0)
lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libwebkit2gtk-4.1.so.0)
lynko: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgtk-3.so.0)
lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgtk-3.so.0)
lynko: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libsoup-3.0.so.0)

What next: once the AppImage is fixed (e.g. in a new release), comment /retest here to test it again. If it should not be in the catalog after all, close this pull request; an app that is already in the catalog can be removed by a maintainer with /remove.

Commit fcd9231. Full log

@ErfanBagheri404

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Nov 15, 2026
@probonopd probonopd reopened this Nov 15, 2026
@github-actions github-actions Bot added screenshot-ok Test passed; the screenshot was checked and looks fine and removed error-app-exits Test failed: the application quit or crashed right after starting error-glibc-too-new Test failed: built on a too new system (needs a newer glibc) labels Nov 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

✅ Test passed

Please check that the screenshot shows the application's main window.

Lynko

Lynko

Tested:

Compatibility: not self-contained: uses the C library of the system; references glibc 2.35

Suggestions for improving the AppImage:

  • The window is mostly dark, so the application seems to start in a dark theme although the test system is not set to dark mode. Please use a light mode by default and use the dark theme only when the system is configured for dark mode (e.g. the GTK/Qt or theme setting) or the user chooses it in the settings.
  • The AppImage contains no update information, so users cannot update it with AppImageUpdate or similar tools. Please consider embedding it when building the AppImage (e.g., appimagetool -u) and publishing the .zsync file next to the AppImage; see https://docs.appimage.org/packaging-guide/optional/updates.html

Commit fcd9231. Full log

@ErfanBagheri404

Copy link
Copy Markdown

Note: the body still says v0.1.0 - my token can't edit it (write access on this repo is restricted to the bot). The tested release is v0.2.2 (Lynko_0.2.2_amd64.AppImage, glibc 2.35, world-executable launcher) and the test passed.

@probonopd

Copy link
Copy Markdown
Member Author

Thanks @ErfanBagheri404. It says 0.2.2 in the post just about yours.
But why is the interface dark on a system that is not set to dark mode?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-discovered screenshot-ok Test passed; the screenshot was checked and looks fine

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants