TheJakeBraun · Oct 26, 2026 · Oct 26, 2026
diff --git a/app/linux/packaging/flatpak-modules/libayatana-appindicator-gtk3.json b/app/linux/packaging/flatpak-modules/libayatana-appindicator-gtk3.json
@@ -6,6 +6,7 @@
         "/lib/pkgconfig"
     ],
     "config-opts": [
+        "-DCMAKE_INSTALL_LIBDIR=lib",
         "-DENABLE_BINDINGS_MONO=NO",
         "-DENABLE_BINDINGS_VALA=NO",
         "-DENABLE_GTKDOC=NO"
@@ -62,6 +63,7 @@
                 "/lib/pkgconfig"
             ],
             "config-opts": [
+                "-DCMAKE_INSTALL_LIBDIR=lib",
                 "-DENABLE_INTROSPECTION=OFF"
             ],
             "sources": [
@@ -92,6 +94,9 @@
                 "/libexec",
                 "/share"
             ],
+            "config-opts": [
+                "-DCMAKE_INSTALL_LIBDIR=lib"
+            ],
             "sources": [
                 {
                     "type": "git",

diff --git a/app/pubspec.yaml b/app/pubspec.yaml
@@ -16,7 +16,7 @@ publish_to: 'none' # Remove this line if you wish to publish to pub.dev
 # https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
 # In Windows, build-name is used as the major, minor, and patch parts
 # of the product and file versions while build-number is used as the build suffix.
-version: 0.30.0+163
+version: 0.30.1+164
 
 environment:
   sdk: ^3.12.0

diff --git a/dev/logs/agent-changelog.md b/dev/logs/agent-changelog.md
@@ -13,6 +13,20 @@ happened": nothing was logged between 2026-07-02 and 2026-07-15, or between 2026
      it is: it used to say ABOVE, which pushed it further down the file with every entry until
      it sat hundreds of lines under the newest one and pointed writers at the wrong place. -->
 
+## [2026-10-26] - v0.30.1: Flatpak tray library builds again (Linux files back)
+
+**Agent:** Claude Code (Claude Opus 5.5)
+**Files Modified:**
+- `app/linux/packaging/flatpak-modules/libayatana-appindicator-gtk3.json` (`-DCMAKE_INSTALL_LIBDIR=lib` on the three CMake modules)
+- `app/pubspec.yaml` (0.30.1+164), `dev/releases/v0.30.1.md`
+
+**Why:** the v0.30.0 release run failed in both Linux jobs at "Build Flatpak": the GNOME SDK's
+CMake installs `ayatana-ido` to `/app/lib64`, so `libayatana-indicator` could not find
+`libayatana-ido3-0.4.pc` (pkg-config searches `/app/lib/pkgconfig`). With the Linux jobs failed,
+v0.30.0 shipped without tarballs, AppImages and Flatpaks, and without the Docker image. The PR never
+ran the Flatpak build: in `linux-runner.yml` that job runs only on a manual dispatch with
+`flatpak: true`. Tags are never moved, so this ships as v0.30.1 (like v0.29.1).
+
 ## [2026-10-26] - Tray review fixes: menu leak, stable click keys, update quit, close dialogs, Arch, APPIMAGE
 
 **Agent:** Claude Code (Claude Opus 5.5), with OpenCode (DeepSeek V4.1 Flash)

diff --git a/dev/releases/v0.30.1.md b/dev/releases/v0.30.1.md
@@ -0,0 +1,19 @@
+# Airclone v0.30.1 — Linux downloads are back
+
+v0.30.0 was released without its Linux files (`airclone-linux-*.tar.gz`, the
+AppImages and the Flatpaks), because the library the new tray icon needs
+didn't build inside the Flatpak. This release fixes that build and brings the
+Linux files back. Nothing else changed, so everything in
+[v0.30.0](https://github.com/GigaionLLC/Airclone/releases/tag/v0.30.0) applies:
+
+- **A tray icon on Windows, macOS and Linux (#54)** that shows what Airclone is
+  doing and lets you pause, resume, set a bandwidth limit, open the window or
+  quit.
+- **Closing the window can keep Airclone running** (Settings → Tray, off by
+  default), so transfers, mounted drives, servers and schedules keep going.
+- **Start Airclone in the tray when you sign in** (Windows installer and
+  portable, macOS 13 and later, Linux AppImage and tarball).
+- Only one Airclone window runs at a time: launching it again brings back the
+  running copy.
+
+Full details: [Keeping Airclone in the tray](../../docs/guide/tray.md).