-
Notifications
You must be signed in to change notification settings - Fork 64
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
Memory Fault (core dumped) #261
Comments
@kraxarn Hi, NetBSD package maintainer here. I can reproduce this on my system. Even though, I've just build the latest release with
Additional info: |
Yeah, seems to be the same issue as #251. Because there has been no progress in the pull request in a while, I'll probably try to fix the remaining issues with it myself, as this seems to be a fairly common issue. As for working around this, the config file should be in "~/.config/kraxarn/spotify-qt.json", which can be fetched using "spotify-qt --paths". If you open the file and set "Spotify.start_client" to "false", or just delete the file entirely, you should be able to start the client again. |
Is this at all related to librespot/issues/1308 ? |
@pfr-dev I don't think so. I had no issues with authentication while trying to reproduce your issue. You might have had bad luck and bumped into both of these. For the record, I use |
Yeah, seems to be the same issue as #251. Because there has been no progress in the pull request in a while, I'll probably try to fix the remaining issues with it myself, as this seems to be a fairly common issue. As for working around this, the config file should be in "~/.config/kraxarn/spotify-qt.json", which can be fetched using "spotify-qt --paths". If you open the file and set "Spotify.start_client" to "false", or just delete the file entirely, you should be able to start the client again. |
No, on NetBSD
This just means that if you want to use another backend, you need to compile from source. Pre-built binaries will use As for this issue, it's because #252 has been merged but, there is no new release, yet. You will need to build Even if @kraxarn pushes a new release, you will still need to wait for the next stable package release which, is due somewhere between Christmas and New year. |
Ok Thanks Pin. When I ran
This is the
So I'm unable to build it without those options present. Any chance you can paste the more recent |
@pfr-dev the audio options are for Build options are ... well, build options and can only be used for source builds. Binaries come with default options. Anyway, not changing them only means you will need both On the other hand, you do need a |
Doh! I knew it would be obvious. Sorry for the noise. |
No worries. After all the bug still lives in your version. |
@pfr-dev instructions on how to build from the master branch here have now been sent to you off thread. |
@kraxarn With Pin's help I've attempted to build from d647b202fd23cd and get the following build error:
He is unable to reproduce this but he is on Can you please confirm if this commit (which might solve this issue) relies on a higer version than |
System information
NetBSD-10 STABLE
Detailed information
spotify-qt
would launch to begin with, but would not play anything due to aFailed to start playback: Player command failed: No active device found
. So I looked and it seemed no playback device was listed. So I went in and added the path to/usr/pkg/bin/librespot
for the device, restartedspotify-qt
and....What happens?
So I checked the
.core
file...Not much info here...
I tried uninstalling, clearing
~/.cache/spotify-qt/
and reinstalling but the issue persists. How can I completely purgespotify-qt
and its dependencies from my system to start again?The text was updated successfully, but these errors were encountered: