FS#63242 - [sox] segfault with "play --norm"

Attached to Project: Community Packages
Opened by G. M. (NoSuck) - Sunday, 21 July 2019, 00:10 GMT
Last edited by Toolybird (Toolybird) - Thursday, 01 June 2023, 22:44 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To George Rawlinson (rawlinsong)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


Can anyone reproduce this?

■ play -q 0.wav && echo OK
play WARN alsa: can't encode 0-bit Unknown or not applicable
■ LC_ALL=C play --norm -q 0.wav && echo OK
Segmentation fault (コアダンプ)
▲ play --version
play: SoX v14.4.2
■ uname -srvmo
Linux 5.1.11-arch1-1-ARCH #1 SMP PREEMPT Mon Jun 17 18:56:30 UTC 2019 x86_64 GNU/Linux
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 01 June 2023, 22:44 GMT
Reason for closing:  Upstream
Additional comments about closing:  See comments
Comment by wommel (wommel) - Saturday, 27 July 2019, 01:59 GMT
yes. stable issue on multiple systems.

problme occured with build 14.4.2-5.
build 14.4.2-4 works fine.
Comment by David Runge (dvzrv) - Saturday, 31 August 2019, 23:34 GMT
@NoSuck: It is quite likely that the many patches, that had to be applied on top of 14.4.2 to fix the 12 (!) CVEs that sox currently has attached to that version, broke something. IMHO, the best thing to do would be to complain upstream [1] and demand a new release (to also get the remaining ~30 patches on top of 14.4.2 released).
That being said: I've tried to get a reply from upstream for about a year now and don't have the feeling they care about releases (although they do care about new features apparently).

[1] https://sourceforge.net/p/sox/mailman/sox-devel/
Comment by Toolybird (Toolybird) - Thursday, 27 April 2023, 07:09 GMT
Is this still an issue with latest pkgs?
Comment by wommel (wommel) - Tuesday, 02 May 2023, 07:47 GMT
Yes, the issue still exists.
Comment by David Runge (dvzrv) - Tuesday, 02 May 2023, 08:23 GMT
Then it is an upstream issue (since we seem to be on a very recent commit). Please bring it up with them and report back.