Package Details: spotify 1:1.3.8.620-1

Git Clone URL: https://aur.archlinux.org/spotify.git (read-only, click to copy)
Package Base: spotify
Description: A proprietary music streaming service
Upstream URL: https://www.spotify.com
Licenses: custom
Submitter: Foxboron
Maintainer: gromit (Antiz)
Last Packager: Antiz
Votes: 274
Popularity: 2.89
First Submitted: 2023-02-09 22:51 (UTC)
Last Updated: 2026-11-09 17:24 (UTC)

Pinned Comments

Antiz commented on 2025-11-23 18:37 (UTC) (edited on 2025-11-23 18:41 (UTC) by Antiz)

Please make sure to import the correct OpenPGP key first:

$ curl -sS https://download.spotify.com/debian/pubkey_5384CE82BA52C83A.gpg | gpg --import -

And always build in a clean chroot. It is as easy as:

pacman -S devtools
git clone https://aur.archlinux.org/spotify.git
cd spotify
pkgctl build
pacman -U <path-to-spotify-package>

It is expected that the package will break now and then, as spotify continuously changes download binaries, OpenPGP keys, etc (which is not appropriate, but we cannot change this). Please be patient if an update does not occur the next day, you can still use an existing spotify install or update the version yourself.

Antiz commented on 2023-09-13 13:21 (UTC)

@lightofpast Just pushed v1:1.2.20.1210-2 that now allows you to set custom launch flags in a spotify-flags.conf file under $XDG_CONFIG_HOME or ~/.config :)

Latest Comments

1 2 3 4 5 6 .. 29 Next › Last »

syriusz commented on 2026-11-10 10:43 (UTC) (edited on 2026-11-10 10:47 (UTC) by syriusz)

Heh... funny thing - I've got two machines with Plasma Wayland and spotify from AUR:

Machine A: PC with Nvidia GPU

Machine B: laptop with B390 integrated GPU

When spotify is run with default flags (so x11 platform):

machine A: works fine

machine B: crashes on scrolling home view

When I put these custom flags (so forcing wayland platform):

machine A: crashes on scrolling home view

machine B: works fine

:-D

So finally I just put these custom flags on machine B and leaved default on machine A - seems to work fine now.

@no4b thanks for help!

no4b commented on 2026-11-10 10:23 (UTC) (edited on 2026-11-10 10:24 (UTC) by no4b)

@syriusz apparently I forgot that wayland is not the default. It surprises me, but hey, you can set it up yourself. You're using it with plasma anyway:

$ cat ~/.config/spotify-flags.conf 
--enable-features=UseOzonePlatform
--ozone-platform=wayland

Give it a try. It works perfectly fine for me.

syriusz commented on 2026-11-10 07:29 (UTC)

@no4b there is nothing custom in my installation - that's the way spotify runs on my Plasma Wayland. By the way - the same "ozone" switch appears on both my machines - both without any custom settings - just Plasma Wayland and spotify installed from AUR.

no4b commented on 2026-11-09 22:48 (UTC)

@syriusz Why are you using --ozone-platform=x11? Works fine for me on Plasma Wayland.

syriusz commented on 2026-11-09 21:30 (UTC)

It seems the last update is worse then the previous one - it constantly crashes while scrolling content on home page view under Plasma Wayland. Crash report:

 PID: 90994 (spotify)
           TID: 90994 (spotify)
           UID: 1000 (syriusz)
           GID: 1000 (syriusz)
        Signal: 11 (SEGV) si_code: SEGV_MAPERR
     Timestamp: Mon 2026-11-09 22:26:18 CET (5s ago)
  Command Line: $'/opt/spotify/spotify --type=gpu-process --no-sandbox --ozone-platform=x11 --crashpad-handler-pid=90969 --enable-crash-reporter=, --change-stack-guard-on-fork=enable --user-data-dir=/home/syriusz/.cache/spotify --log-severity=disable --user-agent-product=Chrome/151.0.7922.138 Spotify/1.3.8.620 --gpu-preferences=YAAAAAAAAAAgAQAEAAAAAAAAAAAAAGAASAAAAAAAAAABAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAwAAAAAAAAAAEAAAAAAAAACAAAAAAAAAAMAAAAAQAAAAAAAAAAAAAACAAAAAAAAAAIAAAAAAAAAA== --shared-files --metrics-shmem-handle=4,i,5106963943661123717,7402359895463316586,262144 --field-trial-handle=3,i,366501125621072772,5860390651785282234,262144 --disable-features=AutofillActorMode,BackForwardCache,EyeDropper,FullscreenBubbleShowOrigin,GlicActorUi,KillOnInvalidNavigationHeaders,LensOverlay,PartitionAllocDanglingPtr,PartitionAllocUnretainedDanglingPtr,StorageNotificationService --variations-seed-version --pseudonymization-salt-handle=7,i,2109289878363923441,17398689904816227746,4 --trace-process-track-uuid=3190708988185955192'
    Executable: /opt/spotify/spotify
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-spotify@2eff7504346e4859bfa28a0e588b0926.service
          Unit: user@1000.service
     User Unit: app-spotify@2eff7504346e4859bfa28a0e588b0926.service
         Slice: user-1000.slice
     Owner UID: 1000 (syriusz)
       Boot ID: 303737a4c125455d84908272ff4095b7
    Machine ID: 5e99e0af0d8944fb80347304a8c3f466
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.spotify.1000.303737a4c125455d84908272ff4095b7.90994.1794259578000000.zst (present)
  Size on Disk: 24.8M
       Message: Process 90994 (spotify) of user 1000 dumped core.

                Stack trace of thread 90994:
                #0  0x00007f3d1c29b8d4 pthread_mutex_lock (libc.so.6 + 0x9b8d4)
                #1  0x00007f3d1ba97448 wl_proxy_create_wrapper (libwayland-client.so.0 + 0x5448)
                #2  0x00007f3c9ae064d0 n/a (libEGL_mesa.so.0 + 0x244d0)
                #3  0x00007f3c9adfca19 n/a (libEGL_mesa.so.0 + 0x1aa19)
                #4  0x00007f3c9adeb8ba n/a (libEGL_mesa.so.0 + 0x98ba)
                #5  0x00007f3d21650263 n/a (libcef.so + 0x4050263)
...

dustovich commented on 2026-11-04 02:45 (UTC)

Anybody notice spotify using large amounts of CPU when minimized? Mine is running 133% when minimized not playing music sometimes.

soundsurf420 commented on 2026-10-27 12:26 (UTC)

minimize to toolbar currently working

inky commented on 2026-08-29 12:28 (UTC)

couldn't autobuild 1.2.96.518-2 with paru. cloned, tried it manually in clean chroot - the error is that I can't download the .sig file

Had to change all http:// schema to https:// in .SRCINFO and PKGBUILD - clean chroot build succeeds, the package can be built.

Antiz commented on 2026-08-26 17:40 (UTC)

@ggdG @agarof, this should be fixed now. Thanks for the heads up :)