Software 44727 Published by

Bottles 66.7 has arrived, shipped just three days after 66.6 as a focused maintenance release from lead developer Mirko Brombin. The update resolves a common catalog loading error by retrying repository requests over IPv4 when IPv6 resolution times out on partially configured networks. Additional fixes normalize bottle copy paths to prevent accidental overwrites, ensure the UI refreshes on the main thread after deletion, and expose the UMU data directory to fix Flatpak sandbox crashes on external storage. The 15-file patch cycle continues Bottles' rapid development cadence for Linux users running Windows software via Wine and Proton.



Bottles 66.7 drops: IPv4 fallback, path fixes, and a Flatpak sandbox patch

The open-source Wine/Proton manager rolls out four bug fixes and a CI update, all shipped just three days after 66.6.

Bottles 66.7 is now live. It's a maintenance release from lead developer Mirko Brombin, arriving on August 16, 2026. The changelog is tight: four bug fixes and one CI change touching 15 files. No new features, just real problems being solved.

The highlight is the IPv4 retry fix for repository timeouts. Users on systems with partial IPv6 stacks were seeing a Resolving timed out after 5000 milliseconds error when loading the Components, Dependencies, and Installers lists. Bottles uses pycurl for network requests, and its default DNS strategy prefers IPv6. If your router or ISP doesn't actually route IPv6 traffic properly, the connection would hang until the timeout fired.

Now the app retries over IPv4 when the initial resolution fails. Affects proxy.usebottles.com and raw.githubusercontent.com. The fix landed after user Diukeen reproduced the issue on Debian 13 / LMDE with Cinnamon. Confirmed reproducible from the Flathub package.

Screenshot_from_2026_02_16_13_28_00

Path normalization and UI thread fixes

Creating a copy of an existing bottle now normalizes file paths before comparison. Previous behavior could result in duplicate copies overwriting each other if path separators differed. Failed copy operations now clean up partial data and report errors through Bottles' dialog system instead of leaving orphaned files on disk.

After deleting a bottle, the UI list now refreshes properly. GTK requires UI updates on the main application thread, but the deletion callback was running asynchronously in a worker context. The fix uses GLib.idle_add() to push the refresh onto the GLib main loop.

Flatpak sandbox patch for UMU games

A separate Flatpak manifest update addresses a crash when launching games via Proton-Soda (UMU-Launcher). The error: bwrap: Can't find source path /proc/self/fd/25: No such file or directory. The issue hit users who'd added games from external storage.

The fix exposes the UMU data directory within the Flatpak sandbox. umu-launcher 1.4.4 can now access its SteamRT runtime files at ~/.local/share/umu/steamrt4. It's a minor adjustment, but one that affects anyone running Windows games through the Flatpak package.

Where 66.7 fits in the version timeline

The 66.x series has been moving fast. Bottles 65.0 shipped on August 4 with Soda v11.0-4, 100+ changes, and gaming features. 65.1 dropped hours later as a hotfix for a GameMode initialization crash. 66.6 arrived August 13, fixing bottle deletion in dedicated sandboxes. 66.7 follows three days later, continuing the rapid iteration pattern.

Bottles itself sits at roughly 8.7k GitHub stars, 372 forks, and 6,595+ commits on main. It's written in Python with a GTK4/Libadwaita UI, built via Meson + Flatpak, and distributes through Flathub, the AUR, and cpak.it. Flathub reports around 146,594 monthly downloads.

Keep in mind that this is a maintenance cycle, not a feature drop. The project's cadence suggests active development, with the 66.x series still rolling. If you're running into the IPv6 resolution timeout or UMU launch crashes, updating should clear those up.

Head here to grab it on Flathub, or check the full changelog on GitHub.