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
When deleting a bottle that was created on a different directory than default (in my case in a different drive mounted on /mnt), the cache folder located on ~/.var/app/com.usebottles.bottles/data/bottles/bottles/ with the bottles name isn't removed. This causes an error when trying to create a bottle with the same name. Deleting the cache directory manually fixes the issue.
To Reproduce
1.- Create a custom bottle on a different directory than default.
2.- Delete said bottle.
3.- Create a bottle with the same name.
#Bottle deletes without errors
15:19:09 (INFO) Deleted the bottle in: /mnt/hdd/Bottles/Test
#Creating a bottle with the same name shows this error
15:19:54 (ERROR) Failed to create placeholder directory/file at: /home/juan/.var/app/com.usebottles.bottles/data/bottles/bottles/Test
Additional context
File permissions have been setup using flatseal to grant access to mounted drives on /mnt
The text was updated successfully, but these errors were encountered:
mirkobrombin
changed the title
[Bug]: Deleting a bottle created on a different drive doesnt delete cache directories, causing an error when creating another bottle with the same name.
[Bug]: Deleting a bottle created on a different drive doesnt delete cache directories
Dec 8, 2024
Describe the bug
When deleting a bottle that was created on a different directory than default (in my case in a different drive mounted on /mnt), the cache folder located on
~/.var/app/com.usebottles.bottles/data/bottles/bottles/
with the bottles name isn't removed. This causes an error when trying to create a bottle with the same name. Deleting the cache directory manually fixes the issue.To Reproduce
1.- Create a custom bottle on a different directory than default.
2.- Delete said bottle.
3.- Create a bottle with the same name.
Package
Flatpak from Flathub
Distribution
Arch Linux
Debugging Information
Troubleshooting Logs
Additional context
File permissions have been setup using flatseal to grant access to mounted drives on /mnt
The text was updated successfully, but these errors were encountered: