Dear Maintainer,

I am getting segfault when trying to play ogg files. File is being played with no sound and then getting segfault.
Here is some output:

~$ gdb --args ogg123 /usr/share/sounds/KDE-Im-Cant-Connect.ogg
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 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-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://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 ogg123...Reading symbols from /usr/lib/debug/.build-id/81/473fbaeae8f802994c1590b9238bfaec47375b.debug...done.
done.
(gdb) r
Starting program: /usr/bin/ogg123 /usr/share/sounds/KDE-Im-Cant-Connect.ogg
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Audio Device:   Advanced Linux Sound Architecture (ALSA) output

[New Thread 0x7fffee3fa700 (LWP 26989)]
Playing: /usr/share/sounds/KDE-Im-Cant-Connect.ogg
Ogg Vorbis stream: 2 channel, 48000 Hz
[Thread 0x7fffee3fa700 (LWP 26989) exited]0.4 kbps)  Output Buffer   0.0% (EOS)

Thread 1 "ogg123" received signal SIGSEGV, Segmentation fault.
__lll_unlock_elision (lock=lock@entry=0x614c60 <output_lock>, private=0) at ../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
29      ../sysdeps/unix/sysv/linux/x86/elision-unlock.c: No such file or directory.
(gdb) bt
#0  __lll_unlock_elision (lock=lock@entry=0x614c60 <output_lock>, private=0) at ../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#1  0x00007ffff70f7187 in __pthread_mutex_unlock_usercnt (mutex=mutex@entry=0x614c60 <output_lock>, decr=decr@entry=1) at pthread_mutex_unlock.c:64
#2  0x00007ffff70f720a in __GI___pthread_mutex_unlock (mutex=mutex@entry=0x614c60 <output_lock>) at pthread_mutex_unlock.c:314
#3  0x000000000040a94a in status_reset_output_lock () at status.c:365
#4  0x0000000000408eff in play (source_string=<optimized out>) at ogg123.c:746
#5  0x0000000000403daa in main (argc=<optimized out>, argv=<optimized out>) at ogg123.c:496

Let me know if you need more information.

Hi, and thank you for the crash report.

[phaoost@gmail.com]
to crash from the kde-runtime-data package?  Which version are you
using?  Are you really using oldstable?

I'm unable to reproduce the crash in Strech:

% valgrind ogg123 /usr/share/sounds/KDE-Im-Cant-Connect.ogg
==12052== Memcheck, a memory error detector
==12052== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==12052== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==12052== Command: ogg123 /usr/share/sounds/KDE-Im-Cant-Connect.ogg
==12052==

Audio Device:   Advanced Linux Sound Architecture (ALSA) output

Spiller: /usr/share/sounds/KDE-Im-Cant-Connect.ogg
Ogg Vorbis stream: 2 channel, 48000 Hz

Færdig.
==12052==
==12052== HEAP SUMMARY:
==12052==     in use at exit: 275,582 bytes in 4,930 blocks
==12052==   total heap usage: 8,674 allocs, 3,744 frees, 1,077,314 bytes allocated
==12052==
==12052== LEAK SUMMARY:
==12052==    definitely lost: 0 bytes in 0 blocks
==12052==    indirectly lost: 0 bytes in 0 blocks
==12052==      possibly lost: 151,802 bytes in 4,776 blocks
==12052==    still reachable: 123,780 bytes in 154 blocks
==12052==         suppressed: 0 bytes in 0 blocks
==12052== Rerun with --leak-check=full to see details of leaked memory
==12052==
==12052== For counts of detected and suppressed errors, rerun with: -v
==12052== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
%

Thanks,

here is the output:

~$ valgrind ogg123 /usr/share/sounds/KDE-Im-Cant-Connect.ogg
==29668== Memcheck, a memory error detector
==29668== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==29668== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright
info
==29668== Command: ogg123 /usr/share/sounds/KDE-Im-Cant-Connect.ogg
==29668==

Audio Device:   Advanced Linux Sound Architecture (ALSA) output

Playing: /usr/share/sounds/KDE-Im-Cant-Connect.ogg
Ogg Vorbis stream: 2 channel, 48000 Hz


Done.
==29668==
==29668== HEAP SUMMARY:
==29668==     in use at exit: 194,333 bytes in 4,923 blocks
==29668==   total heap usage: 9,593 allocs, 4,670 frees, 1,022,831 bytes
allocated
==29668==
==29668== LEAK SUMMARY:
==29668==    definitely lost: 0 bytes in 0 blocks
==29668==    indirectly lost: 0 bytes in 0 blocks
==29668==      possibly lost: 151,952 bytes in 4,780 blocks
==29668==    still reachable: 42,381 bytes in 143 blocks
==29668==         suppressed: 0 bytes in 0 blocks
==29668== Rerun with —leak-check=full to see details of leaked memory
==29668==
==29668== For counts of detected and suppressed errors, rerun with: -v
==29668== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

valgrind shows the same output you've posted, there is no segfault and no
sound.
Yes the ogg file is from kde-runtime-data, but I am getting the same result
with file from oxygen-sounds

I am using testing/sid packages on my system mostly. All packages related
to vorbis-tools are either from sid or from testing branches (see initial
report). Here are versions of packages which provide sound files:

~$ dpkg -l kde-runtime-data oxygen-sounds |grep ii
ii  kde-runtime-data 4:16.04.3-1  all          shared data files for the
KDE base runtime module
ii  oxygen-sounds    4:5.7.0-1    all          Sounds for the Oxygen
desktop theme

Hm, I was reminded of this issue when I read
<URL: http://www.bityard.org/blog/2016/08/05/debugging_segfaults_open-iscsi_iscsiuio_intel_broadwell >.
Could it be the same issue?

Control: tags -1 + patch

I created a draft patch to address this.  See the attached file.  Perhaps it should
be discussed with upstream?

See also <URL: https://bugs.debian.org/842796 >.

My proposed patch is passed upstream now.