search

SpotX-Official / SpotX-Bash

SpotX Mac and Linux adblocker for the Spotify desktop client, in Bash
MIT License
1.7k stars 58 forks source link

SpotX not installing, stating "no backup file!" #21

Closed breddie-normie closed 8 months ago

breddie-normie commented 8 months ago

๐Ÿง Have you fully read the README and viewed similar issues?

ะกountry of your account

India

What is your Spotify Plan?

Free

Do you have Spicetify installed?

No

โ„น Computer information

- Spotify version: 1.2.22.982
- OS: Artix Linux
- Shell: fish  (switched to bash for installation)

๐Ÿ“ Description

Tried reinstalling both spotify-launcher and this program, but to no avail.

๐Ÿ–ฅ๏ธ Terminal Input/Output

bash <(curl -sSL https://spotx-official.github.io/run.sh) -cdhf

โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ•— โ–ˆโ–ˆโ–ˆโ•— โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ•— โ–ˆโ•— โ–ˆโ–ˆโ–ˆโ•— โ–ˆโ–ˆโ•— โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ•— โ–ˆโ•— โ–ˆโ•”โ•โ•โ•โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ•โ–ˆโ•—โ•šโ•โ–ˆโ•”โ•โ•โ•šโ–ˆโ•—โ–ˆโ•”โ• โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ•โ•โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ•”โ•โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ•‘ โ•šโ–ˆโ•”โ•โ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ•”โ•โ–ˆโ–ˆโ–ˆโ–ˆโ•‘โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ–ˆโ•‘ โ•šโ•โ•โ–ˆโ•‘โ–ˆโ•”โ•โ• โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ•”โ–ˆโ•—โ•šโ•โ•โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ–ˆโ•‘โ•šโ•โ•โ–ˆโ•‘โ–ˆโ•”โ•โ–ˆโ•‘ โ–ˆโ–ˆโ–ˆโ–ˆโ•‘โ–ˆโ•‘ โ•šโ–ˆโ–ˆโ–ˆโ•”โ• โ–ˆโ•‘ โ–ˆโ•”โ• โ–ˆโ•— โ–ˆโ–ˆโ–ˆโ•”โ•โ–ˆโ•‘ โ–ˆโ•‘โ–ˆโ–ˆโ–ˆโ–ˆโ•‘โ–ˆโ•‘ โ–ˆโ•‘ โ•šโ•โ•โ•โ•โ•šโ• โ•šโ•โ•โ• โ•šโ• โ•šโ• โ•šโ• โ•šโ•โ•โ• โ•šโ• โ•šโ•โ•šโ•โ•โ•โ•โ•šโ• โ•šโ•

Searching for Spotify directory...

Found Spotify Directory: /home/breddie/.local/share/spotify-launcher/install/usr/share/spotify

/home/breddie/.local/share/spotify-launcher/install/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /home/breddie/.local/share/spotify-launcher/install/usr/share/spotify/spotify) Latest supported version: 1.2.22.982 Detected Spotify version: 1.2.22.982

โœ” Created backup โœ” Cleared app cache

Warning: Detected SpotX but no backup file! Reinstall Spotify. Exiting...

๐Ÿ“ธ Screenshots

image

jetfir3 commented 8 months ago

Hmm.. something strange is going on as it's detecting modified files even before any patches were made.

EDIT Can you detail if Spotify was patched on a previous version at any point before this.. and if so, what patched it? Or was this the very first time Spotify was patched on the system?

EDIT 2 I setup an Arch install and used spotify-launcher to install Spotify but was unable to replicate this issue. Installed spotify-launcher with:

sudo pacman -Syu spotify-launcher

Installed Spotify with:

spotify-launcher

Ran SpotX-Bash with:

bash <(curl -sSL https://spotx-official.github.io/run.sh) -cdhf

No errors. I then did a "force-update" with spotify-launcher to see how Spotify client reinstalls/updates were handled...

spotify-launcher --force-update

with and without SpotX-Bash used and in all cases the Spotify app directory was properly cleared out first and then the app was uninstalled (no SpotX-Bash backups etc were still found in the directory.. which is what we want after an update/reinstall). Re-running SpotX-Bash after the forced-updates all worked without issue.

Based on your initial report and error output I can only assume files in the spotify directory were handled by a user or another patcher or something at some point (and not spotify-launcher or SpotX-Bash exclusively).. regardless deleting the Spotify directory entirely then reinstalling spotify via spotify-launcher and then re-running SpotX-Bash should get things going.

  1. rm -rf /home/breddie/.local/share/spotify-launcher/install/usr/share/spotify/
  2. spotify-launcher --force-update
  3. bash <(curl -sSL https://spotx-official.github.io/run.sh) -cdhf
jetfir3 commented 8 months ago

Closed due to no response after 1 week.

Previous post should take care of specific issue.

breddie-normie commented 8 months ago

Closed due to no response after 1 week.

Previous post should take care of specific issue.

Sorry for this late reply, it's now working properly. Thanks for resolving this. Cheers.