spicetify / cli

Command-line tool to customize Spotify client. Supports Windows, MacOS, and Linux.
https://spicetify.app
GNU Lesser General Public License v2.1
18.77k stars 734 forks source link

Spotify breaks on Linux apply. #301

Closed samm-sepi0l closed 4 years ago

samm-sepi0l commented 4 years ago

When I run spicetify backup apply the Spotify autostart (as in the automatic launch of spotify after spicetify is applied) doesn't let me play anything, just gives me an error message saying "Spotify can't play this right now. If you have the file on your computer, import it". When I try restarting spotify, it's just broken, blank screen and all. restore backup doesn't help. It's stuck in the blank screen stage until I reinstall spotify itself.

khanhas commented 4 years ago
  1. What is your distro?
  2. Spotify version and how did you install Spotify?
vinhocent commented 4 years ago

Same issue occurs with Windows.

samm-sepi0l commented 4 years ago

Tried it on Ubuntu 20.04 and Linux Mint 20

I have tried flatpak, apt, manually dpkging it, and snap when I was on Ubuntu. No luck, I even tried the featured .deb's on this here repository. My spotify version is currently the latest. But I have tried older versions such as the ones you had here.

3raxton commented 4 years ago

Dealing with this on Mac as well. The issue for me came from Spotify's newest update, which is 1.1.43.700. I reinstalled from the website and was fortunate to end up with 1.42 again, which works with spicetify-cli, but it seems like the problem comes from 1.43

tikeyike commented 4 years ago

I had a similar issue — What I ended up doing was to download Spotify again from the Spotify website (for windows) - version 1.1.43.700.g20acee0f

Then I ran the spicetify backup apply command again, and that seemed to fix the issue for me.

Pushkin31 commented 4 years ago

I support the problem. Some control buttons are also gone and the design cannot be used on any themes. spotify-1: 1.1.42.622-1 spicetify v1.1.0 arch linux kernel: 5.8.12-arch1-1 qt 5.15.1-1 gtk engine murrine 0.98.2-4

Screenshot > ![photo_2020-10-01_16-32-57](https://user-images.githubusercontent.com/35974828/94817665-ed72bf80-0405-11eb-8db0-d064496a07b8.jpg)
samm-sepi0l commented 4 years ago

Still doesn't work guys. I tried using an older version (1.26) and I'm getting the same blank screen unless I open from the terminal. And once that happens it does not let me play anything. I still get the banner saying "Spotify can't play this right now. If you have the file on your computer you can import ti".

samm-sepi0l commented 4 years ago

GUYS I FIGURED IT OUT. Instead of installing with curl install Homebrew on your devices first and install run homebrew install spicetify or spicetify-cli. That fixed it for me, there's something wrong with curl.

3raxton commented 4 years ago

I have spicetify-cli installed via Homebrew and still deal with this issue. I wouldn't say this issue is completely resolved.

samm-sepi0l commented 4 years ago

@3raxton Well, my bad, I'll keep it open again until you Mac and Windows users get something from Khan.

3raxton commented 4 years ago

All good! I appreciate that you’re opening it again for us. Thank you! On Oct 6, 2020, 10:35 -0500, samm-sepi0l , wrote:

Well, my bad, I'll keep it open again until you Mac and Windows users get something from Khan. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

3raxton commented 4 years ago

Just took a look at #304, and it looks like what I ran into was that I applied an old back up to a new version of Spotify. Hoping to hear from @khanhas on this, but it looks like we should back up after each update. Do I understand this correctly?

khanhas commented 4 years ago

It supposes to show a warning when you try to apply old backup on new version. I wonder if any of you guys saw that warning.

samm-sepi0l commented 4 years ago

I saw no warning, and I've tried it with so many different distributions of Spotify, it'd be odd if all of them had "mismatched version" warnings no?