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

Memory Fault (core dumped) #261

Open
pfr-dev opened this issue Sep 10, 2024 · 6 comments
Open

Memory Fault (core dumped) #261

pfr-dev opened this issue Sep 10, 2024 · 6 comments

Comments

@pfr-dev
Copy link

pfr-dev commented Sep 10, 2024

System information

NetBSD-10 STABLE

Detailed information

spotify-qt would launch to begin with, but would not play anything due to a Failed 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, restarted spotify-qt and....

What happens?

Xxio

So I checked the .core file...

~ $ gdb spotify-qt spotify-qt.core
GNU gdb (GDB) 11.0.50.20200914-git
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64--netbsd".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from spotify-qt...
(No debugging symbols found in spotify-qt)
[New process 769]
[New process 773]
[New process 772]
[New process 771]
[New process 770]
Core was generated by `spotify-qt'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000075e1ae34f876 in QObject::deleteLater() () from /usr/pkg/qt6/lib/libQt6Core.so.6
[Current thread is 1 (process 769)]
(gdb) bt
#0  0x000075e1ae34f876 in QObject::deleteLater() () from /usr/pkg/qt6/lib/libQt6Core.so.6
#1  0x00000000a78dc73d in ?? ()
#2  0x00000000a78dc774 in ?? ()
#3  0x00000000a78e0e4d in ?? ()
#4  0x00000000a7960ccc in ?? ()
#5  0x00000000a7855e4d in ?? ()
#6  0x00007f7e53c0baf8 in ?? () from /usr/libexec/ld.elf_so
#7  0x0000000000000001 in ?? ()
#8  0x00007f7fffa0f348 in ?? ()
#9  0x0000000000000000 in ?? ()
(gdb) 

Not much info here...

I tried uninstalling, clearing ~/.cache/spotify-qt/ and reinstalling but the issue persists. How can I completely purge spotify-qt and its dependencies from my system to start again?

@pfr-dev
Copy link
Author

pfr-dev commented Sep 10, 2024

Similar to #251 ? what happened to #252 ?

@0323pin
Copy link

0323pin commented Sep 11, 2024

@kraxarn Hi, NetBSD package maintainer here.

I can reproduce this on my system. Even though, I've just build the latest release with -DCMAKE_BUILD_TYPE=RelWithDebInfo, I can't seem to get a better backtrace 😞

gdb spotify-qt spotify-qt.core
GNU gdb (GDB) 15.1
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64--netbsd".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from spotify-qt...
(No debugging symbols found in spotify-qt)
[New process 10828]
[New process 17567]
[New process 7960]
[New process 22802]
Core was generated by `spotify-qt'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000070fe6038c553 in QObject::deleteLater() () from /usr/pkg/qt6/lib/libQt6Core.so.6
[Current thread is 1 (process 10828)]
(gdb) bt
#0  0x000070fe6038c553 in QObject::deleteLater() () from /usr/pkg/qt6/lib/libQt6Core.so.6
#1  0x00000000004878a3 in ?? ()
#2  0x00000000004878da in ?? ()
#3  0x000000000048c25e in ?? ()
#4  0x000000000051709c in ?? ()
#5  0x00000000003ffba5 in ?? ()
#6  0x00007f7ff7447f58 in ?? () from /usr/libexec/ld.elf_so
#7  0x0000000000000001 in ?? ()
#8  0x00007f7fff2dccf8 in ?? ()
#9  0x0000000000000000 in ?? ()

Additional info:
compiler: gcc version 12.4.0
cmake: cmake version 3.30.3
OS: NetBSD 10.99.12 (GENERIC)

@kraxarn
Copy link
Owner

kraxarn commented Sep 12, 2024

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.

@pfr-dev
Copy link
Author

pfr-dev commented Sep 13, 2024

Is this at all related to librespot/issues/1308 ?
I'm also unable to authenticate using ncspot on various machines. Hoping this will be fixed in the near future.

@0323pin
Copy link

0323pin commented Sep 13, 2024

@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 spotify-player built with different audio backends on two different machines, running two different OSs and, both work for now. That said, it wouldn't surprise me if things break at some point. After all, Spotify only really supports streaming through Googles WideVine.

@kraxarn
Copy link
Owner

kraxarn commented Sep 14, 2024

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.

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

3 participants