Illegal instruction (core dumped)

[mcdragon]

Plan

Premium

Country

UK

Device

PC

Operating System

Arch Linux

My Question or Issue

Running spotify either as re-packaged spotify for linux via aur helper or spotify-launcher doesn't work

spotify --show-console --debug-level=MAX
16:34:56.744 E [f:25 ] TCPServer: Failed to create port checker
16:34:56.757 I [f:229 ] Starting step: core_init
16:34:56.757 I [f:159 ] Access allowance changed from online: 0 stream: 0, sync: 0, persistent conn: 0 to online: 1 stream: 1, sync: 0, persistent conn: 1
16:34:56.758 I [f:77 ] Connectivity policy is initially allow_all
16:34:56.758 I [f:79 ] Connection type is initially unknown
16:34:56.758 I [f:96 ] Enabling all persistent connections
16:34:56.758 I [f:139 ] Open storage index header at /home/mcdragon/.cache/spotify/Storage/index.dat
16:34:56.758 I [f:23 ] Opened storage index at /home/mcdragon/.cache/spotify/Storage OK
16:34:56.758 I [f:271 ] NmNetworkNotifier is not aware of running NetworkManager (yet), assume 'ethernet'
16:34:56.759 I [f:248 ] Ending step: core_init
16:34:56.763 I [f:271 ] NmNetworkNotifier is not aware of running NetworkManager (yet), assume 'ethernet'
16:34:56.763 I [f:389 ] Reachability changed from unknown (IP [], roaming false) to ethernet (IP [192.168.1.15, fe80::f716:ab01:5c73:c5b2%enp3s0], roaming false)
16:34:56.763 I [f:159 ] Access allowance changed from online: 1 stream: 1, sync: 0, persistent conn: 1 to online: 1 stream: 1, sync: 1, persistent conn: 1
16:34:56.763 I [f:190 ] Scheduling emission of signal.
16:34:56.765 I [f:123 ] connectivityChanged(), is_logged_in:1
16:34:56.766 I [f:243 ] aq: Updating dealer URL from 'wss://gew1-dealer.spotify.com:443'
Illegal instruction (core dumped)

Restarting PC doesn't work

Re-installing doesn't work

Current workaround: manual rebuild from to /var/lib/snapd/snap/bin/spotify

git clone https://aur.archlinux.org/spotify.git

cd spotify/

makepkg -si

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

[Razorclaw · Accepted solution]

I just noticed this post which confirms Spotify's new UI uses AVX instructions and considering our old (but still good!) CPUs lack the required extension, we're out of luck.

[mcdragon]

May I also add that I found the package here https://mirror.twds.com.tw/armbian-apt/pool/bookworm-desktop/s/spotify-client/ but I had to physically rename it to spotify-1.2.45.454-gc16ec9f6-x86_64.deb and then run makepkg -si

The snap or flatpak versions have not worked for me
I also added/amended  IgnorePkg=spotify in /etc/pacman.conf to prevent the package from being updated by the helper.

This whole using the old version of spotify unfortunately might not work forever as at one point the backend will be refused on older versions of the app

[Exord]

Dear developers, please look into this problem, I receive a ton of core files every day. I don't really need to pollute the disk with this. 

It costs you nothing to add a few checks for avx2 instructions, and simply not use them if the system does not support them. 

Background:
Debian Stable.

[sergiomb]

https://community.spotify.com/t5/Desktop-Linux/The-app-crashes-on-Debian-due-to-HW-acceleration/m-p/...

spotify --no-zygote

i.e. fix is a option send to chromium https://codereview.chromium.org/2384163002 and can be a chromium problem not a spotify problem

[rokejulianlockhart]

---

@Razorclaw wrote:

I just noticed this post which confirms Spotify's new UI uses AVX instructions and considering our old (but still good!) CPUs lack the required extension, we're out of luck.

---

I'm using a new AMD Ryzen 5 7600X, so I doubt that this is the cause (if my issue matches this).

[rokejulianlockhart]

---

@sergiomb wrote:

https://community.spotify.com/t5/Desktop-Linux/The-app-crashes-on-Debian-due-to-HW-acceleration/m-p/...

spotify --no-zygote

i.e. fix is a option send to chromium https://codereview.chromium.org/2384163002 and can be a chromium problem not a spotify problem

---

How did you ascertain this?

[sergiomb]

I remembered a similar problem that occurred in 2021, as described in my previous message