Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pass arguments + flags to spotify executable #6

Closed
tfachmann opened this issue Aug 9, 2022 · 4 comments · Fixed by #7
Closed

Pass arguments + flags to spotify executable #6

tfachmann opened this issue Aug 9, 2022 · 4 comments · Fixed by #7

Comments

@tfachmann
Copy link

Is it possible to send arguments + flags to the spotify executable?

E.g. for wayland support it is necessary to start spotify like this

spotify --enable-features=UseOzonePlatform --ozone-platform=wayland
@kpcyrd
Copy link
Owner

kpcyrd commented Aug 15, 2022

This is now possible in the 0.3.0 release:

$ cat /etc/spotify-launcher.conf 
[spotify]
extra_arguments = ["--enable-features=UseOzonePlatform", "--ozone-platform=wayland"]

@tfachmann
Copy link
Author

Cool, thanks a lot for implementing!!

@D3SOX
Copy link

D3SOX commented Aug 15, 2022

Just out of interest: Why do you need these parameters for Spotify on Wayland? I'm also on Wayland (KDE Plasma) and it works without them.

@tfachmann
Copy link
Author

Is it running natively on wayland, or is there an xwayland session in between?
To test this, you might use the small program called xeyes. If the eyes move when hovering over spotify, it runs on xwayland. If they don't move, it is indeed running natively on wayland.

I'm using a minimal compositor (sway), if it runs natively on KDE, it may be the case that they have special flags / optimizations for apps in the Chromium Embedded Framework I don't know of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants