Motrix v2.0.0-beta.25

v2.0.0-beta.25Pre-release
Added 2
  • AppImages now include native zsync update metadata
  • New Task file-type filters now show consistent tooltips
Changed 10
  • BitTorrent payloads now use a fixed-length internal staging workspace with validated per-file output mappings
  • Final names are restored after BitTorrent completion, and failed Magnet metadata resolution can be retried safely with a fresh engine task
  • Magnet-to-BT conversion immediately persists aria2's authoritative file paths, sizes, and selection state
  • Domain file indexes consistently remain zero-based, including restore and reseed paths
  • Re-adding the same torrent now compares its info hash, destination, and file selection
  • Motrix reuses or focuses a compatible task and verifies completed data before reuse
Fixed 3
  • Internal staging path no longer leaks a bare aria2 GID
  • Activity heatmap omits a partial leading month label when it would overlap the next month
  • AppImage desktop entry now correctly references motrix.desktop instead of app.motrix.native.desktop

From Motrix

Motrix 2.0.0-beta.25

English | 简体中文

Motrix 2.0.0-beta.25 strengthens BitTorrent and Magnet task identity, recovery, and storage safety; modernizes AppImage distribution; and refines several desktop controls. It is intended for public distribution only after every protected release gate passes.

Beta.24 did not reach public distribution because the protected Linux smoke test looked for the AppStream application ID (app.motrix.native.desktop) instead of electron-builder's actual AppImage desktop entry (motrix.desktop). Beta.25 carries the same user-facing changes and corrects that release-only assertion; both AppImage architectures must still pass the complete no-FUSE extraction gate before publication.

Highlights
  • BitTorrent payloads now use a fixed-length internal staging workspace with validated per-file output mappings. Final names are restored after completion, and failed Magnet metadata resolution can be retried safely with a fresh engine task (#1930, #1932).
  • Magnet-to-BT conversion immediately persists aria2's authoritative file paths, sizes, and selection state. Domain file indexes consistently remain zero-based, including restore and reseed paths (#1934, #1937).
  • Re-adding the same torrent now compares its info hash, destination, and file selection. Motrix reuses or focuses a compatible task, verifies completed data before reuse, and reports explicit conflicts for incompatible copies or leftover files instead of silently downloading a numbered duplicate. The internal staging path no longer leaks a bare aria2 GID (#1939).
  • AppImages now use static x64 and arm64 runtimes, include native zsync update metadata, and support extraction on current Linux systems without depending on FUSE 2 (#1898, #1899, #1933).
  • Windows caption controls use compact Chromium-inspired glyphs and stay in sync when the window is maximized, restored, or resized (#1925, #1935).
  • The activity heatmap omits a partial leading month label when it would overlap the next month (#1936, #1938).
  • New Task file-type filters now show consistent tooltips (#1939).
Before testing

This is prerelease software. Back up existing Motrix application data and downloads before installing it. Migration from Motrix v1 data has not yet been validated, so do not use your only copy of v1 data with this beta.

When practical, test v2 in parallel using a separate OS account, machine, or Docker data directory. Do not rely on this beta for your only copy of important downloads.

For BitTorrent testing, add the same Magnet link more than once with matching and different destinations or file selections. Confirm that compatible tasks are reused, incompatible copies require an explicit choice, and completed data is checked before reuse. Historical tasks with empty file metadata can only be repaired while aria2 still retains their result; otherwise remove the old task and re-add the Magnet link. On Linux, also verify AppImage extraction, desktop integration, and update checks on the architectures you use.

Planned downloads after release gates pass
DistributionArchitecturesPlanned output
macOS 12 or laterarm64 (Apple Silicon), x64 (Intel)DMG and ZIP
Windowsx64Unsigned NSIS installer (.exe) and ZIP
Linuxx64, arm64AppImage, DEB, and RPM
Flatpak Native Host companionlinux/x64, linux/arm64Motrix-Native-Host-2.0.0-beta.25-linux-<arch>.tar.gz
Docker Hub / GHCRlinux/amd64, linux/arm64Immutable 2.0.0-beta.25 tag in both registries
Snap StoreNot published for this beta

After every container gate passes, the versioned image references will be docker.io/motrixapp/motrix-server:2.0.0-beta.25 and ghcr.io/agalwood/motrix-server:2.0.0-beta.25. See the Docker Server deployment guide for storage, networking, and upgrade guidance.

Distribution notes
  • AppImage desktop integration is opt-in and confined to the current user's XDG data directory. Browser-extension hand-off is not yet available from the AppImage package because its Native Messaging host does not have a stable path outside the mounted image.
  • Flatpak is validated separately and is not published by the release tag; the GitHub prerelease includes its Native Host companion archives.
  • Windows arm64 and all 32-bit packages are not available.
  • Windows packages are unsigned and may trigger a Windows SmartScreen warning. Download them only from the official GitHub prerelease after it is published.
  • Beta container tags are immutable and do not update latest, stable, or other stable floating tags.
  • Snap is not published for this beta. Prerelease Snap runs stop after source validation, so they do not build Snap artifacts, upload Store revisions, or change latest/edge.
Feedback

Please report reproducible problems through GitHub Issues. Include your operating system, architecture, package type, and the steps needed to reproduce the issue.

What's Changed
New Contributors

Full Changelog: https://github.com/agalwood/Motrix/compare/v2.0.0-beta.23...v2.0.0-beta.25

View original

Upgraded? How did it go?

Discussion