Hi, and thank you for the crash report.
[phao...@gmail.com]
> Let me know if you need more information.
Please try to reproduce the crash using valgrind. Is the file you use
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)
%
--
Happy hacking
Petter Reinholdtsen
