Hello. This is a long shot, but I installed openSUSE Slowroll over Tumbleweed yesterday and everything went great. However, now I’m no longer able to create new bottles with Bottles. Bottles is installed from Flathub. Any way I try to create a new bottle it immediately fails with:

(ERROR) Failed to initialize the Wine prefix. Command exited with status 1.

I tried downgrading Bottles and the results were much the same with the versions I tried, except the error message was:

(ERROR) Wine prefix initialization failed.

This is frustrating because there’s not much to go on. The process does create some folders on the SDD I’m using for my bottles, so I don’t think it’s a permission issue. I have used Flatseal to give proper access. The default bottle folder has the same result anyway. I never had this issue on my previous installation and Bottles worked fine.

Bottles issue tracker has the bug #4919 which I assume is the same problem I have, except I’m completely unable to create a bottle no matter which settings I try.

If anyone has any ideas I could try it would be welcome. I’d prefer using Bottles for my Wine needs.

EDIT: I have solved this issue for now. The problem is apparently related to SELinux on openSUSE. Installing selinux-policy-targeted-gaming with zypper lets me at least create bottles. Thanks for your comments!

  • juipeltje@lemmy.world
    2·
    2 hours ago

    Not very helpful but for what it’s worth i had issues with bottles lately too. Don’t know if it’s the same issue, but when i tried to do pretty much anything with it it would fail. When i ran it in the terminal it seemed to be caused by bottles trying to download some dependencies in the background, but they all failed to download. I couldn’t find recent issues about it and couldn’t find a fix, so i ended up using heroic instead. This was on the latest flatpak at the time.

  • TallonMetroid@lemmy.worldEnglish
    2·
    2 hours ago

    If you did this by changing the Bottles directory in the settings, try reverting that and instead replacing the directory itself (ie ~/.var/app/com.usebottles.bottles/data/bottles) with a symlink to your second drive. That was what worked for me.