Constant coredump messages

[Ferlinuxdebian]

systemd-coredump is flooded with messages about spotify flatpak.
Fedora 41 Gnome-shell

[Erick555]

It's not flatpak issue. See upstream thread

[murkl]

Same here on Arch Linux

[Vitus-TL]

This seems to be a general issue for Spotify after version 1.2.45.454 no matter the distributions method (apt/snap/flatpak). Can someone make v1.2.45.454 (August 30, 2024.) available on a flatpak hub? Since it doesn't seems Spotify could be bothered with this.. Better even to retract newer versions, because of the carbon footprint of filling the logs with these core dumps... Rolling back to a previous working version is a good ITIL practice..

[djpeebles]

This seems to be a general issue...

I think it's possible to do this yourself through the command line.

# Get details of a flatpak (including commits) and downgrade to a particular commit
flatpak remote-info --log flathub com.spotify.Client
sudo flatpak update --commit=d22ab2f6059cca52bc56754ca1860fb41b0d9c6333975bd8f2eb375fde5a4d84 com.spotify.Client

[djpeebles]

This proposed solution has been posted on the Spotify community page about this problem. The flatpak command is

flatpak run com.spotify.Client --no-zygote

I've tried this and it works for me.

[djpeebles]

This proposed solution has been posted on the Spotify community page about this problem. The flatpak command is

flatpak run com.spotify.Client --no-zygote

I've tried this and it works for me.

I'm trying to add --no-zygote to the com.spotify.Client.desktop file that runs spotify when you click an icon but wherever I put it in the command below the application crashes as before (unlike the command above). Can anyone advise me how to do this?

Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=spotify --file-forwarding com.spotify.Client @@u %U @@

[guihkx]

@djpeebles You don't have to do it like that. As per the README, you can make launch options permanent by adding them to ~/.var/app/com.spotify.Client/config/spotify-flags.conf.

[djpeebles]

@guihkx That has worked - thank you! I'm assuming the reason why it wasn't working previously is that I hadn't run the command to enable the flags to run on Wayland.