{"id":58,"date":"2025-11-28T15:01:59","date_gmt":"2025-11-28T14:01:59","guid":{"rendered":"https:\/\/linuxundich.de\/en\/?p=58"},"modified":"2026-10-03T21:49:53","modified_gmt":"2026-10-03T19:49:53","slug":"spotify-on-gnome-how-to-fix-the-blue-window-border","status":"publish","type":"post","link":"https:\/\/linuxundich.de\/en\/gnu-linux\/spotify-on-gnome-how-to-fix-the-blue-window-border\/","title":{"rendered":"Spotify on GNOME: How to Fix the Blue Window Border"},"content":{"rendered":"\n

If you use Spotify on Linux with GNOME<\/a>, you may have noticed an ugly blue border around the app window over the last few days. I’m seeing the problem here on my machine under Arch Linux<\/a>, but it should affect all distributions.<\/p>\n\n\n\n

The culprit is an update to the official Electron-based Linux client that messed up the GTK-style window decoration. Spotify<\/a> itself works just as before, but visually it looks anything but nice.<\/p>\n\n\n\n

\"Spotify\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Spotify with a blue border. An update to the Linux client broke the GTK-style window decoration, so the window is framed in an ugly blue and isn’t displayed correctly.<\/figcaption><\/figure>\n\n\n\n

Solutions for Spotify<\/h2>\n\n\n\n

There are two easy ways to fix the problem. The most convenient one is to install Spotify as a Flatpak<\/a>. The Flatpak version doesn’t show the blue frame, and you don’t have to worry about anything. No configuration changes are needed.<\/p>\n\n\n\n

\"The\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
The Flatpak version of Spotify doesn’t show the blue frame. The GTK-style window decoration is rendered correctly, and after installation the window looks normal and error-free.<\/figcaption><\/figure>\n\n\n\n

If you installed Spotify via the Spotify Launcher<\/a> (the spotify-launcher<\/em> package from Arch’s extra repository) or directly from the AUR<\/a> (the spotify<\/em> entry), you need to set the launch flag --ozone-platform=x11<\/code> instead. That makes the GTK decoration show up correctly. Depending on how you installed it, add the flag like this:<\/p>\n\n\n\n

For AUR Spotify<\/strong> in the file ~\/.config\/spotify-flags.conf<\/code>:<\/p>\n\n\n\n

--ozone-platform=x11<\/code><\/pre>\n\n\n\n
For Spotify Launcher<\/strong> in ~\/.config\/spotify-launcher.conf<\/code>:<\/p>\n\n\n\n
&#91;spotify]\nextra_arguments = &#91;"--ozone-platform=x11"]<\/code><\/pre>\n\n\n\n
You may have to create these files first. After restarting Spotify, the blue frame should be gone and everything should look normal again.<\/p>\n\n\n\n
\"The\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
The configuration files under ~\/.config. You may have to create them first. You only need the file that matches your installation method, not both at the same time.<\/figcaption><\/figure>\n\n\n\n
\"Alternatively,\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Alternatively, you can set the flag –ozone-platform=x11 if you installed Spotify from the AUR. The window frame is then displayed correctly and normally again.<\/figcaption><\/figure>\n\n\n\n
Correction from Fabian on Mastodon<\/a>:<\/strong> That’s not quite right. This is solely down to Spotify running natively on Wayland, where under GNOME it needs a client-side decoration (CSD), which it provides through that blue one. Forcing it back to X11 might cause real problems, like blurry fonts, bad (or no) scaling and so on. Also, Spotify isn’t Electron, it’s the Chromium Embedded Framework (CEF).<\/p>\n\n\n\n
Sure, it’s a crutch, but one that helps right now. And you can undo the change quickly, too. The other options would be to run GNOME under X11 or to make friends with the blue frames. To me, neither is exactly ideal. So for now this is a workaround, and of course you shouldn’t forget about it in case Spotify starts acting up again at some point.<\/p>\n","protected":false},"excerpt":{"rendered":"
A blue frame around Spotify on GNOME ruins the look, even though everything still works as it should. On Arch Linux, the fix is easy: either go through Flatpak or use a launch flag for the client from the AUR.<\/p>\n","protected":false},"author":2,"featured_media":57,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"lui_source_id":45241,"lui_source_hash":"46d6fea6688712aad9fe1c729e2d715a81587bcc4d41aee9581d997fea1bd554","lui_source_translated":"2026-10-03","lui_source_reviewed":true,"lui_via_url":"","lui_via_label":"","lui_source_url":"","lui_source_label":"","footnotes":""},"categories":[2],"tags":[],"class_list":["post-58","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-gnu-linux"],"_links":{"self":[{"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/posts\/58","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/comments?post=58"}],"version-history":[{"count":1,"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/posts\/58\/revisions"}],"predecessor-version":[{"id":81,"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/posts\/58\/revisions\/81"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/media\/57"}],"wp:attachment":[{"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/media?parent=58"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/categories?post=58"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxundich.de\/en\/wp-json\/wp\/v2\/tags?post=58"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}