Bottles 66.1 patches two critical regressions from the major v66.0 release
Open-source Windows compatibility layer manager Bottles dropped version 66.1 just hours after its v66.0 launch. The reason is straightforward: 66.0 broke game launching and crashed a brand new feature. Lead developer Mirko Brombin just pushed an emergency patch, closing both reported issues before most users finished their morning routines.
Bottles has built a solid following on Linux, sitting at 8.7k GitHub stars and a loyal Flatpak user base. Version 66 marked a serious pivot toward gaming. The changelog promised native UMU launcher support, ProtoSoda as the default runner for UMU prefixes, an Adaptive Launch performance tweak for Soda 11.0-5, and an experimental cpak package. It was a big update for a project that typically runs on a single maintainer with community contributors.
The regressions
Shipping that much at once meant things slipped through. The first problem, tracked as issue #4675, was a path resolution bug inside Flatpak. Bottles expected Wine runners at system-level paths like /var/data/bottles/runners/soda-11.0-5/bin/wine, but Flatpak sandboxes route everything through ~/.var/app/com.usebottles.bottles/data/.... Games simply refused to launch. Brombin updated the _get_wine_compatible_base() function in bottles/backend/globals.py to leave Flatpak-specific paths untouched. The production code change added three lines.
The second issue hit users trying to manually add games with custom UMU prefixes. Clicking the button to browse for an existing executable produced a Python AttributeError instead of a file picker. The culprit was a mismatched method reference in bottles/frontend/windows/umu.py from the UMU integration work in 66.0. A quick rename of the private method reference plus 27 lines of test coverage in commit a14c2c2 cleared the crash. The entire patch sits at two commits above v66.0, touching four files.
It's a rather tight patch for a release that shipped with core functionality broken, though the sub-two-hour turnaround does earn some points. The Flatpak sandbox path issue also highlights a persistent headache for Linux developers: app sandboxes and native filesystem expectations still don't always play nice. At the same time, shipping a gaming-focused update with launch flows broken is a reminder that rapid iteration without a broader testing matrix can bite back.
If you're running the Flatpak version of Bottles, you'll get the update through Flathub automatically. Users tracking the experimental cpak package can pull it directly from cpak.it. The repository sits at 372 forks and uses GPL-3.0, with the full commit history and release notes available on GitHub.
