Package Details: spotify-adblock-git 1:1.0.0.r2.g990c0f2-1

Git Clone URL: (read-only, click to copy)
Package Base: spotify-adblock-git
Description: Adblocker for Spotify
Upstream URL:
Licenses: GPL3
Conflicts: spotify-adblock
Provides: spotify-adblock
Submitter: xyzzy
Maintainer: xyzzy
Last Packager: xyzzy
Votes: 48
Popularity: 2.98
First Submitted: 2018-12-14 14:05 (UTC)
Last Updated: 2021-05-06 07:48 (UTC)

Latest Comments

coxackie commented on 2022-01-10 18:23 (UTC)

Apologies for the "advertisement", but I have created a simple solution for getting rid of the ad banner. The removal persists via a hook with new installations of spotify. You can find it here. Certainly not my idea, and not taking credit for it (as mentioned there), but hope it helps.

kr0wx1 commented on 2021-12-16 13:37 (UTC)

@coxackie awh my bad I didn't know that, thank you so much for the information/explanation.

coxackie commented on 2021-12-16 12:03 (UTC)

@kr0wx1 xyzzy has already answered exactly the same thing below. This is a git package, and does not need to be updated as it builds from git. Just rebuild it, and install. Alternatively, if you are using paru or yay, they should pick up that there is a newer commit.

kr0wx1 commented on 2021-12-16 11:52 (UTC)

hey, thanks for maintaining this package. are you going to update it?? there is a new commit that fixes the issues with the latest spotify updates.

xyzzy commented on 2021-12-15 09:42 (UTC)

@Sanras: I don't think you're supposed to do that with VCS packages. FWIW, paru seems to notice the changes and rebuild automatically.

Sanras commented on 2021-12-15 00:56 (UTC)

@xyzzy, I think you should update the version number in the PKGBUILD so that everyone's AUR helpers can automatically rebuild the package. There was an update 11 hours ago to spotify-adblock that fixes an issue with all songs becoming greyed out and unplayable. Rebuilding the package is necessary to make Spotify work properly again.

Sanras commented on 2021-11-18 16:25 (UTC)

Found this useful in combination with this package, thought I would share - The BlockTheSpot project (Basically spotify-adblock-linux but for Windows), provides a way to patch out not just the ad banner, but also the upgrade button. They are both xpui.js modifications. BTS updates their script with each Spotify update, so you can use it as a reference to manually apply their patches on your own Spotify install. You can take a look at their pacthes by going through their PowerShell install script located here -

Scroll to "Remove ad placeholder and upgrade button. (Y/N)" section of the script.

xyzzy commented on 2021-06-03 18:47 (UTC)

allexj: Your AUR helper apparently can't handle that the source Github repository has recently changed. You can probably fix that error by deleting the cached repository (i.e. rm -rf ~/.cache/yay/spotify-adblock-git).

allexj commented on 2021-06-03 18:38 (UTC) (edited on 2021-06-03 18:41 (UTC) by allexj)

If I try to update I get this error:

==> ERROR: /home/myuser/.cache/yay/spotify-adblock-git/spotify-adblock is not a clone of The operation is about to be aborted... error downloading sources: spotify-adblock-git

I fixed removing /home/myuser/.cache/yay/spotify-adblock-git

xyzzy commented on 2021-05-06 07:11 (UTC) (edited on 2021-05-06 07:53 (UTC) by xyzzy)

@polyzen: Thanks for the hint! I've changed the pkgver and also removed the epoch, since the new versioning scheme already preserves monotonicity.

Edit: Removing the epoch wasn't a good idea apparently. It breaks version monotonicity for people who had already updated while it was added, so I restored it.

polyzen commented on 2021-05-06 02:13 (UTC) (edited on 2021-05-06 02:14 (UTC) by polyzen)

With projects that tag releases, you should use a pkgver that includes the version and numbers of commits since that release.

For this project you could get that with: git describe --long --tags | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g'

coxackie commented on 2021-05-05 21:45 (UTC)

@xyzzy I do apologise; while I was following the thread, I can also see that it is off (package-)topic. I can rescind the previous comments, if you wish, for integrity's sake.

xyzzy commented on 2021-05-05 19:53 (UTC) (edited on 2021-05-05 19:54 (UTC) by xyzzy)

@coxackie: Enabling higher bitrates isn't possible. Requesting the decryption keys with a free account just results in errors.

That said, please try to keep comments here about this AUR package.

Sanras commented on 2021-05-05 19:47 (UTC)

@coxackie I don't think we can enable higher bitrates, as that seems to be tied to the account. I have a modded Android Spotify app as well, and it has unlocked skips, no ads, etc. They also enabled the quality changer, but noted that it doesn't actually do anything, as that setting is controlled server-side. I guess you are simply not given access to the higher quality files with a free account, which makes sense. So unfortunately, you do still need to pay for premium to get that. However, I honestly don't care too much, I was never able to tell the difference between 128kbps and 320 anyway.

