Closed Aivech closed 5 months ago
The last log line is from the spotify binary, so it seems the launcher is working correctly. I tried on my own computer and it seems to be working fine.
I can't really provide support beyond this, the spotify-launcher
is no longer executing at this point, you need to figure out which part of your system the spotify binary can't deal with, and then fix it.
You can either try strace -f spotify-launcher --skip-update
to get an idea of what's going on, or have a look at the other github issues, since some common misconfigurations are already documented there.
Somebody has reported this kind of behavior when using hyprland: #48
The solution may be configuring the ozone
flags in ~/.config/spotify-launcher.conf
.
[aivech@2cube ~]$ spotify-launcher
[2024-07-19T06:06:57Z INFO spotify_launcher::config] Loading configuration file at "/home/aivech/.config/spotify-launcher.conf"
[2024-07-19T06:06:57Z INFO spotify_launcher] No update needed
[0719/020658.018715:WARNING:main_runner.cc(261)] Alloy bootstrap is deprecated and will be removed in ~M127. See https://github.com/chromiumembedded/cef/issues/3685
[aivech@2cube ~]$ cat ~/.config/spotify-launcher.conf
[spotify]
extra_arguments = ["--enable-features=UseOzonePlatform", "--ozone-platform=wayland"]
I've created the file as specified, to no effect. Also the launcher works fine on another computer with a nearly identical Wayland setup.
If anyone else finds this issue, especially if spotify was previously working on the same PC:
Try deleting ~/.cache/spotify/
.
Program exits without ever launching Spotify.