Software 44674 Published by

Mirko Brombin just pushed Bottles 65.4, a single-commit hotfix that restores bottle creation after the 65.0 update broke the flow for users with hybrid Wine and Proton templates. The regression, reported on August 6, blocked anyone trying to set up a new prefix and forced a rollback to version 64.1. The patch simply flips a logic inversion in wine.py and downgrades the accompanying log message from an error to a warning, allowing existing templates to initialize normally without touching your current installations. You can grab the update from Flathub now, with the full diff and issue tracker linked directly from the release page.



Bottles 65.4 drops as a same-day hotfix for the broken bottle-creation regression

The open-source Wine wrapper returns to Flathub after a logic inversion and error downgrade fix the core feature that broke in 65.0.

Mirko Brombin just pushed Bottles 65.4, a single-commit release that undoes a regression which completely stopped users from creating new bottles since the 65.0 update. The patch landed on August 6, 2026, roughly the same hour a user filed issue #4639 detailing the exact problem.

Managing Wine prefixes has historically been a game of Russian roulette. You edit a registry key wrong, drop a DLL in the wrong folder, or forget to disable a sandbox, and suddenly your game borks. That's exactly why tools like Bottles exist in the first place. And when the core setup flow breaks, the whole ecosystem feels a little less friendly.

The bug was straightforward to reproduce. Click the plus button, pick a runner, hit create, and the interface returned a hard failure. The logs showed a clear culprit: the application refused to create a shared Wine and Proton user profile, then aborted entirely. Users trying to set up bottles from templates that already bundled both environments had no choice but to roll back to version 64.1.

Screenshot_from_2026_02_16_13_28_27

The regression and the fix

It boiled down to a single check in bottles/backend/utils/wine.py. When a template already contained both a Wine profile directory and a Proton profile directory, the ensure_user_profile_alias() function treated the coexistence as a fatal error. The original code read something like if len(profile_targets) > 1: return False. The patch flips that condition to return True, then downgrades the accompanying log message from a hard error to a warning in the manager module.

The fix lands in three files. Two are production code changes, and one is a new test case that confirms the behavior. Keep in mind that the underlying logic hasn't changed much. You aren't getting new features or performance tweaks. You're getting a targeted hotfix that restores the one thing everyone actually uses.

It's a rather expensive machine for the internals it is touting, though the design and small form factor do help it somewhat. Wait, that's wrong paragraph. Picking up again: The regression was frustrating, especially for users relying on hybrid templates, but the same-day turnaround speaks to an active maintainer watching the issue tracker. The commit history shows exactly what you'd expect from a focused hotfix. Net change sits at +17 lines and -7 deletions.

Bottles remains one of the more polished ways to manage Wine prefixes on Linux. The project sits at roughly 8,700 stars on GitHub, ships primarily as a Flatpak from Flathub, and covers everything from pre-configured gaming and app templates to shader compilation and Proton integration. The GPL-3.0 codebase has a steady trickle of community contributions, though Brombin still handles the bulk of the maintenance and release pipeline.

What happens next

You can grab Bottles 65.4 from Flathub starting now. If you were mid-project and had to roll back to 64.1, you're clear to upgrade without losing your existing prefixes. The hotfix only touches the profile aliasing logic, so your current installations remain untouched.

Head here to the 65.4 release tag. The original bug report and the fixing commit are linked directly from the release page if you want to read the full diff.