Spotify crashes with SIGSEGV after spicetify apply (works after spicetify restore) #3711
Closed as not planned
Description
Environment
| Distro | CachyOS Linux (Arch-based, rolling) |
| Kernel | 6.19.3-2-cachyos |
| Spicetify version | 2.42.10 |
| spotify-launcher version | 0.6.5 |
| Spotify (backup) version | 1.2.82.428.g0ac8be2b |
| Spotify path | /home/vyrx/.local/share/spotify-launcher/install/usr/share/spotify |
Description
After running spicetify apply, Spotify crashes immediately on launch with a SIGSEGV (segmentation fault). Running spicetify restore fixes the issue — Spotify works normally after restoring.
Steps to Reproduce
- Run
spicetify apply - Launch Spotify via
spotify-launcher - Spotify crashes with SIGSEGV
Expected Behavior
Spotify launches normally with spicetify patches applied.
Actual Behavior
Spotify terminates with a segmentation fault immediately on launch.
Crash Output
~ ❯ spotify-launcher
[2026-02-24T02:39:42Z INFO spotify_launcher::config] Loading configuration file at "/etc/spotify-launcher.conf"
[2026-02-24T02:39:42Z INFO spotify_launcher] No update needed
(spotify:200683): libayatana-appindicator-WARNING **: 08:09:42.847: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.
[0224/080943.809774:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0224/080943.810289:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0224/080943.825082:ERROR:third_party/crashpad/crashpad/util/file/directory_reader_posix.cc:43] opendir /home/vyrx/.cache/spotify/attachments/5b378f42-ad98-437f-bb87-53cad11e64a8: No such file or directory (2)
fish: Job 1, 'spotify-launcher' terminated by signal SIGSEGV (Address boundary error)
Spicetify Config
current_theme (none)
inject_theme_js 1
replace_colors 1
overwrite_assets 0
inject_css 1
disable_ui_logging 1
remove_rtl_rule 1
expose_apis 1
disable_sentry 1
experimental_features 1
Additional Notes
- The crashpad error (
tag not found) and the missing attachments directory appear to be related to the crash handler itself failing, which may point to a binary patching issue introduced byspicetify apply. - No custom theme or extensions are configured — base apply only.