Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spotify crashes when adding a music source #140

Open
soaringowl2145 opened this issue Sep 28, 2020 · 9 comments
Open

Spotify crashes when adding a music source #140

soaringowl2145 opened this issue Sep 28, 2020 · 9 comments

Comments

@soaringowl2145
Copy link

soaringowl2145 commented Sep 28, 2020

I am using Debian 10 Buster with Gnome XORG with Nvidia proprietary graphics driver.

When I click "ADD A SOURCE" from the LOCAL FILES submenu the entire app closes.

@betocoutinho
Copy link

This is happening to me also on ubuntu 20.04 in the flatpak version.

@natejank
Copy link

This also happens on Fedora Workstation 33, with Intel graphics, on GNOME wayland and x11. From my perspective, it tries to spawn a file browser window, but fails to load it and kills both windows. There is no log output by spotify itself upon the crash, even when the --show-console flag is used.

@soaringowl2145
Copy link
Author

Even the Snap version does this on Ubuntu

@tosziro
Copy link

tosziro commented Dec 7, 2020

Same on Ubuntu 20.10

@soaringowl2145
Copy link
Author

Upon further inspection, this might be a GNOME issue as I have tried on MATE and openbox and those both work fine. Only GNOME seems to not work.

@natejank
Copy link

Now on Ubuntu 20.04, this happens to me on the snap, deb, and flatpak. I think it's an upstream problem where at some point GNOME's xdg desktop portal support was broken, and it hasn't been fixed because Linux is an unsupported platform. There doesn't seem to be a way to manually add a path using plain text configuration, but I have been able to downgrade to a version before the portal was broken, set a path, and upgrade again.

@Zlopez
Copy link

Zlopez commented Jan 21, 2021

I can confirm this is also happening on Fedora 33 Silverblue.

@shaicoleman
Copy link

shaicoleman commented Jan 26, 2021

This is an upstream bug in the latest version of the app (not caused by Flatpak). The workaround is to temporarily revert to an older version:

# Clear Spotify configuration if downgrading from a newer version
rm -rf ~/.var/app/com.spotify.Client/
# Revert to version 1.1.26.501.gbe11e53b
sudo flatpak update --commit=ca4fd2d20d5b3188e31d7ecff120ed8be818cd7d4b32b56229c97db12c65a1ea com.spotify.Client
# Allow access to the home directory
sudo flatpak override com.spotify.Client --filesystem=home
# Optionally, prevent automatic updates
sudo flatpak mask com.spotify.Client

Optionally, upgrade to a newer version after configuring the local directory:

# Enable automatic updates
sudo flatpak mask --remove com.spotify.Client
# Update spotify
sudo flatpak update

@shaicoleman
Copy link

shaicoleman commented Mar 23, 2021

With the latest version, it seems to be fixed now. You still need to grant access to the filesystem

sudo flatpak override com.spotify.Client --filesystem=home

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants