Package Details: tidal-hifi-git 4.1.0.r0.g1439a11-1

Git Clone URL: (read-only, click to copy)
Package Base: tidal-hifi-git
Description: The web version of running in electron with hifi support thanks to widevine. If the install fails use nvm to temporarily downgrade npm
Upstream URL:
Licenses: custom:MIT
Conflicts: tidal-hifi
Provides: tidal-hifi
Submitter: mastermindzh
Maintainer: mastermindzh
Last Packager: mastermindzh
Votes: 5
Popularity: 0.35
First Submitted: 2021-06-26 14:03 (UTC)
Last Updated: 2022-08-07 14:55 (UTC)

Latest Comments

mastermindzh commented on 2022-06-25 20:15 (UTC)

@deimidis, @papavlos,

Should be fixed now ;) Enjoy!

deimidis commented on 2022-06-24 17:55 (UTC)

@mastermindzh thanks for your work. I installed the pacman file that was created by your script. The only problem is now the package is tidal-hifi and not tidal-hifi-git, but that will be resolved with your new package

mastermindzh commented on 2022-06-24 07:19 (UTC)

Hey Guys,

Deimidis is on the right track. Nothing in the PKGBUILD actually changed and I accidentally have rpm-tools installed so I didn't notice it :/

The update of electron-builder does indeed mean that some of the configs have to change which we also didn't notice before deployment.

As for now, you can temporarily install the rpm-tools package to finish the install. I will have time later this evening (after work, CEST) to figure out the new build configs and update this repo.

Sorry for the inconvenience!


Glad you like it. I specifically included a temporary nvm setup to work around the downgrade of npm :) Shouldn't be something the user worries about!

deimidis commented on 2022-06-23 21:39 (UTC)

I see that PKGBUILD says npm run build-arch but it seems it's built everything. I think the problem is that electron-builder.pacman.yml extends electron-builder.yml (and this build everything)

deimidis commented on 2022-06-23 21:05 (UTC)

I have the same problem that @papavlos. I tried to check if can find the part of the code that creates rpm, and see there's an Appimage created as well. So I will use it in the meantime.

papavlos commented on 2022-06-23 17:50 (UTC) (edited on 2022-06-23 17:57 (UTC) by papavlos)

Thanks a lot @mastermindzh for maintaining it! As a matter of fact the package builds without any need of downgrading npm.

Missing dependence on rpm-tools detected - please add this. The building process fails without the package being installed.

By the way, please review if we really need all these builds like rpm, deb, freebsd, snap, etc? They are very time (and energy) consuming. I suspect that they are useless for us here on Arch.

mastermindzh commented on 2022-03-14 09:18 (UTC)


Your error log indicates that installing nvm (which is a dependency) is failing because you didn't provide pacman with a password: See:

==> Installing package nvm with pacman -U...
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required

blakerateliff commented on 2022-03-13 18:08 (UTC) (edited on 2022-03-13 18:10 (UTC) by blakerateliff)

Package is broken as-is. Manually installing package: "nvm" resolved the issue. It should probably be added as a dependency.

Building tidal-hifi...
==> Making package: tidal-hifi 2.7.2-1 (Sun 13 Mar 2022 01:00:24 PM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   137  100   137    0     0    660      0 --:--:-- --:--:-- --:--:--   661

100   97k    0   97k    0     0   157k      0 --:--:-- --:--:-- --:--:--  157k
100 2897k    0 2897k    0     0  3442k      0 --:--:-- --:--:-- --:--:-- 12.4M
  -> Found tidal-hifi.desktop
==> Validating source files with md5sums... ... Passed
    tidal-hifi.desktop ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting with bsdtar
==> Starting prepare()...
nvm could not be found, installing
Cloning into '01801b4cb7ec'...
==> Making package: nvm 0.39.1-1 (Sun 13 Mar 2022 01:00:27 PM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading nvm-0.39.1.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   129  100   129    0     0    665      0 --:--:-- --:--:-- --:--:--   668

100  162k    0  162k    0     0   257k      0 --:--:-- --:--:-- --:--:--  257k
  -> Found
  -> Found install-nvm-exec
==> Validating source files with sha256sums...
    nvm-0.39.1.tar.gz ... Passed ... Passed
    install-nvm-exec ... Passed
==> Extracting sources...
  -> Extracting nvm-0.39.1.tar.gz with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "nvm"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: nvm 0.39.1-1 (Sun 13 Mar 2022 01:00:28 PM CDT)
==> Installing package nvm with pacman -U...
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required
==> WARNING: Failed to install built package(s).
==> ERROR: A failure occurred in prepare().

mastermindzh commented on 2022-02-23 16:17 (UTC)

Hey @deimidis,

Some dependencies have been moved to libxcrypt-compat, I will add it as a dependency of tidal-hifi.

All in all, the build works again :)

deimidis commented on 2022-02-22 15:05 (UTC) (edited on 2022-02-22 15:06 (UTC) by deimidis)

I'm having problems updating this package with yay. I tried with a cleanbuild too, but the same error (it's working with the old version):

