Version: 3.7 (using KDE 4.7.3) OS: Linux Sometimes, when JuK is playing a song, and jumps to the next song, it crashes. Here a backtrace: Application: JuK (juk), signal: Segmentation fault [Current thread is 1 (Thread 0xb40f7a00 (LWP 2194))] Thread 2 (Thread 0xacf59b70 (LWP 2208)): #0 0xb78d7424 in __kernel_vsyscall () #1 0xb552098b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb57c30ec in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6 #3 0xb2972683 in vlc_cond_wait (p_condvar=0x87c73d4, p_mutex=0x87c73bc) at misc/pthread.c:359 #4 0xb28e3674 in LoopRequest (p_playlist=<optimized out>) at playlist/thread.c:539 #5 Thread (data=0x87c72f8) at playlist/thread.c:586 #6 0xaf79570c in ?? () from /usr/lib/libGL.so.1 #7 0x00000000 in ?? () Thread 1 (Thread 0xb40f7a00 (LWP 2194)): [KCrash Handler] #7 0xb7849af7 in TagLib::ID3v2::Frame::~Frame() () from /usr/lib/libtag.so.1 #8 0xb785081b in TagLib::ID3v2::TextIdentificationFrame::~TextIdentificationFrame() () from /usr/lib/libtag.so.1 #9 0xb7850862 in TagLib::ID3v2::TextIdentificationFrame::~TextIdentificationFrame() () from /usr/lib/libtag.so.1 #10 0xb7848ca7 in TagLib::List<TagLib::ID3v2::Frame*>::~List() () from /usr/lib/libtag.so.1 #11 0xb784538e in TagLib::ID3v2::Tag::~Tag() () from /usr/lib/libtag.so.1 #12 0xb7845462 in TagLib::ID3v2::Tag::~Tag() () from /usr/lib/libtag.so.1 #13 0xb788b5f4 in TagLib::TagUnion::~TagUnion() () from /usr/lib/libtag.so.1 #14 0xb783e19a in TagLib::MPEG::File::~File() () from /usr/lib/libtag.so.1 #15 0x08082bc8 in _start () Reproducible: Sometimes Steps to Reproduce: Really I don't know how reproduing this, just happens... Actual Results: JuK crashes Expected Results: JuK does not crash OS: Linux (i686) release 3.0-pae Compiler: gcc I have noticed a rare behaviour. Sometimes when JuK is playing a song and I change to another song, the previous song does not finish to play, and then I listen both songs. I use VLC as phonon backend. Thanks for reading.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!