Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Something went wrong - Try reloading page

Something went wrong - Try reloading page

Plan

Premium

Country

 

Device

Dell XPS13

Operating System

Linux Mint 20.2

 

My Question or Issue

Spotify won't start up - I just get a message Something went wrong - Try reloading page. I can use Spotify fine on my Android phone.

I seem to get the following errors in the console

 

17:59:18.060 D [connect:180 ] ConnectState::updateCluster: delaying cluster update 200ms
17:59:18.064 D [connect:180 ] ConnectState::updateCluster: delaying cluster update 200ms
17:59:18.264 D [connect:192 ] ConnectState::updateCluster: Cluster timestamp 1638035958014
17:59:18.264 D [connect:111 ] no active_device_id
17:59:18.266 D [connect:111 ] no active_device_id
17:59:18.266 D [connect:111 ] no active_device_id
17:59:18.266 D [connect:111 ] no active_device_id
17:59:18.266 D [connect:111 ] no active_device_id
17:59:18.267 D [connect:111 ] no active_device_id
17:59:34.649 I [f:186 ] mdata: caa46e81: Task from `profile` finished. 0/0 entity URIs requested/needed (0.0% cached). 0/0 extensions requested/needed (0.0% w/ ETags, 0.0% cached). 0 unfinished task(s).
17:59:36.779 E [f:83 ] Unable to open database for pruning
17:59:36.779 E [f:102 ] Unable to open database for pruning
17:59:49.015 I [f:591 ] aq: LWS got LWS_CALLBACK_CLIENT_WRITEABLE
17:59:49.035 I [f:591 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE_PONG
18:00:06.779 E [f:83 ] Unable to open database for pruning
18:00:06.779 E [f:102 ] Unable to open database for pruning
18:00:20.047 I [f:591 ] aq: LWS got LWS_CALLBACK_CLIENT_WRITEABLE
18:00:20.068 I [f:591 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE_PONG
18:00:36.779 E [f:83 ] Unable to open database for pruning
18:00:36.780 E [f:102 ] Unable to open database for pruning
18:00:51.008 I [f:591 ] aq: LWS got LWS_CALLBACK_CLIENT_WRITEABLE
18:00:51.028 I [f:591 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE_PONG
18:01:06.779 E [f:83 ] Unable to open database for pruning
18:01:06.779 E [f:102 ] Unable to open database for pruning

 

I deleted the .config/spotify dir and let spotify recreate it. So then it prompted me to enter my details again. Which I did. But after that I got the same error.

Reply
2 Replies

Have the same issue with spotify installed thought this repository on debian 10 :

 

http://repository.spotify.com stable InRelease

 

My actual spotify version is :

 

Spotify version 1.1.72.439.gc253025e, Copyright (c) 2021, Spotify Ltd

 

A workaround is to start spotify from the terminal with the option -mu=0 like this :

 

spotify -mu=0

 

it works for me and i can use spotify normally the time the job run in terminal. if closed, the next time, it need to be started again using exactly the same command from terminal

 

Apparently it seems to be link to a cache directory problem, while spotify provide a patch i'll use this method to stream music.

 

If needed i have some logs and can send it to spotify

Seems to be back to normal

Suggested posts