-
Notifications
You must be signed in to change notification settings - Fork 456
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
Snapclient v0.26 does not start: Segmentation fault #968
Comments
I have the same problem. On two Raspberry Pi 1B's (running 0.25 before) 0.26.0-1_without-pulse_armhf.deb causes segmentation faults, however, on my Orange Pi Zero 0.26.0-1_without-pulse_armhf.deb does not cause them. I'm unsure what is the difference between them, but I can give the output of Raspberry Pi 1B:
Orange Pi Zero:
This probably is not too helpful, so is there any way I can help debugging? |
Same here. I have 3 Pis all running Raspbian Bullseye Lite, all were running 0.25 before. Two (both 3Bs with 1GB RAM) are working with 0.26, one of them is also running snapserver 0.26 successfully. But one is a Pi Zero W (512 MB RAM) and that segfaults when I try to run 0.26 (using the without_pulse .deb). I've reverted it to 0.25 and it works fine. I note that 0.26 had an additional dependency on libvorbisidec1, which wasn't required for 0.25. Don't know if this is relevant but thought it worth mentioning. Looking at the above reply, I note that the two of mine that work are armv71 architecture, whereas the one that doesn't is armv61, which tallies with the above reply. |
Same problem on a Pi B+ running Raspbian Buster (10) |
Hi, the 0.26.0 debian packages are built on a bullseye docker container, hosted on a RaspberryPi 4. Previous builds were built on a native Raspian Buster powered RPi3. |
Thanks for the quick response. Unfortunately that new build still segfaults on my Pi Zero.
|
I was suspicious about the fact the 0.26 has a new dependency on libvorbisidec1, which 0.25 didn't have. So I built a new version from source, after hacking the Makefile to remove all references to vorbis, ogg, and opus (and pulse, since I was using the without_pulse version before). I built this on an armv7l Raspberry Pi 3 with bullseye. I then transferred that binary to the Pi Zero, armv6l, device that would not run 0.26. This new version works. I'm playing PCM audio through it as I type this. |
Same problem here on Raspberry Pi 1B and RPi Zero Digging a little further, running
the snapshot:
Don´t know if that hints to something... |
same problem. just upgraded my old setup to buster, upgraded to snapcast 0.26 and they are segfaulting as well. both on two raspberry pi 2.
|
And what about the linked packages in the snapos repo from my last answer? |
🎉
|
Nice! Thanks for the feedback. |
it's not all good yet. not sure what to make of it yet or if it's related:
|
looks better after
those directories were owned by |
I haven't tested the builds in snapos extensively, but for the 5 seconds I tested them on my Raspberry Pi 1B it worked perfectly straight away. |
Thanks for testing. I've also tested on my rpi1 as well as on rpi3 and rpi4. |
New uploaded deb works on rpi0 also. thx. |
Seems also to work now for me. Thank you very much @badaix ! |
@badaix Will you add these armv6 versions here under the release section? My ansible playbook automatically checks here for new versions and distributes them to my various clients. |
Offtopic (sorry): @jojo141185, could you share your ansible playbook? |
From my previous post:
|
I'd suggest to make a 0.26.1 release, as the binaries differ. |
Distributions would be confused with a 0.26.1, because not a single line of code changed, just the package build process, which is in the meantime hosted in the snapos project, to clearly separate the code from packaging. |
To bump that version number you'll have changed the code, right? The issue (which I've never personally heard of before) is avoided. |
Fixed in snapcast v0.27.0 |
Describe the bug
After upgrading snapclient to version 0.26.0 the client does not start any more. It only displays "Segmentation faul"
Steps to Reproduce
Environment details
gdb output:
_pi@garage:~ $ gdb snapclient
GNU gdb (Raspbian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 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 "arm-linux-gnueabihf".
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 snapclient...
(No debugging symbols found in snapclient)
(gdb) run
Starting program: /usr/bin/snapclient
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x0048c24c in player::AlsaPlayer::worker() ()_
The text was updated successfully, but these errors were encountered: