Skip to content

Add BigText - #11914

Merged
github-actions[bot] merged 1 commit into
masterfrom
discover/BigText
Nov 13, 2026
Merged

github-actions[bot] merged 1 commit into
masterfrom
discover/BigText

Conversation

@probonopd

Copy link
Copy Markdown
Member

Repository: https://github.com/Erkinbek/bigtext

Fast text editor for huge files (1-50+ GB): opens 10 GB logs instantly and never freezes. 2.5 GB/s search, regex, replace, editing, atomic save, diff, hex view. Windows, Linux, macOS. Rust + egui.

  • Stars: 29
  • Release with the AppImage: v0.7.1 (2026-11-12T05:14:48Z)
  • AppImage asset: bigtext-linux-x64.AppImage
  • License: MIT

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-glibc-too-new Test failed: built on a too new system (needs a newer glibc) labels Nov 12, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

@Erkinbek: 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.43

Names:

WARNING: AppImage name 'bigtext-linux-x64.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')
  • 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.
  • Please check the remarks about the names below.

First error in the log:

/run/firejail/appimage/usr/bin/bigtext: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.43' not found (required by /run/firejail/appimage/usr/bin/bigtext)
/run/firejail/appimage/usr/bin/bigtext: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by /run/firejail/appimage/usr/bin/bigtext)

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 6ca4496. Full log

Erkinbek added a commit to Erkinbek/bigtext that referenced this pull request Nov 12, 2026
…systems

ubuntu-latest moved to 26.04 before v0.5.0, so the Linux binaries of
v0.5.0 to v0.7.1 need glibc 2.43 and do not start on Ubuntu 22.04/24.04,
Debian 12/13, Mint 22 or Fedora 43 (the AppImage, the .deb and the
tarball alike). The AppImage catalog's test caught it
(AppImage/appimage.github.io#11914: GLIBC_2.43 not found).

- The linux-x64 job builds in an ubuntu:22.04 container (glibc 2.35, the
  oldest LTS still supported, where the catalog tests). The container is
  bare, so the dependency step installs the compiler, git, curl and zstd
  too, runs before checkout and without sudo; its cache key is separate.
- The .deb depends on libc6 >= the newest glibc symbol version the
  binaries use, so dpkg refuses an install that could not start.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Erkinbek

Erkinbek commented Nov 12, 2026 •

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Nov 12, 2026
@probonopd probonopd reopened this Nov 12, 2026
@github-actions github-actions Bot added error-missing-library Test failed: see the test result comment and removed error-glibc-too-new Test failed: built on a too new system (needs a newer glibc) labels Nov 12, 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.35

Names:

WARNING: AppImage name 'bigtext-linux-x64.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')
  • The application needs a library that is neither in the AppImage nor on the test system ("error while loading shared libraries" or "Library ... could not be loaded", the first error below names it). Please bundle this library, and what it depends on, in the AppImage: an AppImage cannot rely on libraries that are not installed on every target 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.
  • Please check the remarks about the names below.

First error in the log:

Library libxkbcommon-x11.so could not be loaded.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

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 6ca4496. Full log

Erkinbek added a commit to Erkinbek/bigtext that referenced this pull request Nov 12, 2026
…indow libraries

BigText loads its window libraries at run time (winit), and on X11 it
needs libxkbcommon-x11, which a desktop without Qt or GNOME may not
have: it then quit at start with "Library libxkbcommon-x11.so could not
be loaded". The AppImage catalog's test system is such a one
(AppImage/appimage.github.io#11914, the second test, of v0.7.2).

- The AppImage carries libxkbcommon-x11 with libxkbcommon (the two share
  private structures, so they go together) and libxcb-xkb. The binary
  finds them through its run path, set with patchelf, not through
  LD_LIBRARY_PATH, which the programs BigText starts would inherit.
  libX11, libxcb, libGL and libwayland stay the system's, as AppImages
  leave them.
- The .deb named only libgl1 and libxkbcommon0; it now depends on what
  is loaded on X11 and on Wayland, the libraries the AUR package names.
- CI installs patchelf and libxkbcommon-x11-0 in the build container.

Tested with packages built from the v0.7.2 binaries by these scripts.
The AppImage: in a copy of the catalog's test system (Ubuntu 22.04 with
exactly its packages, no network), where v0.7.2 fails with the same
error, it shows its window in 1 s and typing works, the three libraries
loading from the AppImage; the same on Ubuntu 26.04 beside the system's
libxkbcommon 1.13. The .deb: apt installs it on bare Ubuntu 22.04 and
24.04 and Debian 12 and BigText starts; Debian 11 (glibc 2.31) refuses
it.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@Erkinbek

Erkinbek commented Nov 12, 2026 •

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Nov 12, 2026
@probonopd probonopd reopened this Nov 12, 2026
@github-actions github-actions Bot removed error-app-exits Test failed: the application quit or crashed right after starting error-missing-library Test failed: see the test result comment labels Nov 12, 2026
@github-actions

Copy link
Copy Markdown
Contributor

✅ Test passed

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

BigText

BigText

Tested:

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

Names:

WARNING: AppImage name 'bigtext-linux-x64.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')

Warnings:

  • Please check the remarks about the names below.
  • 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 6ca4496. Full log

@Erkinbek

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Nov 13, 2026
@probonopd probonopd reopened this Nov 13, 2026
@github-actions github-actions Bot added the screenshot-ok Test passed; the screenshot was checked and looks fine label Nov 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

✅ Test passed

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

BigText

BigText

Tested:

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

Names:

WARNING: AppImage name 'bigtext-linux-x64.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')

Warnings:

  • Please check the remarks about the names below.

Commit 6ca4496. Full log

@github-actions
github-actions Bot merged commit 4d48581 into master Nov 13, 2026
13 of 15 checks passed
@github-actions
github-actions Bot deleted the discover/BigText branch November 13, 2026 13:33
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