Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Hi,
Can you release a linux package with ozone support built so that we can use the client under Wayland? There have been posts requesting this in the past because it is highly anticipated.
It shouldn't be that complicated it seems:
https://www.collabora.com/news-and-blog/blog/2019/05/08/cef-on-wayland-upstreamed/
https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/ozone_overview.md
Best,
@iiiian wrote:Thanks !drop down menu and chinese/japanese input work like a charm now!. I also test with
--enable-features=UseOzonePlatform --ozone-platform=wayland
this eliminate blurry app on fractional scaling, but chinese/japanese input will not work, which is understandable since chromium doesn't implement it. Anyway, thanks for the update.
So by default the app will still use xwayland in a wayland environment? Thats a bit sad to read. 😞
Thanks so much to developers working on this. Its very exciting to see 1.1.99 starting to work in Wayland. Right now I'm noting a couple issues that hopefully won't be terrible to resolve. 1) the window border is pretty strange looking. Guessing based on the fact that its still relying on the "--enable-features=UseOzonePlatform --ozone-platform=wayland" flags this means Spotify is running a pretty old version of Electron, but would be great if we could get the newer version that support native Gnome chrome with the flag "--enable-features=WaylandWindowDecorations". Also the app doesn't seem to set a window class so it doesn't show properly on the dock. Thanks again!
Spotify is not Electron, but Chromium Embedded Framework(CEF) and does use a pretty recent version of it: https://www.spotify.com/us/opensource/
I've tested the 1.1.99 version and I would like to report these 3 issues:
Testing environment: Kubuntu 22.10
The drop down menu works normally in XWayland. But when running with `--enable-features=UseOzonePlatform --ozone-platform=wayland`, the menu is still not working, and I cannot even use the keyboards to open it.
I tested the version 1.1.99.878-g1e4ccc6e. It is working like a charm and the things that are not working are the following:
I'm running on a Ubuntu 22.04 machine, with the flags
--enable-features=UseOzonePlatform --ozone-platform=wayland
Running with the flags --enable-features=UseOzonePlatform,WaylandWindowDecoration --ozone-platform=wayland still have the same issues.
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game…