Announcements

Help Wizard

Step 1

NEXT STEP

Spotify SIGSEV

Spotify SIGSEV

Device

  • ThinkPad T15 Gen 1

OS

  • CachyOS (Linux kernel 6.18), Wayland (Sway / SwayFX)

Software

  • Spotify package: 1:1.2.82.428-1 (AUR)
  • spicetify: 2.42.10

Summary

  • After applying spicetify, Spotify briefly opens with only three dots in the top-right and then exits with SIGSEGV. Restoring spicetify makes Spotify run normally.

Observed output (most relevant lines):
(spotify:80738): Gtk-WARNING **: …: Theme parsing error: gtk.css:1048:16: 'border-spacing' is not a valid property name (spotify:80738): libayatana-appindicator-WARNING **: …: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code. [0218/014424.650809:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found fish: Job 1, 'spotify' terminated by signal SIGSEGV (Address boundary error)

Why I think this is spicetify-related

  • Spotify launches and runs correctly after running: spicetify restore
  • Spotify crashes immediately after spicetify apply
  • spicetify config shows injects enabled and preprocesses that modify runtime behavior

spicetify config (excerpt)

  • spicetify -v: 2.42.10
  • spotify_path: /opt/spotify/
  • prefs_path: /home/lunix/.config/spotify/prefs
  • inject_theme_js: 1
  • inject_css: 1
  • replace_colors: 1
  • overwrite_assets: 0
  • Preprocesses: disable_sentry=1, disable_ui_logging=1, remove_rtl_rule=1, expose_apis=1

Steps to reproduce

  1. Install Spotify v1.2.82.428-1 from AUR
  2. Install spicetify-cli 2.42.10 and run "spicetify backup apply"
  3. Launch Spotify — it opens briefly and then crashes with SIGSEGV
  4. Restore stock Spotify (spicetify restore) — Spotify launches normally

Files/logs pasted (please request if more needed)

  • Full terminal run log (GTK_DEBUG=all spotify 2>&1 | tee spotify-run.log):

    (spotify:81700): Gtk-WARNING **: 01:59:22.260: GTK_DEBUG set but ignored because gtk isn't built with G_ENABLE_DEBUG

    (spotify:81700): Gtk-WARNING **: 01:59:22.291: Theme parsing error: gtk.css:1048:16: 'border-spacing' is not a valid property name

    (spotify:81700): libayatana-appindicator-WARNING **: 01:59:23.027: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.
    [0218/015924.716948:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
    [0218/015924.717401:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
    fish: Process 81700, 'spotify' from job 1, 'GTK_DEBUG=all spotify 2>&1 | te…' terminated by signal SIGSEGV (Address boundary error)

  • spicetify config dump (spicetify config):

    Settings
    always_enable_devtools 0
    spotify_path /opt/spotify/
    prefs_path /home/lunix/.config/spotify/prefs
    current_theme
    inject_theme_js 1
    inject_css 1
    replace_colors 1
    overwrite_assets 0
    spotify_launch_flags
    color_scheme
    check_spicetify_update 1

    Preprocesses
    disable_sentry 1
    disable_ui_logging 1
    remove_rtl_rule 1
    expose_apis 1

    AdditionalFeatures
    sidebar_config 0
    home_config 1
    experimental_features 1
    extensions
    custom_apps

    Backup
    version 1.2.82.428.g0ac8be2b
    with 2.42.10

  • spotify >$HOME/spotify-dump.txt 2>&1:

    fish: Job 1, 'spotify >$HOME/spotify-dump.txt…' terminated by signal SIGSEGV (Address boundary error)

Notes on the observed messages

  • The GTK css warning ('border-spacing' invalid) and libayatana-appindicator deprecation are warnings and unlikely to cause a native SIGSEGV by themselves.
  • The Crashpad ELF error ("tag not found") and the SIGSEGV are the actionable crash indicators; these appear only after spicetify apply in my environment.

What I’m requesting

  • Investigation into whether spicetify-modified resources or runtime injections cause a segmentation fault with this Spotify build (1.2.82.428-1).
  • Guidance on which patched/overwritten resources to revert if you need to reproduce the crash locally.

Environment details (for debugging)

  • Kernel: Linux 6.18
  • Window manager: Sway (Wayland)
  • Installed dependencies per pacman for spotify: alsa-lib, gtk3, libxss, desktop-file-utils, openssl, nss, at-spi2-atk, libcurl-gnutls, libsm, libayatana-appindicator
  • I can provide the full spotify-run.log and the Backup/Patched file listing on request.

If you want more logs attached here, tell me which exact files you need and I’ll paste them.

Reply
2 Replies

I am getting the same error on Arch Linux, the relevant issue:

https://github com/spicetify/cli/issues/3695

Update: this was fixed in a subsequent update, either from Spotify or Spicetify (I don't remember)

However I am still concerned, because getting a Segfault indicates that there is something not quite right in the internals

Suggested posts

Let's introduce ourselves!

Hey there you,   Yeah, you! 😁   Welcome - we're glad you joined the Spotify Community!   While you here, let's have a fun game and get…

ModeratorStaff / Moderator/ 4 years ago  in Social & Random