I run Qwen Code Desktop on an ARM64 Linux machine (Ubuntu 24.04, aarch64), and I maintain a small setup script that installs the Desktop app from the release feed.
The current release feed (desktop-latest.json for desktop-v0.24.6) contains builds for:
darwin-aarch64darwin-x86_64linux-x86_64windows-x86_64
but no linux-aarch64. Looking at .github/workflows/desktop-release.yml, the build matrix confirms it — Linux is only built for x86_64-unknown-linux-gnu (appimage, deb).
What I hit: on my ARM64 box there is simply no Desktop artifact to install. My installer previously had no way to tell "no build for my architecture" apart from "no build for Linux at all" — the first run on an aarch64 machine silently downloaded the linux-x86_64 AppImage, which cannot execute without an emulation layer, and the install looked successful until the app failed to start. I now guard on architecture explicitly, which works, but it is a workaround for a missing build rather than a fix.
Request: add an aarch64-unknown-linux-gnu entry to the desktop release matrix (AppImage + deb, same as the x86_64 Linux target). GitHub Actions already offers ARM64 Linux runners (ubuntu-24.04-arm), so this should be a matrix addition plus whatever the existing Linux job steps already do (xvfb smoke, SHA256SUMS, feed update).
If ARM64 Linux is deliberately out of scope, a one-line note on this issue is enough — I will keep my installer's architecture guard and skip Desktop there.
I run Qwen Code Desktop on an ARM64 Linux machine (Ubuntu 24.04, aarch64), and I maintain a small setup script that installs the Desktop app from the release feed.
The current release feed (
desktop-latest.jsonfordesktop-v0.24.6) contains builds for:darwin-aarch64darwin-x86_64linux-x86_64windows-x86_64but no
linux-aarch64. Looking at.github/workflows/desktop-release.yml, the build matrix confirms it — Linux is only built forx86_64-unknown-linux-gnu(appimage, deb).What I hit: on my ARM64 box there is simply no Desktop artifact to install. My installer previously had no way to tell "no build for my architecture" apart from "no build for Linux at all" — the first run on an aarch64 machine silently downloaded the
linux-x86_64AppImage, which cannot execute without an emulation layer, and the install looked successful until the app failed to start. I now guard on architecture explicitly, which works, but it is a workaround for a missing build rather than a fix.Request: add an
aarch64-unknown-linux-gnuentry to the desktop release matrix (AppImage + deb, same as the x86_64 Linux target). GitHub Actions already offers ARM64 Linux runners (ubuntu-24.04-arm), so this should be a matrix addition plus whatever the existing Linux job steps already do (xvfb smoke, SHA256SUMS, feed update).If ARM64 Linux is deliberately out of scope, a one-line note on this issue is enough — I will keep my installer's architecture guard and skip Desktop there.