You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The app has a "Default" bottle directory, but never says what that "Default" directory is.
I made a directory in my $HOME, but bottles wouldn't use it and returned "Failed to create bottles directory."
Running it on CLI shows (ERROR) Failed to create bottle directory: /run/user/1000/doc/db9d965c/Bottles/bottlenamehere
I told it to use $HOME/Bottles/ for the base directory.
It shouldn't be trying to use the /run filesystem.
To Reproduce
Create a new bottle.
Give it a name.
Set bottle directory to directory in $HOME
See failure message.
(ERROR) Failed to create bottle directory: /run/user/1000/doc/db9d965c/Bottles/bottlenamehere
Additional context
Stop downloading things in the background. This gives Microsoft vibes. There is no accounting for what you're doing in the background. Gotta give better user feedback and progress status. Quit being secretive!
The text was updated successfully, but these errors were encountered:
Describe the bug
The app has a "Default" bottle directory, but never says what that "Default" directory is.
I made a directory in my $HOME, but bottles wouldn't use it and returned "Failed to create bottles directory."
Running it on CLI shows
(ERROR) Failed to create bottle directory: /run/user/1000/doc/db9d965c/Bottles/bottlenamehere
I told it to use $HOME/Bottles/ for the base directory.
It shouldn't be trying to use the /run filesystem.
To Reproduce
Create a new bottle.
Give it a name.
Set bottle directory to directory in $HOME
See failure message.
Package
Flatpak from Flathub
Distribution
POP!_OS 22.04 LTS
Debugging Information
Troubleshooting Logs
Additional context
Stop downloading things in the background. This gives Microsoft vibes. There is no accounting for what you're doing in the background. Gotta give better user feedback and progress status. Quit being secretive!
The text was updated successfully, but these errors were encountered: