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
My launched application behaves differently depending on whether it's started from the bottles GUI or with bottles-cli.
I'm trying to setup media keys for foobar2000, running in a bottle. I encountered two different issues, not sure whether they are connected.
When starting from the GUI, and I execute flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000" --args "/playpause", playback starts (as expected), but the Bottles window closes. Further invocations of playpause work as expected - playback pauses or starts.
When starting from a terminal with flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000", the application opens fine. But when running flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000" --args "/playpause", playback starts for ~half a second, then the application closes.
This is problematic, since this is how the desktop file works.
Using shell instead of run, e.g. flatpak run --command=bottles-cli com.usebottles.bottles shell --input "c:\\\Program\\ Files\\\foobar2000\\\foobar2000.exe /playpause" -b "Foobar2000" behaves exactly the same.
To Reproduce
For the Bottles window closing:
Create a new bottle and install foobar2000 in it, and add it as a program
Start bottles with flatpak run com.usebottles.bottles
In the bottle, start foobar2000
Run flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000" --args "/playpause"
For the foobar2000 window closing:
Create a new bottle and install foobar2000 in it, and add it as a program
Start foobar2000 with flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000"
Run flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000" --args "/playpause"
Describe the bug
My launched application behaves differently depending on whether it's started from the bottles GUI or with
bottles-cli
.I'm trying to setup media keys for foobar2000, running in a bottle. I encountered two different issues, not sure whether they are connected.
When starting from the GUI, and I execute
flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000" --args "/playpause"
, playback starts (as expected), but the Bottles window closes. Further invocations of playpause work as expected - playback pauses or starts.When starting from a terminal with
flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000"
, the application opens fine. But when runningflatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000" --args "/playpause"
, playback starts for ~half a second, then the application closes.This is problematic, since this is how the desktop file works.
Using
shell
instead ofrun
, e.g.flatpak run --command=bottles-cli com.usebottles.bottles shell --input "c:\\\Program\\ Files\\\foobar2000\\\foobar2000.exe /playpause" -b "Foobar2000"
behaves exactly the same.To Reproduce
For the Bottles window closing:
flatpak run com.usebottles.bottles
flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000" --args "/playpause"
For the foobar2000 window closing:
flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000"
flatpak run --command=bottles-cli com.usebottles.bottles run --args-replace -p Foobar2000 -b "Foobar2000" --args "/playpause"
Package
Flatpak from Flathub
Distribution
Debian 12.5
Debugging Information
Troubleshooting Logs
Additional context
Running flatpak with
-vv
shows no suspicious entries, there is no output after bottles is started.The text was updated successfully, but these errors were encountered: