Package Details: spotifyd 0.2.20-1

Git Clone URL: (read-only)
Package Base: spotifyd
Description: A spotify playing daemon
Upstream URL:
Licenses: GPL3
Submitter: bertptrs
Maintainer: bertptrs
Last Packager: bertptrs
Votes: 14
Popularity: 0.57
First Submitted: 2018-05-28 10:44
Last Updated: 2019-11-10 13:42

Pinned Comments

bertptrs commented on 2019-04-15 12:07

New users: you may be wondering which package to use for spotifyd. If you're not sure, just use the plain spotifyd package. This installs just the features that upstream has marked as default.

If you need more features, use spotifyd-full. This package includes all optional features (that are applicable to Arch Linux).

Since there are currently 32 possible feature sets, I will be discontinuing the other variants. Both the spotifyd-pulseaudio and spotifyd-dbus-mpris are deprecated in favour of the spotifyd-full package and will be removed with a future release.

Latest Comments

1 2 3 4 Next › Last »

Felixoid commented on 2019-09-18 10:58

@bertptrs Hey. Could you please add provides = ('spotifyd') to the base config, please? Now subpackages don't conflict with each other.

2 all: If you have an issue with thread 'main' panicked at 'calledResult::unwrap()on anErrvalue: Custom("provided string was not true or false")', src/libcore/ after the last update, take a look on the comment

Felixoid commented on 2019-09-17 15:31

I've faced the same issue as @masca does

The error is

>±> spotifyd --no-daemon -b pulseaudio
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Custom("provided string was not `true` or `false`")', src/libcore/
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

I've built the latest spotifyd-full and the config is

username = **name**
use-keyring = true
backend = pulseaudio
device_name = ig-fel-spotifyd
bitrate = 320
volume-normalisation = true
normalisation-pregain = -10

upd: it's in the upstream]

upd2 the issue was in the inline comment in the config. File parser has counted use_keyring = true # can be used as alternative to password as true # can be used as alternative to password and panicked

masca commented on 2019-09-17 15:23

I have installed spotifyd. When I tried to run it I obtain:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Custom("unknown variant `pulseaudio                                        # run `spotifyd --backends` for possible values`, expected one of `alsa`, `portaudio`, `pulseaudio`")', src/libcore/
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

I have placed a spotifyd.config file in ~/.config/spotifyd/ where I set:

# ~/.config/spotifyd/spotifyd.conf
username = **my_username**
password = **my_password**
# password_cmd = command_that_writes_password_to_stdout  # can be used as alternative to `password`
# use_keyring = true                                     # can be used as alternative to `password`
backend = pulseaudio                                        # run `spotifyd --backends` for possible values
device = alsa_audio_device                               # run `aplay -L` for possible values
# control = alsa_audio_device                            # device for the mixer, if not the same as 'device'
mixer = PCM
volume_controller = alsa                                    # or alsa_linear, or softvol
# on_song_change_hook = command_to_run_on_playback_events
device_name = device_name_in_spotify_connect             # must not contain spaces
bitrate = 320                                           # or 96, or 320
cache_path = cache_directory
volume_normalisation = true
normalisation_pregain = -10
zeroconf_port = port_number 

I am certain I am doing something wrong. Yet if I run

spotifyd -b pulseaudio

my config file does not change. It is because spotifyd does not see it?

keithspg commented on 2019-08-06 00:57

Please add armv6h (Pi1 and PiZero). Builds fine.

Epdfjasfvzp commented on 2019-07-22 18:57

So I have my home directory as read-only, and with env vars such as: export CARGO_HOME="$XDG_DATA_HOME"/cargo export RUSTUP_HOME="$XDG_DATA_HOME"/rustup to prevent home directory pollution.

For some reason when I build from source I have no issues, but this AUR package will fail telling me that it can't create /home/user/.rustup. Tried to figure it out but not sure why this PKGBUILD doesn't respect my CARGO_HOME and RUSTUP_HOME env vars.

keithspg commented on 2019-06-17 02:01

ouch! this takes forever to build for such a small package

bertptrs commented on 2019-05-12 16:40

HaoZeke: I can't reproduce the issue, but it looks like you are using an older version of cargo. Cargo 1.34 (from rust) works fine for me.

HaoZeke commented on 2019-05-12 10:47

Seems to be broken right now:

==> Starting package_spotifyd()...
error: `/tmp/makepkg/spotifyd/src/spotifyd-0.2.8` is not a crate root; specify a crate to install from, or use --path or --git to specify an alternate source

Caused by:
  failed to parse manifest at `/tmp/makepkg/spotifyd/src/spotifyd-0.2.8/Cargo.toml`

Caused by:
  editions are unstable

Caused by:
  feature `edition` is required

consider adding `cargo-features = ["edition"]` to the manifest
==> ERROR: A failure occurred in package_spotifyd().
Error making: spotifyd (spotifyd-full)

bertptrs commented on 2019-04-30 10:12

@drpyser, this is an issue with yaourt not handling split packages properly and not with this package. It tries to install all of the different packages together, which is impossible as they provide the same binary.

Please stop using yaourt since it has been unsupported for a few months now, and try another AUR helper such as pikaur or yay which both install spotifyd (and its variants) just fine.

drpyser commented on 2019-04-30 01:59

There seems to be an issue with this package.

Trying to install it(using yaourt -S spotifyd) on my archlinux laptop fails because of conflicting packages:

error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: spotifyd-dbus-mpris and spotifyd are in conflict

See also .

For the record:

$ uname -a
Linux drpyser-main 5.0.9-arch1-1-ARCH #1 SMP PREEMPT Sat Apr 20 15:00:46 UTC 2019 x86_64 GNU/Linux