-
Notifications
You must be signed in to change notification settings - Fork 35
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
(at least) opt-in for wayland support #275
Comments
I second this, on my Arch Linux machine, spotify running under XWayland takes 800MB - 1GB of memory, that is too much for a music player..... but I've had experiences where native wayland version of some apps consumed way less memory than Xwayland versions. |
Note that everyone can opt-in already by adding relevant flags in config |
True! Didn't even notice it until you mentioned it lol. The biggest gripe for me is that in my multi-monitor setup, I'm forced to use fractional scaling which means blurry text on XWayland. I'm running GNOME 45 on Fedora 39 Workstation |
I haven't been able to get Wayland to work. What command were you using? This command wouldn't open any window: This command would hang up my desktop environment (GNOME 45 on Wayland): For reference, I'm running version the latest version as of writing (version 1.2.31) on FlatHub and the Spotify snap version works besides improperly styled window decoration. |
To match what discord does (and what this issue proposes) try:
|
Hi, @justin13888 's answer is correct and this below produces no window.
but as @Erick555 's answer produces a window that is still running in XWayland, here is the output:
can anybody tell what I'm doing wrong here..?! |
You may try to force wayland by: |
None of the solutions on this page worked for me. I guess the Flatpak version doesn't support Wayland in a stable way yet. I ended up installing spotify AUR Package (not spotify-launcher). and it launches in native wayland beautifully with command: Also, it's resource usage is way less than Flatpak version too. @justin13888 . Around 300MB as compared to 700MB-1.5GB of Flatpak version. |
You may note Flatpak has exact same spotify versions as AUR and snap. |
here is a fix for cursor scaling on wayland, for those who have HIDPI screen |
I used this and it works for me
... not sure if all of these are needed, anyway : |
Interesting. I didn't notice how much RAM it's using until you mentioned! |
Thanks! I could confirm this also works on my system (Fedora 39, with MESA AMD drivers) |
Does anyone have cursor issues with this? I don't mean the cursor theme missing, I mean the cursor not clicking where you think it should be. It seems to be off by quite a lot, resulting in completely different UI elements being activated that aren't under the cursor. |
I have the same issue, I commented in #239, but maybe this thread is more relevant to it. |
About the second command, setting platform hint to auto doesn't guarantee that Ozone uses Wayland. I got it working on Fedora 39 Workstation as mentioned previously but the other problem is that the client-side window decoration on Spotify is hidious. On GNOME, since server side decoration has been rejected, the only solution that would work on GNOME/Mutter would be for Spotify devs to add back a GTK decoration (or perhaps it could be possible to modify the community's Flatpak version?) |
Done in 5248553 |
On Wayland the application controls the cursor. It is using the wrong size, probably nothing we can do about it. |
follow up on previous discussion in issue #239 (comment), I'm suggesting the addition of Wayland support.
Enabling Wayland support, even optionally, would significantly enhance the user experience, especially for NVIDIA users who currently experience xwayland flickering and it would lead to a smoother and more stable performance overall.
I did notice a minor issue with the display of generic Wayland icons, but I believe this can be addressed
The text was updated successfully, but these errors were encountered: