Bug 250272

Summary: K3B crash or hang during audio CD ripping to FLAC format (other file types are not tested yet)
Product: [Applications] k3b Reporter: aka <dr_anonymous>
Component: generalAssignee: k3b developers <k3b>
Status: RESOLVED WORKSFORME    
Severity: crash CC: aacid, trueg
Priority: NOR Keywords: triaged
Version: 1.91.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description aka 2010-09-05 14:49:11 UTC
Application: k3b (1.91.0)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
Hello!

I was ripping my newly bought CD-s into FLAC file formats.
This crashes/hangs was not happened before.
Maybe related to this: I was upgraded my Ubuntu Linux distribution to Lucid Lynx (10.04) from Karmik Koala (9.10) in this week.
But strange, the ripping works normally, when I rip to wav.
Oh, and one more thing: the K3B windows won't respond or won't give any feedback after the ripping starts. I know, when it has finished the ripping, because the DVD drives LED stops blinking. (or K3B crashes)
The last ripped track not always complete.

aka
2010. September 5. 14h46m


The crash can be reproduced every time.

 -- Backtrace:
Application: K3b (k3b), signal: Segmentation fault
[Current thread is 1 (Thread 0x7febbaa36760 (LWP 23129))]

Thread 2 (Thread 0x7feba02b6710 (LWP 23183)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007febb5365ea3 in QMutexPrivate::wait (this=0x13e5780, timeout=-1) at thread/qmutex_unix.cpp:84
#2  0x00007febb5361a05 in QMutex::lock (this=0x13e5750) at thread/qmutex.cpp:205
#3  0x00007febb545ace2 in QCoreApplication::postEvent (receiver=0x2497f90, event=0x30ce7f0, priority=0) at kernel/qcoreapplication.cpp:1113
#4  0x00007febb546bb77 in queued_activate (sender=0x249ace0, signal=<value optimized out>, c=0x249c9a0, argv=0x2, semaphore=0x0) at kernel/qobject.cpp:3173
#5  0x00007febb546dd02 in QMetaObject::activate (sender=0x249ace0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xffffffffffffffff) at kernel/qobject.cpp:3266
#6  0x00007febba2f9251 in K3b::Job::subPercent(int) () from /usr/lib/libk3blib.so.6
#7  0x00000000004e64b5 in _start ()

Thread 1 (Thread 0x7febbaa36760 (LWP 23129)):
[KCrash Handler]
#5  QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x13e5710) at kernel/qcoreapplication.cpp:1299
#6  0x00007febb54849d3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#7  postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#8  0x00007febaf73c8c2 in g_main_dispatch (context=0x14292b0) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:1960
#9  IA__g_main_context_dispatch (context=0x14292b0) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2513
#10 0x00007febaf740748 in g_main_context_iterate (context=0x14292b0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2591
#11 0x00007febaf7408fc in IA__g_main_context_iteration (context=0x14292b0, may_block=1) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2654
#12 0x00007febb5484513 in QEventDispatcherGlib::processEvents (this=0x13e4e60, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#13 0x00007febb442e46e in QGuiEventDispatcherGlib::processEvents (this=0x13e5750, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007febb5459992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#15 0x00007febb5459d6c in QEventLoop::exec (this=0x7fffd38b7e60, flags=) at kernel/qeventloop.cpp:201
#16 0x00007febb484809e in QDialog::exec (this=0x7fffd38b80a0) at dialogs/qdialog.cpp:546
#17 0x00000000005411f7 in _start ()

Possible duplicates by query: bug 250232, bug 250178, bug 250142, bug 249944, bug 249601.

Reported using DrKonqi
Comment 1 Albert Astals Cid 2014-09-29 22:27:12 UTC
Can you reproduce this crash on k3b 2.0.2?
Comment 2 Andrew Crouthamel 2018-09-25 03:39:12 UTC
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 set the bug status 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!
Comment 3 Andrew Crouthamel 2018-10-27 04:16:53 UTC
Dear Bug Submitter,

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!