Releases: Naitrate/Eagle-Linux
Releases · Naitrate/Eagle-Linux
Release list
v4.0.6
Eagle for Linux v4.0.6 A packaging release. Every package now provides the media tools Eagle's plugins shell out to, rather than each one differing. exiv2 is now a declared dependency ---------------------------------- The Exif Metadata plugin ships Windows and macOS builds of exiv2 only, and picks the macOS one on Linux, where it cannot execute and reports "Error: 126". ffmpeg was already declared for the equivalent reason, so exiv2 joins it: on PATH for Nix, in Requires for rpm, in depends for Arch, and built inside the sandbox for Flatpak. This does not fix that plugin on its own. Its bundled binary still has to be replaced with a wrapper; the dependency is what makes such a wrapper able to resolve. The AppImage now carries its tools ---------------------------------- An AppImage has no dependency mechanism, so it was the one package that could silently do nothing on a host without ffmpeg or exiv2. It now ships both, plus ffprobe, with their libraries. This adds roughly 100MB. The core runtime is deliberately left to the host: bundling glibc alongside the host loader is how an AppImage ends up running only on the machine that built it. The build verifies that every other dependency resolves from inside the bundle and that all three tools actually start, so an incomplete bundle fails the build rather than reaching a user. Nothing here changes application behaviour. Everything from v4.0.5 - the fix for videos and other plugin-backed formats getting stuck on "importing" - is included. Fedora users need RPM Fusion for ffmpeg with proprietary codecs.
v4.0.5
Eagle for Linux v4.0.5 Fixes videos and other plugin-backed formats getting stuck on "importing". Thumbnails no longer hang ------------------------- Dragging in an mp4 left the item stuck on "importing" until a 100 second timeout, with nothing logged to explain it. Images imported fine. Every plugin-backed thumbnail runs in a hidden window whose injected code calls a $$electronIpc global. That global is defined by web-capture-preload.js, which upstream ships at the root of the Windows install rather than inside the app payload, so extracting the app dropped it. Without it the injected script threw, the reply never arrived, and the promise never settled - and because nothing rejected, Eagle never fell back to its built-in video handler either. This affected far more than video. The same path serves the HEIC, JXL, RAW, 3D, HDR, VRM, EPUB, SWF and vector thumbnail plugins. Items that failed to import while this was broken need re-importing. Known issue: the Exif Metadata plugin still reports "Error: 126" on Linux. It ships Windows and macOS builds of exiv2 only, and picks the macOS binary on Linux, which cannot execute. That is inside the plugin rather than this port. Fedora users need RPM Fusion for ffmpeg with proprietary codecs.
v4.0.4
Eagle for Linux v4.0.4 A follow-up to v4.0.3 fixing one thing: "start hidden" was being ignored on rpm, Arch and Nix installs. Launch at login now honours "start hidden" everywhere ----------------------------------------------------- When enabling autostart, Eagle prefers copying the installed eagle.desktop over writing a fresh entry, and that copy was verbatim. The installed file launches Eagle normally, so the "start hidden" preference was silently dropped on every rpm, Arch and Nix install - autostart worked, but the window always appeared. Flatpak and AppImage were unaffected. The Exec line is now rewritten while copying, inserting --hidden ahead of any desktop field codes, so "Exec=eagle %u" becomes "Exec=eagle --hidden %u". If you already had launch-at-login enabled, toggle it off and on once to regenerate the entry. Everything from v4.0.3 is included: imported and renamed items no longer collapse to "_", the Flatpak launches, and autostart works under Flatpak and AppImage. Existing items already named "_" will not repair themselves and need re-importing. Fedora users need RPM Fusion for ffmpeg with proprietary codecs.
v4.0.3
Eagle for Linux v4.0.3 Fixes a long-standing bug that made imported and renamed items unusable, and gets the Flatpak launching for the first time. Anyone on v4.0.2 should upgrade: that release could not open a window on a fresh install. Item names no longer collapse to "_" ------------------------------------ Every imported item was stored as "_", and renaming from the inspector appeared to do nothing. Upstream's remainingFilenameLength() only assigns a maximum path length for win32 and darwin, so on Linux it returned NaN and name.substr(0, NaN) emptied every filename. This affected imports and inspector renames alike. Existing items named "_" will not repair themselves - re-import them. Flatpak now launches -------------------- flatpak-builder applies strip-components: 1 to archive sources by default, which flattened Electron's locales/ and resources/ into /app/electron. Electron could not resolve its locale bundle and exited before loading the app, so the Flatpak had never started. Autostart works from Flatpak and AppImage ----------------------------------------- "Launch at login" wrote an entry pointing at a command that does not exist outside the sandbox or AppImage mount, so it reported itself enabled and started nothing. It now re-enters the sandbox via "flatpak run", and uses the AppImage's own path for AppImage installs. Disabling autostart no longer raises an unhandled ENOENT. Packaging --------- - app_patches overrides are re-applied on incremental builds instead of only on a fresh extraction, so a new override can no longer go missing from a build while appearing correct in the working tree. - Release publishing is opt-in for manual workflow runs, so the matrix can be run for test artifacts without pushing anything public. - The smoke test now fails if the filename-length patch is absent. Fedora users need RPM Fusion for ffmpeg with proprietary codecs.
v4.0.2
fix(gitignore): stop excluding app_patches/app from the repository
.gitignore carried unanchored `app/`, `build/` and `dist/` rules. Git
matches those at any depth, so alongside the intended top-level artefact
directories they also excluded:
app_patches/app/app.bundle.js
app_patches/app/js/debug-reporter.js
app_patches/app/js/directives/welcome-page.js
app_patches/app/js/lib/api/screen-capture.js
app_patches/node_modules/{jsbi,long}/dist/
app_patches/node_modules/nsfw/build/
ensure-extracted-app.sh applies app_patches with `cp -r app_patches/. app/`,
so any build from a clean checkout silently skipped every one of them. CI
builds only ever saw app_patches/my_modules and app_patches/node_modules,
which means the published packages shipped upstream's Windows
screen-capture.js rather than the XDG portal implementation, and the
unpatched app.bundle.js.
Anchor the three rules to the repository root. The top-level app/, build/
and dist/ payload directories stay ignored exactly as before; only the
nested paths under app_patches/ become visible. Verified both halves of
that with git check-ignore.
Co-Authored-By: Claude <noreply@anthropic.com>