@lightofpast
edit your spotify desktop file, it should be somewhere in /usr/share/applications, and it has a line that starts with Exec, that's where those arguments should go
Git Clone URL: | https://aur.archlinux.org/spotify.git (read-only, click to copy) |
---|---|
Package Base: | spotify |
Description: | A proprietary music streaming service |
Upstream URL: | https://www.spotify.com |
Licenses: | custom |
Submitter: | Foxboron |
Maintainer: | gromit (Antiz) |
Last Packager: | gromit |
Votes: | 214 |
Popularity: | 12.10 |
First Submitted: | 2023-02-09 22:51 (UTC) |
Last Updated: | 2025-05-19 14:19 (UTC) |
« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 19 Next › Last »
@lightofpast
edit your spotify desktop file, it should be somewhere in /usr/share/applications, and it has a line that starts with Exec, that's where those arguments should go
Hi all, is there anyway to start the program with "--enable-features=UseOzonePlatform --ozone-platform=wayland" flags automatically? The program seems to run in wayland with these arguments, so is there any configuration files that the application reads before launch (like spotify-flags.conf)?
@jaytau Just checked the checksums and they're correct. I'm unflagging the package.
@gromit Ok, sorry, seems to be a false alarm. Apparently, I first started Spotify but the window was somehow not there. The process continued to run though and so starting a new instance did nothing as it immediately quit.
@phuhl, I think the easiest you could do is to see if this problem is local to your user account or generally your system (i.e. create a new user and start spotify there).
@gromit Interesting, no for me that is all the output, then nothing happens. Any other output I can provide?
EDIT: nothing happens = spotify executable quits, no window was ever opened
@phuhl, works fine for me although there seems to be some cli output:
spotify 134 ↵
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
But afterwards spotify starts and works fine ... Do you get more output?
Seems there is a new version of libcurl-gnutls that is not compatible and prevents spotify from starting:
$ spotify
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
It was crashing on launch for me with
[0720/122312.041162:FATAL:gpu_data_manager_impl_private.cc(440)] GPU process isn't usable. Goodbye.
140540725722272:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:../../third_party/boringssl/src/ssl/handshake.cc:393:
zsh: trace trap (core dumped) spotify
I had to launch it with this instead
% spotify --no-zygote
Pinned Comments
gromit commented on 2024-01-24 14:22 (UTC) (edited on 2024-12-28 11:34 (UTC) by gromit)
Please make sure to import the correct GPG key first:
And always build in a clean chroot. It is as easy as:
It is expected that the package will break now and then, as spotify continuously changes download binaries, gpg keys etc (which is not appropriate, but we cannot change this). Please be patient if an update does not occur the next day, you can still use an existing spotify install or update the version yourself.
Antiz commented on 2023-09-13 13:21 (UTC)
@lightofpast Just pushed
v1:1.2.20.1210-2
that now allows you to set custom launch flags in aspotify-flags.conf
file under$XDG_CONFIG_HOME
or~/.config
:)