Spotify Community

wschlich · 2024-11-25

Hi!

The spotify binary frequently dumps core on my Gentoo Linux laptop (x86_64, glibc-2.40, kernel 6.1.119).

It seems to only affect some child process, as Spotify itself (main window) keeps running and playing music.

Spotify binary (1.2.48, see https://packages.gentoo.org/packages/media-sound/spotify) from Ubuntu repo crashing:

2024-11-25 08:56:29 +01:00; zephyr; daemon.info; spotify[1039550]: *** stack smashing detected ***: terminated
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd-coredump[1039588]: Process 1039550 (spotify) of user 20001 terminated abnormally with signal 6/ABRT, processing...
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd[1]: Created slice Slice /system/systemd-coredump.
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd[1]: Started Process Core Dump (PID 1039588/UID 0).
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
2024-11-25 08:56:30 +01:00; zephyr; local0.crit; systemd-coredump[1039589]: Process 1039550 (spotify) of user 20001 dumped core.

[...]

Stack trace of thread 1039550:
#0 0x00007f7e483d3f4c n/a (libc.so.6 + 0x8bf4c)
#1 0x00007f7e48384336 raise (libc.so.6 + 0x3c336)
#2 0x00007f7e4836c8f7 abort (libc.so.6 + 0x248f7)
#3 0x00007f7e4836d96f n/a (libc.so.6 + 0x2596f)
#4 0x00007f7e48449c5b __fortify_fail (libc.so.6 + 0x101c5b)
#5 0x00007f7e4844adc6 __stack_chk_fail (libc.so.6 + 0x102dc6)
#6 0x000056347aa83d7d n/a (spotify + 0xd58d7d)
#7 0x00007f7e4836e470 n/a (libc.so.6 + 0x26470)
#8 0x00007f7e4836e529 __libc_start_main (libc.so.6 + 0x26529)
#9 0x000056347aa8266e _start (spotify + 0xd5766e)

Stack trace of thread 1039551:
#0 0x00007f7e483cebfe n/a (libc.so.6 + 0x86bfe)
#1 0x00007f7e483d177a pthread_cond_timedwait (libc.so.6 + 0x8977a)
#2 0x00007f7e5001acbe n/a (libcef.so + 0x6a1acbe)
#3 0x00007f7e500444fd n/a (libcef.so + 0x6a444fd)
#4 0x00007f7e4ffc1f6c n/a (libcef.so + 0x69c1f6c)
#5 0x00007f7e50001b4d n/a (libcef.so + 0x6a01b4d)
#6 0x00007f7e50001cd4 n/a (libcef.so + 0x6a01cd4)
#7 0x00007f7e5001b3a7 n/a (libcef.so + 0x6a1b3a7)
#8 0x00007f7e483d2270 n/a (libc.so.6 + 0x8a270)
#9 0x00007f7e4843dfec n/a (libc.so.6 + 0xf5fec)

Stack trace of thread 1039554:
#0 0x00007f7e483cebfe n/a (libc.so.6 + 0x86bfe)
#1 0x00007f7e483d1442 pthread_cond_wait (libc.so.6 + 0x89442)
#2 0x00007f7e5001ab96 n/a (libcef.so + 0x6a1ab96)
#3 0x00007f7e500444d3 n/a (libcef.so + 0x6a444d3)
#4 0x00007f7e4ffc1f6c n/a (libcef.so + 0x69c1f6c)
#5 0x00007f7e4fffe16d n/a (libcef.so + 0x69fe16d)
#6 0x00007f7e4fffd9e9 n/a (libcef.so + 0x69fd9e9)
#7 0x00007f7e4fffd68d n/a (libcef.so + 0x69fd68d)
#8 0x00007f7e4fffd59d n/a (libcef.so + 0x69fd59d)
#9 0x00007f7e5001b3a7 n/a (libcef.so + 0x6a1b3a7)
#10 0x00007f7e483d2270 n/a (libc.so.6 + 0x8a270)
#11 0x00007f7e4843dfec n/a (libc.so.6 + 0xf5fec)

Stack trace of thread 1039553:
#0 0x00007f7e483cebfe n/a (libc.so.6 + 0x86bfe)
#1 0x00007f7e483d1442 pthread_cond_wait (libc.so.6 + 0x89442)
#2 0x00007f7e5001ab96 n/a (libcef.so + 0x6a1ab96)
#3 0x00007f7e500444d3 n/a (libcef.so + 0x6a444d3)
#4 0x00007f7e4ffc1f6c n/a (libcef.so + 0x69c1f6c)
#5 0x00007f7e4fffe16d n/a (libcef.so + 0x69fe16d)
#6 0x00007f7e4fffd9e9 n/a (libcef.so + 0x69fd9e9)
#7 0x00007f7e4fffd68d n/a (libcef.so + 0x69fd68d)
#8 0x00007f7e4fffd59d n/a (libcef.so + 0x69fd59d)
#9 0x00007f7e5001b3a7 n/a (libcef.so + 0x6a1b3a7)
#10 0x00007f7e483d2270 n/a (libc.so.6 + 0x8a270)
#11 0x00007f7e4843dfec n/a (libc.so.6 + 0xf5fec)
ELF object binary architecture: AMD x86-64

2024-11-25 08:56:30 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Deactivated successfully.
2024-11-25 08:56:30 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Consumed 444ms CPU time, 134.4M memory peak.
2024-11-25 08:56:30 +01:00; zephyr; user.debug; drkonqi-coredump-processor[1039590]: "/opt/spotify/spotify-client/spotify" 1039550 "/var/lib/systemd/coredump/core.spotify.20001.f45496c8d78c4de9a2655cca19bf4157.1039550.1732521389000000.zst"
2024-11-25 08:56:30 +01:00; zephyr; daemon.info; systemd[3818]: Started Launch DrKonqi for a systemd-coredump crash (PID 1039590/UID 0).
2024-11-25 08:56:30 +01:00; zephyr; user.warning; drkonqi-coredump-launcher[1039596]: Unable to find file for pid 1039550 expected at "kcrash-metadata/spotify.f45496c8d78c4de9a2655cca19bf4157.1039550.ini"
2024-11-25 08:56:30 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Deactivated successfully.
2024-11-25 08:56:30 +01:00; zephyr; user.warning; drkonqi-coredump-launcher[1039596]: Nothing handled the dump 😮

Spotify Snap (1.2.48.405.gf2c48e6f) binary crashing:

2024-11-25 12:05:02 +01:00; zephyr; daemon.info; systemd-coredump[1068063]: Process 1067952 (spotify) of user 20001 terminated abnormally with signal 6/ABRT, processing...
2024-11-25 12:05:02 +01:00; zephyr; daemon.info; systemd[1]: Started Process Core Dump (PID 1068063/UID 0).
2024-11-25 12:05:02 +01:00; zephyr; daemon.info; systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
2024-11-25 12:05:03 +01:00; zephyr; local0.crit; systemd-coredump[1068064]: Process 1067952 (spotify) of user 20001 dumped core.

Stack trace of thread 1067952:
#0 0x00007f521189f00b n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64

2024-11-25 12:05:03 +01:00; zephyr; user.debug; drkonqi-coredump-processor[1068065]: "/snap/spotify/80/usr/share/spotify/spotify" 1067952 "/var/lib/systemd/coredump/core.spotify.20001.f45496c8d78c4de9a2655cca19bf4157.1067952.1732532702000000.zst"
2024-11-25 12:05:03 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Deactivated successfully.
2024-11-25 12:05:03 +01:00; zephyr; daemon.info; systemd[3818]: Started Launch DrKonqi for a systemd-coredump crash (PID 1068065/UID 0).
2024-11-25 12:05:03 +01:00; zephyr; user.warning; drkonqi-coredump-launcher[1068071]: Unable to find file for pid 1067952 expected at "kcrash-metadata/spotify.f45496c8d78c4de9a2655cca19bf4157.1067952.ini"
2024-11-25 12:05:03 +01:00; zephyr; user.warning; drkonqi-coredump-launcher[1068071]: Nothing handled the dump 😮
2024-11-25 12:05:03 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Deactivated successfully.

Kernel info (.config attached):

zephyr ~ # uname -a

Linux zephyr 6.1.119-gentoo-x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 23 11:53:09 CET 2024 x86_64 Intel(R) Core(TM)**bleep** GenuineIntel GNU/Linux
zephyr ~ #

If you need any more info, please let me know.

Cheers,

Wolfram

sergiomb · 2025-02-06

from

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

View solution in original post

BBHarris · 2024-11-26

I'm having the exact same issue on Arch with the spotify-launcher package. Spotify runs just fine and nothing seems untoward, but upon checking my coredump history for other reasons I found it littered with coredumps from Spotify as far back as my records go (beginning of August). Every day that I use Spotify it will create about 5-10 coredumps. Every one is caused by a SIGABRT. This has been occurring over multiple versions of Spotify at least as far back as August, including my current version 1.2.50.335.

Here's a representative log for one such coredump:

           PID: 6153 (spotify)
           UID: 1000 (anon)
           GID: 1000 (anon)
        Signal: 6 (ABRT)
     Timestamp: Mon 2024-11-25 19:14:57 GMT (4h 45min ago)
  Command Line: $'/home/anon/.local/share/spotify-launcher/install/usr/share/spotify/spotify --type=utility --utility-sub-type=patch.mojom.FilePatcher --lang=en-US --service-sandbox-type=service --no-sandbox --string-annotations --enable-crash-reporter=, --change-stack-guard-on-fork=enable --user-data-dir=/home/anon/.cache/spotify --log-severity=disable --user-agent-product=Chrome/129.0.6668.90 Spotify/1.2.50.335 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,13039243201217149699,10340549120591809704,262144 --disable-features=BackForwardCache,EyeDropper,PartitionAllocDanglingPtr,PartitionAllocUnretainedDanglingPtr --variations-seed-version'
    Executable: /home/anon/.local/share/spotify-launcher/install/usr/share/spotify/spotify
 Control Group: /user.slice/user-1000.slice/**bleep**/app.slice/**bleep**
          Unit:**bleep**
     User Unit:**bleep**
         Slice: user-1000.slice
     Owner UID: 1000 (anon)
      Hostname: anon
       Storage: /var/lib/systemd/coredump/core.spotify.1000.84f6dc54ee974fbb8e77ebfcbcb86744.6153.1732562097000000.zst (present)
  Size on Disk: 5.6M
       Message: Process 6153 (spotify) of user 1000 dumped core.
                
                Stack trace of thread 6153:
                #0  0x000076747b5f43f4 n/a (libc.so.6 + 0x963f4)
                #1  0x000076747b59b120 raise (libc.so.6 + 0x3d120)
                #2  0x000076747b5824c3 abort (libc.so.6 + 0x244c3)
                #3  0x000076747b583354 n/a (libc.so.6 + 0x25354)
                #4  0x000076747b683799 __fortify_fail (libc.so.6 + 0x125799)
                #5  0x000076747b684a54 __stack_chk_fail (libc.so.6 + 0x126a54)
                #6  0x00006471728a80e9 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

If Spotify is launched from the terminal, the following is a typical output when the coredumps occur:

[2024-11-25T19:13:56Z INFO  spotify_launcher::config] Loading configuration file at "/etc/spotify-launcher.conf"
[2024-11-25T19:13:56Z INFO  spotify_launcher] No update needed
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated

BBHarris · 2024-11-26

Having the exact same issue on Arch. I made a larger post with logs, but it was removed for spam. I've notified a moderator, so hopefully it gets put back.

Arkasha · 2024-12-04

I am having the same problem on Linux Mint 22. I have Spotify version 1.2.50.335.g5e2860a8 installed from the Debian package on your Linux download page. It is crashing at least 5 times a day, often more than 10, but with no noticeable effect on playing music.

===================================================================
 Info                                                              
===================================================================
           PID: 3545033 (spotify)
           UID: 1000 (tstebbens)
           GID: 1000 (tstebbens)
        Signal: 6 (ABRT)
     Timestamp: Wed 2024-12-04 09:22:09 GMT (5min ago)
  Command Line: $'/usr/share/spotify/spotify --type=utility --utility-sub-type=data_decoder.mojom.DataDecoderService --lang=en-US --service-sandbox-type=service --no-sandbox --enable-crash-reporter=, --change-stack-guard-on-fork=enable --user-data-dir=/home/tstebbens/.cache/spotify --log-severity=disable --user-agent-product=Chrome/128.0.6613.138 Spotify/1.2.48.405 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,12820385870385600885,11368080563985126104,262144 --disable-features=BackForwardCache,PartitionAllocDanglingPtr,PartitionAllocUnretainedDanglingPtr --variations-seed-version'
    Executable: /usr/share/spotify/spotify
 Control Group: /user.slice/user-1000.slice/session-c2.scope
          Unit: session-c2.scope
         Slice: user-1000.slice
       Session: c2
     Owner UID: 1000 (tstebbens)
       Boot ID: f2a33cabb3ac47d5b3fc3b14a0ffaed6
    Machine ID: eb97c9c3e2a14dcfab9ba733f28cd7c4
      Hostname: pc-terry
       Storage: /var/lib/systemd/coredump/core.spotify.1000.f2a33cabb3ac47d5b3fc3b14a0ffaed6.3545033.1733304129000000.zst (present)
  Size on Disk: 4.7M
       Message: Process 3545033 (spotify) of user 1000 dumped core.
                
                Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64
                Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.4.amd64
                Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
                Module libatomic.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
                Stack trace of thread 3545033:
                #0  0x00007ca845c9eb1c __pthread_kill_implementation (libc.so.6 + 0x9eb1c)
                #1  0x00007ca845c4526e __GI_raise (libc.so.6 + 0x4526e)
                #2  0x00007ca845c288ff __GI_abort (libc.so.6 + 0x288ff)
                #3  0x00007ca845c297b6 __libc_message_impl (libc.so.6 + 0x297b6)
                #4  0x00007ca845d36c19 __GI___fortify_fail (libc.so.6 + 0x136c19)
                #5  0x00007ca845d37ea4 __stack_chk_fail (libc.so.6 + 0x137ea4)
                #6  0x00005d9d39086d7d n/a (/usr/share/spotify/spotify (deleted) + 0xd58d7d)
                #7  0x00005d9d3c8cbf98 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64
===================================================================
 GDB Log                                                           
===================================================================

warning: Can't open file /usr/share/spotify/spotify (deleted) during file-backed mapping note processing

warning: Can't open file /dev/shm/.org.chromium.Chromium.NDFSER (deleted) during file-backed mapping note processing

warning: Can't open file /usr/share/spotify/icudtl.dat (deleted) during file-backed mapping note processing

warning: Can't open file /dev/shm/.org.chromium.Chromium.N6TgKE (deleted) during file-backed mapping note processing

warning: Can't open file /dev/shm/.org.chromium.Chromium.ok8DuJ (deleted) during file-backed mapping note processing

warning: Can't open file /usr/share/spotify/v8_context_snapshot.bin (deleted) during file-backed mapping note processing

warning: Can't open file /usr/share/spotify/libcef.so (deleted) during file-backed mapping note processing
[New LWP 3545033]
[New LWP 3545036]
[New LWP 3545034]
[New LWP 3545037]
Core was generated by `/usr/share/spotify/spotify --type=utility --utility-sub-type=data_decoder.mojom'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007ca845c9eb1c in ?? ()
[Current thread is 1 (LWP 3545033)]

===================================================================
 GDB Backtrace                                                     
===================================================================

warning: Can't open file /usr/share/spotify/spotify (deleted) during file-backed mapping note processing

warning: Can't open file /dev/shm/.org.chromium.Chromium.NDFSER (deleted) during file-backed mapping note processing

warning: Can't open file /usr/share/spotify/icudtl.dat (deleted) during file-backed mapping note processing

warning: Can't open file /dev/shm/.org.chromium.Chromium.N6TgKE (deleted) during file-backed mapping note processing

warning: Can't open file /dev/shm/.org.chromium.Chromium.ok8DuJ (deleted) during file-backed mapping note processing

warning: Can't open file /usr/share/spotify/v8_context_snapshot.bin (deleted) during file-backed mapping note processing

warning: Can't open file /usr/share/spotify/libcef.so (deleted) during file-backed mapping note processing
[New LWP 3545033]
[New LWP 3545036]
[New LWP 3545034]
[New LWP 3545037]
Core was generated by `/usr/share/spotify/spotify --type=utility --utility-sub-type=data_decoder.mojom'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007ca845c9eb1c in ?? ()
[Current thread is 1 (LWP 3545033)]
#0  0x00007ca845c9eb1c in ?? ()
#1  0x00007ffcb46a5090 in ?? ()
#2  0xe789de0227733a00 in ?? ()
#3  0x0000000000000000 in ?? ()

===================================================================
 GDB Backtrace (all threads)                                       
===================================================================

warning: Can't open file /usr/share/spotify/spotify (deleted) during file-backed mapping note processing

warning: Can't open file /dev/shm/.org.chromium.Chromium.NDFSER (deleted) during file-backed mapping note processing

warning: Can't open file /usr/share/spotify/icudtl.dat (deleted) during file-backed mapping note processing

warning: Can't open file /dev/shm/.org.chromium.Chromium.N6TgKE (deleted) during file-backed mapping note processing

warning: Can't open file /dev/shm/.org.chromium.Chromium.ok8DuJ (deleted) during file-backed mapping note processing

warning: Can't open file /usr/share/spotify/v8_context_snapshot.bin (deleted) during file-backed mapping note processing

warning: Can't open file /usr/share/spotify/libcef.so (deleted) during file-backed mapping note processing
[New LWP 3545033]
[New LWP 3545036]
[New LWP 3545034]
[New LWP 3545037]
Core was generated by `/usr/share/spotify/spotify --type=utility --utility-sub-type=data_decoder.mojom'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007ca845c9eb1c in ?? ()
[Current thread is 1 (LWP 3545033)]

Thread 4 (LWP 3545037):
#0  0x00007ca845c98d61 in ?? ()
No symbol table info available.
#1  0xaaaaaaaaaaaaaaaa in ?? ()
No symbol table info available.
#2  0x0000000000000000 in ?? ()
No symbol table info available.

Thread 3 (LWP 3545034):
#0  0x00007ca845c98d61 in ?? ()
No symbol table info available.
#1  0x00007ca8443fdfe0 in ?? ()
No symbol table info available.
#2  0x00007ca8443fde30 in ?? ()
No symbol table info available.
#3  0x00007ca8443fdf40 in ?? ()
No symbol table info available.
#4  0x0000008900000000 in ?? ()
No symbol table info available.
#5  0x0000000000000000 in ?? ()
No symbol table info available.

Thread 2 (LWP 3545036):
#0  0x00007ca845c98d61 in ?? ()
No symbol table info available.
#1  0xaaaaaaaaaaaaaa00 in ?? ()
No symbol table info available.
#2  0x0000000000000000 in ?? ()
No symbol table info available.

Thread 1 (LWP 3545033):
#0  0x00007ca845c9eb1c in ?? ()
No symbol table info available.
#1  0x00007ffcb46a5090 in ?? ()
No symbol table info available.
#2  0xe789de0227733a00 in ?? ()
No symbol table info available.
#3  0x0000000000000000 in ?? ()
No symbol table info available.
#0  0x00007ca845c9eb1c in ?? ()
#1  0x00007ffcb46a5090 in ?? ()
#2  0xe789de0227733a00 in ?? ()
#3  0x0000000000000000 in ?? ()

wschlich · 2024-12-04

Crashes still occurring with spotify-client 1.2.50 from the spotify repo https://repository-origin.spotify.com/pool/non-free/s/spotify-client/

0x7070 · 2024-12-10

I'm having a similar `stack smashing` issue.

As `BBHarris` pointed out earlier in this thread, this occurs when Spotify is run from within a terminal. Additionally, as others have mentioned, this seemingly only affects child processes and does not appear to affect functionality within the app. Still, I am consistently receiving the same `*** stack smashing detected ***: terminated` error being repeatedly outputted to any terminal currently within focus.

The crash logs suggested some package issues (namely libexpat1), which I fully updated, pointing the issue elsewhere.

Ubuntu version: 24.04.01
Spotify-client version: 1:1.2.50.335.g5e2860a8
Spotify-desktop-client version: 0.9.17.8.gd06432d.31-1
Libexpat1 version: 2.6.1-2ubuntu0.2

Not a fatal issue, but no one likes issues!

wschlich · 2024-12-10

When will Spotify wake up and analyse this issue? 👨‍🔧

Myoldmopar · 2024-12-13

I'm glad to see I'm not the only one encountering this in a recent version of the app. I'm happy to provide any more details or debugging assistance as this is pretty darn easy to reproduce.

wschlich · 2024-12-21

Crashes still occurring with spotify-client 1.2.52 from the spotify repo https://repository-origin.spotify.com/pool/non-free/s/spotify-client/

MisterJesus · 2024-12-29

Hello,
I have the same issue described on Manjaro (Arch) and MX-Linux (Debian).

Launching from terminal keeps reproducing the error over and over:

[jesuslinux@A9410 ~]$ spotify
*** stack smashing detected ***: terminated

The app behaves normal and plays music.

I came here looking for answers and fixes.

zouo · 2025-01-02

Running spotify-launcher 0.6.1-1 from the official Arch repository with kernel 6.12.7

```

$ spotify-launcher -vv
[2025-01-02T16:24:00Z DEBUG spotify_launcher::config] Searching for configuration file at "/home/mirai/.config/spotify-launcher.conf"
[2025-01-02T16:24:00Z DEBUG spotify_launcher::config] Searching for configuration file at "/etc/spotify-launcher.conf"
[2025-01-02T16:24:00Z DEBUG spotify_launcher::config] Found configuration file at "/etc/spotify-launcher.conf"
[2025-01-02T16:24:00Z INFO spotify_launcher::config] Loading configuration file at "/etc/spotify-launcher.conf"
[2025-01-02T16:24:00Z DEBUG spotify_launcher] Using install path: "/home/mirai/.local/share/spotify-launcher/install"
[2025-01-02T16:24:00Z DEBUG spotify_launcher::paths] Reading state file from "/home/mirai/.local/share/spotify-launcher/state.json"...
[2025-01-02T16:24:00Z DEBUG spotify_launcher::paths] Loaded state: Ok(State { version: "1:1.2.52.442.g01893f92", last_update_check: SystemTime { tv_sec: 1735833608, tv_nsec: 776118365 } })
[2025-01-02T16:24:00Z DEBUG spotify_launcher] Last update check was 0 days and 0 hours ago
[2025-01-02T16:24:00Z INFO spotify_launcher] No update needed
[2025-01-02T16:24:00Z DEBUG spotify_launcher] Assembled command: ["spotify"]
*** stack smashing detected ***: terminated
```

often the app launcher properly but after restarting it it begins to faulter, requiring a reboot.

Django76 · 2025-01-25

Linux Mint 22.1, Spotify installed from their official repo. Few coredumps per day in syslog. Same as for Arkasha - no noticeable effect on playing music. But no one likes crashes in log...

ibonk42 · 2025-02-01

I was also constantly having this issue. I ended up adding spotify to the abrt blacklist.

What I did was:
sudo vim /etc/abrt/abrt.conf

or

sudo nano /etc/abrt/abrt.conf

Add this to the end of the file:
BlackList = spotify

Then restart the abrt service:

sudo systemctl restart abrt.service

bigbrew · 2025-02-01

I am also affected by the issue described here. Installed from the official Spotify Debian repo.

wschlich · 2025-02-01

1.2.53 still crashes:

Feb 1 20:54:59 localhost drkonqi-coredump-launcher: Unable to find file for pid 92372 expected at "kcrash-metadata/spotify.cd4ff9a826054e85a0ddcf0121056061.92372.ini"
Feb 1 20:54:59 localhost drkonqi-coredump-launcher: Nothing handled the dump 😮
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Unable to find file for pid 92450 expected at "kcrash-metadata/spotify.cd4ff9a826054e85a0ddcf0121056061.92450.ini"
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Unable to find file for pid 92413 expected at "kcrash-metadata/spotify.cd4ff9a826054e85a0ddcf0121056061.92413.ini"
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Unable to find file for pid 92420 expected at "kcrash-metadata/spotify.cd4ff9a826054e85a0ddcf0121056061.92420.ini"
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Unable to find file for pid 92431 expected at "kcrash-metadata/spotify.cd4ff9a826054e85a0ddcf0121056061.92431.ini"
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Nothing handled the dump 😮
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Nothing handled the dump 😮
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Nothing handled the dump 😮
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Nothing handled the dump 😮
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Unable to find file for pid 92458 expected at "kcrash-metadata/spotify.cd4ff9a826054e85a0ddcf0121056061.92458.ini"
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Unable to find file for pid 92439 expected at "kcrash-metadata/spotify.cd4ff9a826054e85a0ddcf0121056061.92439.ini"
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Nothing handled the dump 😮
Feb 1 20:55:08 localhost drkonqi-coredump-launcher: Nothing handled the dump 😮

tm-craggs · 2025-02-04

Same issue on Fedora 41 with Spotify Flatpak version 1.2.52.442

Spotify killed by SIGABRT is the error title.

rokejulianlockhart · 2025-02-06

Does anyone have any idea whether https://bugzilla.rpmfusion.org/show_bug.cgi?id=7143#c5 is an example of this issue? I'm under the impression that it's separate, but not confident. Apologies for wasting time if so.

rokejulianlockhart · 2025-02-06

Have you reported this to Gentoo's Bugzilla?

sergiomb · 2025-02-06

from

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

BBHarris · 2025-02-09

This seems to have fixed the issue for me. Since I'm using spotify-launcher from the Arch repos, I put

extra_arguments = ["--no-zygote"]

into /etc/spotify-launcher.conf. I've not had any more coredumps in the last few days.

Spotify Community

Help categories

Account & Payment

Using Spotify

Listen Everywhere

Spotify binary frequently crashing and dumping core (Ubuntu binary + Snap)

Spotify binary frequently crashing and dumping core (Ubuntu binary + Snap)

Photos

Suggested posts

Let's introduce ourselves!

Help Wizard

Step 1

Just quickly...

FAQs

Ongoing Issues

Help categories

Account & Payment

Using Spotify

Listen Everywhere

Spotify binary frequently crashing and dumping core (Ubuntu binary + Snap)

Spotify binary frequently crashing and dumping core (Ubuntu binary + Snap)

Photos

Suggested posts

Let's introduce ourselves!