> tidal-hifi@2.7.2 build-arch
> electron-builder --publish=never -c ./build/electron-builder.pacman.yml

  • electron-builder  version=22.14.5 os=5.15.24-1-MANJARO
  • loaded configuration  file=/home/deimidis/.cache/yay/tidal-hifi-git/src/tidal-hifi/build/electron-builder.pacman.yml
  • loaded parent configuration  file=/home/deimidis/.cache/yay/tidal-hifi-git/src/tidal-hifi/build/electron-builder.yml
  • writing effective config  file=dist/builder-effective-config.yaml
  • rebuilding native dependencies  dependencies=abstract-socket@2.1.1, register-scheme@0.0.2 platform=linux arch=x64
  • packaging       platform=linux arch=x64 electron=8.5.2 appOutDir=dist/linux-unpacked
  • building        target=pacman arch=x64 file=dist/tidal-hifi-2.7.2.pacman
  ⨯ cannot execute  cause=exit status 127
                    errorOut=/home/deimidis/.cache/electron-builder/fpm/fpm-1.9.3-2.3.1-linux-x86_64/lib/ruby/bin.real/ruby: error while loading shared libraries: cannot open shared object file: No such file or directory

                    command=/home/deimidis/.cache/electron-builder/fpm/fpm-1.9.3-2.3.1-linux-x86_64/fpm -s dir --force -t pacman -d c-ares -d ffmpeg -d gtk3 -d http-parser -d libevent -d libvpx -d libxslt -d libxss -d minizip -d nss -d re2 -d snappy -d libnotify -d libappindicator-gtk3 --pacman-compression xz --architecture amd64 --after-install /tmp/t-8jXgJ5/1-after-install --after-remove /tmp/t-8jXgJ5/0-after-remove --description '
     Tidal on Electron with widevine(hifi) support' --version 2.7.2 --package /home/deimidis/.cache/yay/tidal-hifi-git/src/tidal-hifi/dist/tidal-hifi-2.7.2.pacman --name tidal-hifi --maintainer 'Rick van Lieshout <>' --url --vendor 'Rick van Lieshout <>' --license MIT /home/deimidis/.cache/yay/tidal-hifi-git/src/tidal-hifi/dist/linux-unpacked/=/opt/tidal-hifi /home/deimidis/.cache/yay/tidal-hifi-git/src/tidal-hifi/assets/icon.png=/usr/share/icons/hicolor/0x0/apps/tidal-hifi.png /tmp/t-8jXgJ5/2-tidal-hifi.desktop=/usr/share/applications/tidal-hifi.desktop
==> ERROR: A failure occurred in build().

mastermindzh commented on 2022-02-17 15:46 (UTC)

Thanks to Mar0xy the app now adds the flag automatically when starting :) Enjoy!

Batpope commented on 2022-02-16 18:28 (UTC) (edited on 2022-02-16 18:29 (UTC) by Batpope)

To fix the app not launching, start tidal-hifi with the --disable-seccomp-filter-sandbox flag:

$ tidal-hifi --disable-seccomp-filter-sandbox

Credits to Mar0xy on github for the fix:

Batpope commented on 2022-02-15 20:33 (UTC) (edited on 2022-02-15 20:35 (UTC) by Batpope)

@carlosal1015 tried installing libxcrypt-compat but didn't fix the issue. Running tidal-hifi in the terminal outputs this:

(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false". It will change to be "true" in Electron 9. For more information please check

[1847:0215/] The display compositor is frequently crashing. Goodbye.

Trace/breakpoint trap (core dumped)

carlosal1015 commented on 2022-02-15 19:04 (UTC) (edited on 2022-02-15 19:08 (UTC) by carlosal1015)

Possible related with this bug

Batpope commented on 2022-02-15 17:15 (UTC)

Tried opening tidal-hifi today but it seems that something updated in my system that causes the app to immediately close. It's happening on my brother's Arch system as well.

mastermindzh commented on 2021-12-28 16:25 (UTC)

Good to hear lastbreak!

Having a "prefix" in npmrc isn't all too common luckily :) PS: an update will be released later today so you get to try again :D

lastbreak commented on 2021-12-28 16:13 (UTC)

Hey mastermindzh,

Thanks for the tip. I've been trying to run the command deployed in the error in my terminal but didn't work. So I follow your advice and did a 'sudo nano' edit at the .npmrc file and disabled the only entry that was there "prefix=/usr" and I was able to run the normal update of this package. I hope that by disable that it won't give any more issues in the future. Thanks!

mastermindzh commented on 2021-12-28 14:40 (UTC)

Hey lastbreak,

Your .npmrc file in the home directory is incompatible with nvm. nvm is a requirement for the build process.

You can run the delete prefix line from the error message. Alternatively you can look at the .npmrc file yourself and remove the prefixes/globalconfigs.

lastbreak commented on 2021-12-28 12:00 (UTC)

I'm still not able to update this package from 2.4.0 to 2.6.0

It gives me the following return error:

Clonando em 'tidal-hifi'...
==> A iniciar prepare()...
found in /usr/share/nvm, sourcing...
Your user’s .npmrc file (${HOME}/.npmrc)
has a `globalconfig` and/or a `prefix` setting, which are incompatible with nvm.
Run `nvm use --delete-prefix v16.13.1 --silent` to unset it.
==> ERRO: Uma falha ocorreu em prepare().
    A cancelar...

Maybe you can come up with an update to fiz this error. Thanks in advance.

mastermindzh commented on 2021-12-19 12:45 (UTC)

With 2.6.0 nvm is now also sourced from /usr/share/nvm/ if it exists, enjoy!

papavlos commented on 2021-12-08 23:53 (UTC)

@rettetdemdativ Thanks for your hint with "source" command. It worked!

Batpope commented on 2021-12-08 22:18 (UTC)

Thanks for the quick update @mastermindzh, unfortunately, now I'm having the same error as @NecroMortis and @carlosal1015

rettetdemdativ commented on 2021-12-08 18:08 (UTC) (edited on 2021-12-08 18:08 (UTC) by rettetdemdativ)


The following worked for me:

  1. source /usr/share/nvm/ to source your nvm installation

  2. Install

carlosal1015 commented on 2021-12-08 17:11 (UTC)

Nope @NecroMoris, we are not alone.

NecroMortis commented on 2021-12-08 16:57 (UTC)

Only I have a problem? :(

⨯ cannot execute cause=exit status 1 errorOut=npm ERR! code 1 npm ERR! path /home/user/.cache/yay/tidal-hifi-git/src/tidal-hifi/node_modules/register-scheme npm ERR! command failed npm ERR! command sh -c node-gyp rebuild npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using node-gyp@8.2.0 npm ERR! gyp info using node@17.1.0 | linux | x64 ... ...

mastermindzh commented on 2021-12-08 16:46 (UTC)

I just pushed a pkgbuild that uses a random foldername for nvm. Should help with the errors.

rettetdemdativ commented on 2021-12-08 16:18 (UTC)

I also unfortunately have the same error as @Batpope.

mastermindzh commented on 2021-12-07 07:50 (UTC)


same nvm error?

I can change the way the pkgbuild clones nvm to solve it later today / tomorrow.

Batpope commented on 2021-12-06 23:48 (UTC)

I'm still unable to build this since the first of december update

rcsilva83 commented on 2021-12-05 15:38 (UTC)

I didn't have nvm installed and I'm getting this error on nvm installation. It tells it couldn't ask passworkd for sudo (I'm using pamac GUI).

Then I installed nvm, it didn't recognized it was installed and got the error that .nvmdep directory already exists. After removing it, I got the first error again.

mastermindzh commented on 2021-12-03 07:55 (UTC)

Hey @kivarnis,

I saw that. The npm listed in the pkgbuild is actually just "npm" without a version number so I don't know why it defaults to 6. I'll try to change that tonight.

Kivarnis commented on 2021-12-02 21:58 (UTC) (edited on 2021-12-02 21:59 (UTC) by Kivarnis)

That sounds good, but npm6 isn't in the repos anymore. Your own depend links there point to nothing.

mastermindzh commented on 2021-12-01 08:44 (UTC)

Please don't flag the package as out-of-date if the build fails ;)

You're building a -git package, this means you are required to have some dev tools (which are listed as dependencies as well) to build the software. If these dev tools aren't configured correctly you can get an error (which is the case).

In many cases your version of npm is either too old or too new (the dependency listed on this page is 6).

usuariopolivalen commented on 2021-10-26 01:15 (UTC)

hello! a new user of tidal here. Something to say about strawberry player and it's support? i have been testing it and there was no way to get it working because of the token api or id client...

mastermindzh commented on 2021-06-26 14:08 (UTC)

This is the new official tidal-hifi. FabioLinux took over the other one and has already abandoned it.

I will keep this one up to date again..