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

Starting problem #122

Closed
sahafselim opened this issue Sep 9, 2022 · 9 comments
Closed

Starting problem #122

sahafselim opened this issue Sep 9, 2022 · 9 comments

Comments

@sahafselim
Copy link

[sahafselim@sahafselim ~]$ 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)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[libprotobuf ERROR ../core/vendor/protobuf3/src/google/protobuf/wire_format_lite.cc:577] String field 'spotify.event_sender.proto.DroppedEvents.DroppedEventsBySequenceIdEntry.key' contains invalid UTF-8 data when parsing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes.
[sahafselim@sahafselim ~]$

@abba23
Copy link
Owner

abba23 commented Sep 10, 2022

Are you certain this is related to spotify-adblock and not just a general problem with Spotify on your system? Search results for the error message suggest that this happens sometimes with the Linux client and might be solved by deleting the Spotify cache (i.e. rm -r ~/.cache/spotify).

@pfuhlert
Copy link

Thank you abba23 that solved the problem for me.

@sahafselim
Copy link
Author

My problem still alive,I can only open spotify once,for reopen must restart .

@abba23
Copy link
Owner

abba23 commented Sep 12, 2022

My problem still alive,I can only open spotify once,for reopen must restart .

That sounds like a different problem. Has your original problem been solved? Not being able to reopen Spotify sounds like the same issue as #121, which is also unrelated to spotify-adblock.

@sahafselim
Copy link
Author

Sorry for misunderstanding,the error message I've posted above is after the second run spotify.
Want to see the error message and run it from terminal for open second time.

@abba23
Copy link
Owner

abba23 commented Sep 13, 2022

Again, are you certain this problem is even related to spotify-adblock? Have you tried running Spotify without spotify-adblock to see if the problem still occurs?

@sahafselim
Copy link
Author

Here's the result
[sahafselim@sahafselim ~]$ 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)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[0913/125740.516584:FATAL:gpu_data_manager_impl_private.cc(447)] GPU process isn't usable. Goodbye.
İzleme/kesme noktası yakalayıcı (çekirdek döküldü) Tracking/breakpoint catcher (core spilled)
[sahafselim@sahafselim ~]$ spotify --no-zygote
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[sahafselim@sahafselim ~]$

@abba23
Copy link
Owner

abba23 commented Sep 13, 2022

Since you didn't elaborate, I assume Spotify was launched successfully with the latter command. Just use the same --no-zygote option when launching Spotify with spotify-adblock as well then. Either way, this shows that the problem is unrelated to spotify-adblock, so I can't really help you with that if it hasn't already been fixed.

@0seno

This comment was marked as off-topic.

@abba23 abba23 closed this as completed Nov 28, 2022
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

4 participants