App is not opening since 2-3 weeks

[hrishikeshsathyan1947]

Spotify is not at all opening

[Erick555]

Guessing in the dark, you may try removing ~/.var/app/com.spotify.Client/cache but it's hard to help without any details.

[Santiago3301]

There's no more details to be given. You click the app, it doesn't open, simple as that.

[Erick555]

When I click the app it opens and starts playing music :)

If above solution doesn't work then I can't help.

[Santiago3301]

Fixed it doing this

Actually you said there that those things are enabled by default. I thing i disabled them to solve the weird Windows XP looking top bar. Now it works and even has the Gnome "default" GTK top bar.

[Erick555]

yeah, if you tweak something then it could backfire at some point when you forget about it.

[fhera]

I found the root cause on my machine, and it's a Flatpak permission override — not the runtime. This is actually the same thing as #317 (the "Windows XP looking" title bar), just with the opposite symptom.

I had disabled the Wayland socket for this app in Flatseal (sockets=!wayland) to work around the ugly Chromium title bar (issue #317). On a Wayland session, that alone makes Spotify's Chromium die silently (exit code 0, no window, no error in the launcher or journal): the app still sees XDG_SESSION_TYPE=wayland and tries to connect to a Wayland socket that no longer exists.

The fix is the official workaround from #317 (by @Erick555):

$ flatpak override --user --unset-env=XDG_SESSION_TYPE --socket=x11 --nosocket=wayland com.spotify.Client

This disables the Wayland socket and unsets XDG_SESSION_TYPE (so Chromium properly falls back to X11) and explicitly enables the X11 socket. Spotify now runs via XWayland (--ozone-platform=x11), opens normally, and — as a bonus — GNOME draws the proper themed title bar, so the ugly Chromium bar is gone too.

If you're affected, check your overrides first:

$ flatpak override --user --show com.spotify.Client

If you see sockets=!wayland (or any display-related permission disabled in Flatseal), that's very likely the culprit. Note that just disabling the Wayland socket (without enabling the X11 socket and unsetting XDG_SESSION_TYPE) is exactly what makes the app fail to open at all — which matches what several people in this thread reported.