Doesn't launch

[Allan-Bruno]

output on terminal launch:
allan@allan-notebook:~$ flatpak run com.spotify.Client allan@allan-notebook:~$ /app/extra/bin/spotify: /usr/lib/x86_64-linux-gnu/libcurl.so.4: no version information available (required by /app/extra/bin/spotify) [spotifywm] attached to spotify /app/extra/share/spotify/spotify: /usr/lib/x86_64-linux-gnu/libcurl.so.4: no version information available (required by /app/extra/share/spotify/spotify) /app/extra/share/spotify/spotify: /usr/lib/x86_64-linux-gnu/libcurl.so.4: no version information available (required by /app/extra/share/spotify/spotify) [spotifywm] attached to spotify [spotifywm] attached to spotify

[TingPing]

None of this is an error. It says spotifywm found an existing window. Maybe it is minimized to the tray?

[jeroen1602]

I have the same problem running Fedora linux 39 with KDE Plasma.

I thought it might be a wayland issue but it also won't launch when running with X11.

I have tried looking through ps aux and top to see if a spotify process was already running but I couldn't find one.

It also happens on a clean boot.

EDIT:

using the version with the commit hash d22ab2f6059cca52bc56754ca1860fb41b0d9c6333975bd8f2eb375fde5a4d84 worked for me by running:

sudo flatpak update --commit=d22ab2f6059cca52bc56754ca1860fb41b0d9c6333975bd8f2eb375fde5a4d84 com.spotify.Client

[Erick555]

Maybe try disabling gpu cache.

[jeroen1602]

First I updated again to the latest stable version with hash: b23c35bae652b4975189aa2f80fde9b52fa6356959f6562bebf0692eb1892bf1

I tried creating the config file and disabling GPU cache. But no dice, it's still not launching.

I also tried running flatpak run --command="bash" com.spotify.Client and then run spotify --disable-gpu-shader-disk-cache --show-console in the new bash instance. But that also didn't work.

[TingPing]

FWIW I tried reverting recent commits and it was still broken. Also disabling spotifywm didn't change anything.

[Allan-Bruno]

None of this is an error. It found an existing window. Maybe it is minimized to the tray?

when I made the launch there were none processes of spotify, when launched, the process was created and stayed still for a minute, after that it killed itself

[Razer0123]

Same issue, i'm unable to run Spotify

[ErikMekiassen]

@jeroen1602 running
sudo flatpak update --commit=d22ab2f6059cca52bc56754ca1860fb41b0d9c6333975bd8f2eb375fde5a4d84 com.spotify.Client
worked for me as well

[gurnben]

@jeroen1602 running sudo flatpak update --commit=d22ab2f6059cca52bc56754ca1860fb41b0d9c6333975bd8f2eb375fde5a4d84 com.spotify.Client worked for me as well

Kudos - this worked for me as well - hopefully a zero-intervention fix is out soon

[Erick555]

There isn't a single error message posted so there isn't a starting point to make a fix.

At first it would be nice to generalize on what kind of systems this happens and see what they have in common that triggers the issue (I have no issue myself) - everyone commenting should post at least distro version, desktop environment version and gpu version.

[ErikMekiassen]

Good point!
Fedora 38
gnome 44
Wayland (not sure if thats self explanitory)
gpu: amd 6800xt

[Allan-Bruno]

Pop!_OS 22.04
Gnome 42.5
Xorg
HD graphics 520

[Allan-Bruno]

@jeroen1602 running sudo flatpak update --commit=d22ab2f6059cca52bc56754ca1860fb41b0d9c6333975bd8f2eb375fde5a4d84 com.spotify.Client worked for me as well

for some reason it appers
erro: com.spotify.Client not installed

checked if the source was wrong

allan@allan-notebook:~$ flatpak install flathub com.spotify.Client Looking for matches… Ignoring: com.spotify.Client/x86_64/stable is already installed

idk what happens here

[ErikMekiassen]

@Allan-Bruno i got the same problem when i had to re update the commit but it promted me to install it and then it worked again. not sure what flatpak update does exactly but i think its a flatpack problem

[Allan-Bruno]

@Allan-Bruno i got the same problem when i had to re update the commit but it promted me to install it and then it worked again. not sure what flatpak update does exactly but i think its a flatpack problem

