Skip to content

v0.6.16 round: #88 #87 #85 #84 #83 #82 #54 #86, Flatpak updater, aarch64/x86_64 builds - #89

Merged
karem505 merged 13 commits into
masterfrom
fix/round-0.6.16
Nov 13, 2026
Merged

karem505 merged 13 commits into
masterfrom
fix/round-0.6.16

Conversation

@karem505

Copy link
Copy Markdown
Owner

One round for v0.6.16: every open issue that can be fixed in code, plus release builds for x86_64 and aarch64 on every OS.

Fixes

Release builds

release.yml adds Linux aarch64 (AppImage + deb), macOS x86_64, Windows ARM64 (NSIS; MSI can't target ARM64), and the publish step now requires them.

Checked locally (Arch, x86_64)

  • cargo fmt --check, cargo clippy --all-targets -D warnings, cargo test (251 passed), all node tests.
  • Unacceptable TLS certificate #84: v0.6.15 AppImage with Debian's CA file hidden (as on openSUSE) never loads WhatsApp; the stripped image loads it with the system GnuTLS; forcing the bundled copy fails again.
  • whatsapp banner  #83: Chrome with a Windows UA: the QR screen's "Download WhatsApp for Windows / Get the app" prompt disappears with the hook, the QR code still loads.
  • Blank window after QR login on Debian 13 (AppImage, old Intel GPU / OpenGL 2.1) #87: dev build with rendering: software starts WhatsApp with LIBGL_ALWAYS_SOFTWARE=1 / WEBKIT_DISABLE_COMPOSITING_MODE=1 in the web process.
  • Flatpak: flatpak-spawn --host works from the sandbox with the new permission, fails with ServiceUnknown without it.

Windows/macOS code (#85, deps) is checked by CI only; #85, #87, #88 need confirmation from the reporters on their hardware.

tao 0.36 (tao#1218) fixed Wayland window decoration handling, including
title-bar buttons that needed a second click after the window came back from
the tray on KDE (tauri#11856).

The tauri 2.12 line moves to webview2-com 0.39 and windows-rs 0.62, so the
direct Windows dependencies follow (windows-future 0.3, tauri-winrt-notification
0.8, notify-rust 4.18 so only one windows-rs version is built). tauri 2.12 needs
Rust 1.90: the Flatpak toolchain moves to 1.91.1 and cargo-sources.json is
regenerated from the new lock.
…or (#87)

On Intel graphics before Sandy Bridge (gen 2-5, e.g. Ironlake) Mesa offers
only OpenGL 2.1. WhatsApp's QR page still draws, but after login the window
stays blank. When every display GPU is one of those (PCI IDs from sysfs),
whatRust now starts WebKit with Mesa's software rasteriser and without
compositing/DMA-BUF. Settings > Rendering > Compatible forces the same on any
GPU (read at startup, applies after a restart). Environment values the user
set are respected.
WhatsApp Web now offers calls to Windows browsers and they connect inside
WebView2 (confirmed on Windows 11 in #86). Linux stays 'no': the FAQ's reasons
(no WebRTC in the AppImage's WebKitGTK, Chrome calling path) are unchanged.
…vated (#85)

After Alt+Tab the top-level window was active but WebView2's child window
was not focused: the composer showed a caret and ignored keys until a click.
On WindowEvent::Focused(true) the account window now calls the controller's
MoveFocus(PROGRAMMATIC); WebView2 restores focus to the element that had it.
…und (#84)

The AppImage bundled Ubuntu's GnuTLS, which looks for CA certificates only at
/etc/ssl/certs/ca-certificates.crt (and a Debian p11-kit module path). openSUSE
and Fedora keep them elsewhere, so every load failed with 'Unacceptable TLS
certificate'; SSL_CERT_FILE is an OpenSSL variable and can't help.

strip-appimage-libs.sh now moves GnuTLS and its private libraries (nettle,
hogweed, tasn1, p11-kit) to usr/lib/gnutls-fallback and adds an AppRun hook
that uses that copy only when the system has no libgnutls.so.30 (or with
WHATRUST_BUNDLED_GNUTLS=1).

Checked on Arch with the v0.6.15 AppImage and Debian's CA file hidden (as on
openSUSE): before, WhatsApp never loaded (bundled GnuTLS in the network
process); after, it loads with the system's GnuTLS. With the file present the
old image loads too, and forcing the bundled copy reproduces the failure.
WhatsApp Web shows 'Get WhatsApp for Windows' (or Mac/Android) prompts, such
as the banner under the chat list, only when WAWebDesktopUpsellUtils reports a
desktop OS with a native app. upsell.js wraps WhatsApp's module definer
(window.__d) before its scripts run and makes that module answer 'no such OS',
as it does on Linux, where no prompt is shown. Other modules are untouched; if
WhatsApp renames the module the hook does nothing.

On by default, as requested in the issue; Settings > Appearance > 'Hide
WhatsApp app promotions' turns it off (applies after a restart). Checked in
Chrome with a Windows user agent: the QR screen's 'Download WhatsApp for
Windows / Get the app' prompt is gone with the hook and the QR code still
loads.
…and version (#82)

- Account rows get padding on all sides so the photo and the menu button sit
  inside the hover highlight; a letter avatar stays visible on hover.
- The privacy blur panel used ui-rounded first, which Chromium on Windows
  resolves to a serif face; it now uses the Settings font stack.
- About whatRust: info icon instead of the reload icon, rounded on all corners
  (the separator moved above the item), and the installed version under it.
… Windows (#54)

With several accounts in separate windows, each account window (and an
account detached from the single window) now carries that account's profile
photo as its window icon, so the taskbar and Alt+Tab tell them apart. Without
a photo it keeps the app icon (default or custom). Setting or removing a photo
updates the open window at once. macOS has no per-window icons, so the Dock
icon stays app-wide there.
…ning the bundle

The Flatpak update button saved the verified bundle and handed it to the
software centre; some (Shelly, for one) only showed it, and whatRust still
logged the update as installed. The bundle is now installed with
'flatpak-spawn --host flatpak install --user|--system --reinstall' (the
installation read from /.flatpak-info), and Restart starts the new version on
the host with 'flatpak run'. If the install command fails the bundle stays in
Downloads and the message gives the exact command; if it can't run, the bundle
is opened as before. The log now says 'installed' only for an applied update.

The manifest gains --talk-name=org.freedesktop.Flatpak, which flatpak-spawn
--host needs (checked: with it, a host 'flatpak info' runs from the sandbox;
without it, ServiceUnknown).
Adds Linux aarch64 (AppImage, deb on ubuntu-22.04-arm), macOS x86_64
(--target x86_64-apple-darwin on macos-latest) and Windows ARM64 (NSIS only,
--target aarch64-pc-windows-msvc: WiX/MSI cannot target ARM64). The AppImage
step uses the appimagetool of the runner's architecture, and publishing now
refuses a release that lacks any of the new bundles. The updater already picks
_aarch64 AppImages, _arm64 debs and setups, and _x64 dmg/app.tar.gz by name.
Releases now carry an aarch64 AppImage next to the amd64 one; the script took
whichever came first.
@karem505
karem505 merged commit f584fa4 into master Nov 13, 2026
14 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant