audacious 3.10.1 will segfault if you attempt to seek the audio while the SoX resampling plugin is active and set to 48000Hz Ultra High quality. steps to reproduce: compile audiacous-3.10.1 and it's plugins enable SoX Resampling plugin set Resample settings to 48000Hz Ultra High quality Open a file the needs resampling play the audio file attempt to seek position forward Thread 21 "audacious" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff5ded700 (LWP 22270)] 0x00007fffdd087641 in ?? () from /usr/lib64/libsoxr.so.0 (gdb) bt #0 0x00007fffdd087641 in () at /usr/lib64/libsoxr.so.0 #1 0x00007fffdd0854e1 in () at /usr/lib64/libsoxr.so.0 #2 0x00007fffdd086f10 in soxr_process () at /usr/lib64/libsoxr.so.0 #3 0x00007fffdfec34f3 in () at /usr/lib64/audacious/Effect/sox-resampler.so #4 0x00007ffff7f3b3f1 in () at /usr/lib64/libaudcore.so.5 #5 0x00007ffff7f40fd1 in () at /usr/lib64/libaudcore.so.5 #6 0x00007ffff7f42afe in InputPlugin::write_audio(void const*, int) () at /usr/lib64/libaudcore.so.5 #7 0x00007ffff43f5ab6 in () at /usr/lib64/audacious/Input/sndfile.so #8 0x00007ffff7f41ed4 in () at /usr/lib64/libaudcore.so.5 #9 0x00007ffff7f06497 in start_thread () at /lib64/libpthread.so.0 #10 0x00007ffff78683cf in clone () at /lib64/libc.so.6 (gdb) bt full #0 0x00007fffdd087641 in () at /usr/lib64/libsoxr.so.0 #1 0x00007fffdd0854e1 in () at /usr/lib64/libsoxr.so.0 #2 0x00007fffdd086f10 in soxr_process () at /usr/lib64/libsoxr.so.0 #3 0x00007fffdfec34f3 in () at /usr/lib64/audacious/Effect/sox-resampler.so #4 0x00007ffff7f3b3f1 in () at /usr/lib64/libaudcore.so.5 #5 0x00007ffff7f40fd1 in () at /usr/lib64/libaudcore.so.5 #6 0x00007ffff7f42afe in InputPlugin::write_audio(void const*, int) () at /usr/lib64/libaudcore.so.5 #7 0x00007ffff43f5ab6 in () at /usr/lib64/audacious/Input/sndfile.so #8 0x00007ffff7f41ed4 in () at /usr/lib64/libaudcore.so.5 #9 0x00007ffff7f06497 in start_thread () at /lib64/libpthread.so.0 #10 0x00007ffff78683cf in clone () at /lib64/libc.so.6 (gdb)
Does the same happen with 4.0_beta1?
kind of. segfaults aren't so much triggered by 48000Hz seeks in version 4 but seeking on 8Khz wav files
In that case, and if there is no existing one, please file a bug report upstream.
Ping, does this happens on 4.0.5?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e1a3f548d70d6b5ab3b891c360fc2c88f9d8836c commit e1a3f548d70d6b5ab3b891c360fc2c88f9d8836c Author: Marco Scardovi <marco@scardovi.com> AuthorDate: 2021-11-21 08:15:55 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2021-11-21 12:58:55 +0000 media-sound/audacious: bump to version 4.1 Drop 3.x as it is require GTK+:2 Closes: https://bugs.gentoo.org/775989 Closes: https://bugs.gentoo.org/797835 Bug: https://bugs.gentoo.org/711292 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Marco Scardovi <marco@scardovi.com> Signed-off-by: Joonas Niilola <juippis@gentoo.org> media-sound/audacious/Manifest | 1 + media-sound/audacious/audacious-4.1.ebuild | 70 ++++++++++++++++++++++++++++++ 2 files changed, 71 insertions(+)
^ Anyone upset about removing the gtk+-2 version, it has been an upstream decision to discontinue supporting gtk+. There are plenty of alternative music players available, or you can git checkout to the parent commit 4af735318c20dc6b211e8b8eb16cb71e6b4b8fa1 (or browse the web git interfaces) and preserve the older ebuilds in a local overlay, and use them as long as they work (no support for them though!)
Closing this bug, since the original reporter ejected himself from it.