how exactly you made it?

[ErikMekiassen]

Im not 100% sure but it happened after restart. spotify is the first thing i opened after firefox. i stil have the spotify icon but nothing happened. i ran flatpack run com.spotify.Client or something to get the prompt

[danielepusceddu]

There isn't a single error message posted so there isn't a starting point to make a fix.

At first it would be nice to generalize on what kind of systems this happens and see what they have in common that triggers the issue (I have no issue myself) - everyone commenting should post at least distro version, desktop environment version and gpu version.

Fedora 39, Wayland Gnome 45.5, Intel UHD Graphics 620

[ErikMekiassen]

i do have an igpu in my intel i9 12900k so i might have similar drivers to @Allan-Bruno @danielepusceddu

[ErikMekiassen]

running
flatpak run com.spotify.Client
now gives this after restart (i updated to latest commit before the restart but it forgets it each time i reboot):
/app/extra/bin/spotify: /usr/lib/x86_64-linux-gnu/libcurl.so.4: no version information available (required by /app/extra/bin/spotify)
[emvit@10-13-37-63 ~]$ [spotifywm] attached to spotify
/app/extra/share/spotify/spotify: /usr/lib/x86_64-linux-gnu/libcurl.so.4: no version information available (required by /app/extra/share/spotify/spotify)
/app/extra/share/spotify/spotify: /usr/lib/x86_64-linux-gnu/libcurl.so.4: no version information available (required by /app/extra/share/spotify/spotify)
[spotifywm] attached to spotify
[spotifywm] attached to spotify

[Erick555]

All of those messages are fine.

[Dazzle995]

@jeroen1602 running sudo flatpak update --commit=d22ab2f6059cca52bc56754ca1860fb41b0d9c6333975bd8f2eb375fde5a4d84 com.spotify.Client worked for me as well

for some reason it appers erro: com.spotify.Client not installed

checked if the source was wrong

allan@allan-notebook:~$ flatpak install flathub com.spotify.Client Looking for matches… Ignoring: com.spotify.Client/x86_64/stable is already installed

idk what happens here

I had to run the command without sudo, as spotify was installed in user and not system space (I guess)

[stefanfisk]

I was just affected by this as well after restarting my computer. flatpak update --commit=d22ab2f6059cca52bc56754ca1860fb41b0d9c6333975bd8f2eb375fde5a4d84 com.spotify.Client worked.

Pop!_OS 22.04 LTS
GNOME 42.9
Xorg
AMD RX580

[jeroen1602]

I might have found a clue.

I first launched a development shell inside of flatpak using flatpak run --command=bash --devel com.spotify.Client

I then ran the spotify binary (inside the flatpak) using strace strace /app/extra/bin/spotify.

In the output of strace I noticed that it would quit right after a call to readLink with the file /home/jeroen/.var/app/com.spotify.Client/cache/spotify/SingletonSocket.

Trying to read this symbolic link using file /home/jeroen/.var/app/com.spotify.Client/cache/spotify/SingletonSocket said it was a broken link.

After that I removed all the cache using rm -rf /home/jeroen/.var/app/com.spotify.Client/cache/ after that I could start Spotify normally.

TL;DR

Removing the cache of spotify seemed to work. Which can be found at ~/.var/app/com.spotify.Client/cache/

[stefanfisk]

Updating com.spotify.Client made it stop launching again. But rm -rf ~/.var/app/com.spotify.Client/cache/ made it work!

[agriffit79]

rm -rf ~/.var/app/com.spotify.Client/cache fixes for me also.

[Allan-Bruno]

rm -rf ~/.var/app/com.spotify.Client/cache worked for me too, idk if the devs are seeing this issue, so I'll let it open until then, but in case anyone need help on this, just use the command

[pavelzherdin]

I stumbled on the same issue. OpenSUSE Tumbleweed, gnome 46, Radeon 6950.

Removing the cache folder helped. I put aside the broken folder, but it's 3.1g.

I tried to figure out what exactly had to be removed, and in my case there were 3 broken links in
.var/com.spotify.Client/cache/spotify
Removing only those made it start again. They looked like this

lrwxrwxrwx   1 username username   20 Apr  6 21:27 SingletonCookie -> 15038546741398103137
lrwxrwxrwx   1 username username   23 Apr  6 21:27 SingletonLock -> localhost.localdomain-6
lrwxrwxrwx   1 username username   50 Apr  6 21:27 SingletonSocket -> /tmp/.org.chromium.Chromium.RtiORB/SingletonSocket

[Erick555]

Did you check they were invalid inside sandbox?

[pavelzherdin]

Did you check they were invalid inside sandbox?

They are. 15038546741398103137 doesn't exist either way.

[Razer0123]

When will the fix be released? i still have the issue

[Erick555]

Never because it's local file corruption. Just read what do to above.

[pavelzherdin]

Did you check they were invalid inside sandbox?

To add to this, it looks like the client creates those files on start and some of them are bad links intentionally. For me, it's enough to remove SingletonLock only for the app to start.
In the bad cache
SingletonLock -> localhost.localdomain-6
In the working cache
SingletonLock -> DESKTOP-MEQFCF4-6

I experimented a bit by creating that file myself with different targets, some of them indeed prevent the client from starting. Going to stop now, this rabbit hole is too deep for me.

[cch264]

Haven't been able to use Spotify in weeks. Updates did not fix the issue nor did uninstalling and reinstalling as user or system wide. The only solution was the fix above. Thank you!!!

[axelsimon]

Never because it's local file corruption. Just read what do to above.

That's a bit rough on regular users, don't you think?

In practice, this means you are using Spotify desktop normally and then it just stops working. You did nothing wrong, it just stops working. This is the sort of stuff that makes people think "the computer has a mind of its own".

I think we need to do better at making things work for users. Can't we detect this situation and then delete the cache automatically?
Because the alternative is to rely on the users:

1. knowing they can run the app from the CLI,
2. doing so and seeing the error message
3. searching for it
4. finding this thread and finally
5. manually running rm -rf ~/.var/app/com.spotify.Client/cache/

[Erick555]

Can't we detect this situation and then delete the cache automatically?

That would require understanding what is happening.

[axelsimon]

Fair point.
A pgrep -af spotify however returns nothing, which is telling. But yeah, it could be considered to be a bit brutal to delete the cache just because a pgrep returns nothing.

[Erick555]

I see that spotify creates those three Singleton* symlinks on startup and removes them on exit so maybe failing to remove them causes the issue on next startup when there are the old ones. rm ~/.var/app/com.spotify.Client/cache/spotify/Singleton* in pre startup may help then.

[SamuelWAnderson45]

rm ~/.var/app/com.spotify.Client/cache/spotify/Singleton*

Deleting just those singleton files fixes it for me

[nutuxedo]

@jeroen1602 running sudo flatpak update --commit=d22ab2f6059cca52bc56754ca1860fb41b0d9c6333975bd8f2eb375fde5a4d84 com.spotify.Client worked for me as well

this works for me, thanks!

[Razer0123]

Surprised this has not been fixed yet

[sagbobbit]

FWIW, I've got the same issue with the same "solution." openSUSE Tumbleweed + XFCE.

[RoyaltyInTraining]

Same here on Fedora 40. The issue returns every time after wiping the app's data. Sometimes within a week, other times within a day.

[e455a81e-d3ba-41a2-bc6d-7aafb1d9a5cd]

I just encountered this issue as well on Fedora Kinoite 40.20240506.0 with Spotify Version 1.2.31.1205.g4d59ad7c.
Could this issue be related to forced closings of the Spotify application? When I rebooted today KDE asked me whether I wanted to logout the session even if some apps are still running. This could have resulted in a race condition that might have prevented Spotify from cleaning up the files in ~/.var/app/com.spotify.Client/cache/spotify/.

[Erick555]

I tested it by killing spotify process - old Singleton* symlinks were left but I started spotify without issues. Perhaps some systems are cursed.

[e455a81e-d3ba-41a2-bc6d-7aafb1d9a5cd]

I tried to reproduce it as well with a reboot between killing the spotify process unfortunately I hadn't had any success. I also looked at the chromium code that handles these singleton files and attempted to mess with the Singleton symlinks to get it to break, but it just works no matter how hard I try to break it.