coxackie commented on 2021-05-05 19:25 (UTC)

@Sanras this is awesome - can confirm. many thanks. It should not be too difficult to make a script that does this automatically, using sed. however, this makes one wonder... are there other properties that we can play with that allow, for example, to enable 320 bitrate, like in premium...

Sanras commented on 2021-05-05 18:19 (UTC) (edited on 2021-05-05 18:20 (UTC) by Sanras)

@coxackie, with huge thanks to @xyzzy for pointing me in the right direction, I found the line that controls the UI ads.

Unzip, and open xpui.js with a text editor. Search for the following line - a=()=>({type:r.ADS_ENABLED}), and replace it - a=()=>({type:r.ADS_DISABLED}).

Save file, rezip it (Seems compression level doesn't matter too much, I used Ark, and left it at default). Then rename the in /opt/spotify/Apps to, and paste in the modified version.

coxackie commented on 2021-05-05 15:56 (UTC)

@Sanras could you please report back on what you did for this? I think one can make a separate aur package that provides a hook to potentially replace xpui.js in every occasion (reverting the change upon uninstall). Hopefully it does not change too much between versions.

Sanras commented on 2021-05-05 15:33 (UTC)

@xyzzy, thanks for that info. I will look into it myself and see if I can remove the placeholder.

You say that it's a zip file, does it need a specific compression level when zipping it back up? I remember back when I was swapping my phone's boot animation, it wouldnt work unless the compression was set to "store" (no compression) level.

Another idea - since this would need to be done with every update, could I make a shell script to automate this? Of course, this depends on how much the xpui.js file changes each time.

xyzzy commented on 2021-05-05 15:27 (UTC)

@Sanras @matt17br: I removed the ad placeholder by modifying xpui.js in /opt/spotify/Apps/ (zip file). Can't remember what exactly I changed, but there are some rather convenient properties you can look for (e.g. "ADS_ENABLED"). Getting rid of all the ads like that should be possible in principle, but would likely be a lot of work and the changes would also have to be reapplied after every update.

matt17br commented on 2021-05-05 15:17 (UTC)

Yeah, I'm using the latest spotify package, and yep I also have the hardcoded rectangle thingy you mention, but oh well I just ignore it because the new spotify version feels much snappier on my system anyways.

Sanras commented on 2021-05-05 15:14 (UTC)

@matt17br - yeah, you're right about that. I guess that can be pretty useful.

Also, I assume you're using the latest spotify package. Do you have the new UI? One issue I noticed is that with the new UI, there is a hard-coded spot for ad placement, so there is currently a blank rectangle right above the media controls, which is slightly annoying. Anything that can be done about this? Maybe roll back the package version? I do have 1.55 and and 1.42 in my yay cache.

matt17br commented on 2021-05-05 15:09 (UTC)

@Sanras, updating worked fine on my system, no need to uninstall/reinstall. One advantage I see is that in order to update whitelist/config files etc. you do not need to rebuild the package every time, which is something you used to need to do in the C version. Check the github page "Configuration" section.

Sanras commented on 2021-05-05 15:05 (UTC)

Is it fine to update from the C version to the rust version, or should I uninstall and then reinstall the package? I assume update is fine?

Also, does anyone know the reason for this change? I honestly only see disadvantages, because now I need to install the rust package, which just adds more space-eating bloat to my system.

coxackie commented on 2021-05-05 10:48 (UTC)

@xyzzy a recent development means that there is a bit of an issue with the naming of the package. evidently, abba23 rewrote spotify-adblock in rust - see (here)[]. According to the old C version (here)[], this package should be renamed to spotify-adblock-linux-git, and spotify-adblock-git should most probably point to the new rust version.

desaparecido commented on 2021-04-28 07:08 (UTC)

when you have VCS package like -GIT version, you need to rebuild it (makepkg command) to have the latest version, and if you use a AUR helper, you need to re-install it to have the latest one. Is your system, is your responsability , in Archlinux not all is "automagically".

xyzzy commented on 2021-04-28 06:59 (UTC) (edited on 2021-04-28 07:00 (UTC) by xyzzy)

@Sanras @ThePoorPilot: That's not how it works with VCS packages.

VCS packages are not considered out of date when the pkgver changes, do not flag them as the maintainer will merely unflag the package and ignore you. AUR maintainers should not commit mere pkgver bumps.


Sanras commented on 2021-04-27 23:26 (UTC)

@xyzzy, I agree with @ThePoorPilot. It would be helpful if you could update the package's version number please.

ThePoorPilot commented on 2021-04-27 23:03 (UTC)

The PKGBUILD itself isn't out of date, but the package version is out of date.

Would it be possible to update the version number to r87.451b206-1, the newest version.

Since the version number isn't being updated in the PKGBUILD, people are not getting update notifications in their AUR helpers.

ren92 commented on 2021-04-13 09:30 (UTC)

@matt17br @Koushik_Sahu thanks you both, the reinstall did the trick!

Koushik_Sahu commented on 2021-04-13 06:33 (UTC)

for anyone facing problems in home screen loading and search not working just need to reinstall the package with

yay -S spotify-adblock-git

matt17br commented on 2021-04-12 16:00 (UTC)

@ren92 take a look at this GitHub issue I opened:

ren92 commented on 2021-04-12 15:06 (UTC)

@matt17br can you tell me what the solution for the not loading issue was? I have the same problem on the current version. Thanks!

f3bruary commented on 2021-03-25 14:15 (UTC)

The latest git version fixes this. (At least for me)

matt17br commented on 2021-03-21 23:03 (UTC)

@xyzzy, that was a great pointer because I think I might have found what the issue is. Opened an issue in the github repo, thanks.

xyzzy commented on 2021-03-21 22:41 (UTC)

@matt17br, the spotify AUR package now follows the testing branch instead of the stable branch. Everything has been working for me, but there can be regional differences with what needs to be whitelisted.

It would help if you could do some debugging by launching Spotify with the adblocker from a terminal (LD_PRELOAD=/usr/lib/ spotify) and see if there are any blocked requests when you try to access the pages that aren't working for you. Please create an issue on Github if you find anything, so this can be fixed for everyone.

matt17br commented on 2021-03-21 21:38 (UTC) (edited on 2021-03-21 21:38 (UTC) by matt17br)

@Sanras, thanks for the reply, I tried launching the non-adblock version too when I encountered your same issue, that did get me to launch spotify-adblock properly, but it still didn't fix the artist/album/homepage not loading issue. Those pages are loading just fine for you I assume? I had the same issue on r80.f81c8bc-1 btw.

Sanras commented on 2021-03-21 21:29 (UTC)

@matt17br, the new Spotify version is working fine for me. After the update, it wouldn't launch with adblock, but once I launched it without adblock and then launched it with adblock, it has been working fine ever since. However, my package is r80.f81c8bc-1, not r82.d458130-1, so that may be why.

matt17br commented on 2021-03-21 21:14 (UTC)

i've rebuilt spotify-adblock-git and i'm on version r82.d458130-1. however, this new version doesn't seem to play well with the latest spotify stable branch update (1.55). i can listen to music fine, and search works properly, however artist profiles, albums, as well as the home page can't be loaded at all. i'm pretty sure it's not normal behaviour since the dev seems to have updated the app with support for the latest version, so i'd like to hear if anyone has encountered the same issue, thanks.

Sanras commented on 2021-01-27 15:13 (UTC)

The new version here in the AUR is version r77.0802c42-1, but once the package is built, the version becomes r80.f81c8bc-1. Why do the versions not match?

AvinashReddy3108 commented on 2021-01-06 14:23 (UTC) (edited on 2021-01-06 14:24 (UTC) by AvinashReddy3108)

For those who use spicetify-cli's Reddit "custom app", here's a patch which helps spotify-adblock-git work with it.

Also, the package should now conflict with spotify-adblock-linux instead of spotify-adblock.

EDIT: Oops, forgot to add the PR link.

ZeroDot1 commented on 2020-10-03 19:21 (UTC)

Sanras commented on 2020-10-02 17:58 (UTC) (edited on 2020-10-03 16:58 (UTC) by Sanras)

Does this new version (68.624) work with Spotify version 1.1.42? I am currently running 65 of adblock, and keeping Spotify at 1.1.10, because of the banner that shows up after updating Spotify to 1.1.42.

Edit - Nvm, I tested it on another computer, and yes, this package now works properly with the latest Spotify, 1.1.42.

hekaton commented on 2020-10-02 00:02 (UTC)

Not working with the latest update

avemilia commented on 2020-09-09 05:03 (UTC)

Needs a curl dep and (at least on manjaro) this patch:

xyzzy commented on 2019-09-20 10:20 (UTC)

Thanks for the hint. I've updated the permissions.

polyzen commented on 2019-09-17 14:42 (UTC)

The shared library shouldn't be executable:

install -Dm644 -t "${pkgdir}/usr/share/applications" "${_pkgname}.desktop"
install -Dm644 -t "${pkgdir}/usr/lib" "${_pkgname}/${_pkgname}.so"

laichiaheng commented on 2019-04-25 05:29 (UTC)

It will appear a new icon on Gnome dock if I have pin it on the Gnome dock.

coxackie commented on 2019-01-30 11:13 (UTC) (edited on 2019-01-30 11:13 (UTC) by coxackie)

Awesome - many thanks!