Anonymous
6/20/2025, 6:31:22 AM
No.105647940
>>105647593
I've not tried with bottles, but i've done this with other flatpaks
# list the flatpaks installed on your system and look up for the bottles' one is gonna be a gay ass long namespace string, use less, a pipe, whatever, to find it it
flatpak list
# very likely is com.usebottles.bottles
# Then just run that over a terminal. Alternatively you can just write the stdout/err to a file of your liking
# flatpak run [whatever gay namespace] > /tmp/file-can-be-anywhere-really.txt 2>&1 -b &
# last bit will also catch most error messages, even the irrelevant ones, and fork the process so it frees the control of your shell
I've not tried with bottles, but i've done this with other flatpaks
# list the flatpaks installed on your system and look up for the bottles' one is gonna be a gay ass long namespace string, use less, a pipe, whatever, to find it it
flatpak list
# very likely is com.usebottles.bottles
# Then just run that over a terminal. Alternatively you can just write the stdout/err to a file of your liking
# flatpak run [whatever gay namespace] > /tmp/file-can-be-anywhere-really.txt 2>&1 -b &
# last bit will also catch most error messages, even the irrelevant ones, and fork the process so it frees the control of your shell