Bug 321073 - K3B became unresponsive and crashed after failing to verify a written DVD
Summary: K3B became unresponsive and crashed after failing to verify a written DVD
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 2.0.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
: 289551 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-06-12 19:26 UTC by pcragg
Modified: 2018-10-31 14:43 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (6.63 KB, text/plain)
2013-11-13 01:57 UTC, Herbert Carl Meyer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pcragg 2013-06-12 19:26:39 UTC
Application: k3b (2.0.2)
KDE Platform Version: 4.10.3
Qt Version: 4.8.4
Operating System: Linux 3.8.0-23-generic x86_64
Distribution: Linux Mint 15 Olivia

-- Information about the crash:
I needed to write an iso file (approx 2.6 GB) to a DVD-R disk. The blanks are Maxell 16x DVD-R being written in an LG drive with the model number GH22LP20. I'm running Mint Linux 15 (olivia) with the cinnamon desktop and I've installed the KDE runtime so that I can use K3B. KDE was installed from the packages in  the linux mint repositories.

I ran the burn in simulate mode and received no errors. I than re-ran the burn with auto speed detection, auto mode and verify written data selected. The burn seemed to progress without error reaching 100% write complete, 50% overall. As soon as the verification started I received a warning message saying that no suitable medium was detected and that I was to load a DVD. As the medium was already loaded I was left with no option but to cancel the burn at this stage.

Following the cancellation I attempted to use the eject function from the K3B menu but the disk refused to eject. I then tried to close K3B using the close widget on the window (the x top right) but got no response. On the second attempt to close the window K3B crashed.

On reinserting the burned DVD I am informed that the medium is empty, However, examination of the surface would seem to indicate that the files were burned.

-- Backtrace:
Application: K3b (k3b), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8cdb7d5800 (LWP 12170))]

Thread 6 (Thread 0x7f8cb6f01700 (LWP 12173)):
#0  0x00007fff997feaf7 in ?? ()
#1  0x4040404040404040 in ?? ()
#2  0x00000002b0002e10 in ?? ()
#3  0x00007f8cb0001350 in ?? ()
#4  0x00007f8cb6f00a80 in ?? ()
#5  0x00007f8cb6f00b38 in ?? ()
#6  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f8cae0e9700 (LWP 12308)):
#0  0x00007f8ccf3dcca4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f8cd93de585 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f8cd93de5d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f8ccf69d1b4 in ?? () from /usr/lib/nvidia-313-updates/libGL.so.1
#4  0x00007f8ccf3d8f8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#5  0x00007f8cd4d38e1d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f8cad8e8700 (LWP 12312)):
#0  0x00007f8ccf3dcca4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f8cd9124a09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f8cd940ccee in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f8ccf69d1b4 in ?? () from /usr/lib/nvidia-313-updates/libGL.so.1
#4  0x00007f8ccf3d8f8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#5  0x00007f8cd4d38e1d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f8cad0e7700 (LWP 12313)):
#0  0x00007fff997feaf7 in ?? ()
#1  0x00007f8cad0e6a80 in ?? ()
#2  0x0000000200000001 in ?? ()
#3  0x00007f8ca0001440 in ?? ()
#4  0x00007f8cad0e6ab0 in ?? ()
#5  0x00007f8cad0e6b68 in ?? ()
#6  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f8c5bbd1700 (LWP 12659)):
#0  0x00007f8ccf3dd05e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f8cd62ac7f6 in thread_sleep (ti=ti@entry=0x7f8c5bbd0c80) at thread/qthread_unix.cpp:475
#2  0x00007f8cd62acf96 in QThread::sleep (secs=secs@entry=2) at thread/qthread_unix.cpp:489
#3  0x00007f8cdb0be7f5 in K3b::MediaCache::PollThread::run (this=0x150fca0) at /build/buildd/k3b-2.0.2/libk3b/tools/k3bmediacache.cpp:106
#4  0x00007f8cd62adbec in QThreadPrivate::start (arg=0x150fca0) at thread/qthread_unix.cpp:338
#5  0x00007f8ccf69d1b4 in ?? () from /usr/lib/nvidia-313-updates/libGL.so.1
#6  0x00007f8ccf3d8f8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#7  0x00007f8cd4d38e1d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f8cdb7d5800 (LWP 12170)):
[KCrash Handler]
#5  0x00007f8cdb09ad41 in K3b::Job::waitForMedium (this=this@entry=0x1d5ea10, device=0x1a7be50, mediaState=..., mediaType=..., minMediaSize=..., message=...) at /build/buildd/k3b-2.0.2/libk3b/core/k3bjob.cpp:146
#6  0x00007f8cdb100ccd in K3b::VerificationJob::slotMediaLoaded (this=0x1d5ea10) at /build/buildd/k3b-2.0.2/libk3b/jobs/k3bverificationjob.cpp:252
#7  0x00007f8cdb101d75 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at /build/buildd/k3b-2.0.2/obj-x86_64-linux-gnu/libk3b/k3bverificationjob.moc:75
#8  K3b::VerificationJob::qt_static_metacall (_o=0x1d5ea10, _c=27770448, _id=-1719901904, _a=0x7fff997c6140) at /build/buildd/k3b-2.0.2/obj-x86_64-linux-gnu/libk3b/k3bverificationjob.moc:62
#9  0x00007f8cd63bf0ef in QMetaObject::activate (sender=sender@entry=0x24617a0, m=m@entry=0x7f8cdb3c2a00 <K3b::Device::DeviceHandler::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff997c6330) at kernel/qobject.cpp:3539
#10 0x00007f8cdb0a884f in K3b::Device::DeviceHandler::finished (this=this@entry=0x24617a0, _t1=_t1@entry=0x24617a0) at /build/buildd/k3b-2.0.2/obj-x86_64-linux-gnu/libk3b/k3bdevicehandler.moc:126
#11 0x00007f8cdb0a8878 in K3b::Device::DeviceHandler::jobFinished (this=0x24617a0, success=<optimized out>) at /build/buildd/k3b-2.0.2/libk3b/tools/k3bdevicehandler.cpp:208
#12 0x00007f8cd63c45be in QObject::event (this=0x24617a0, e=<optimized out>) at kernel/qobject.cpp:1194
#13 0x00007f8cd54d58ec in QApplicationPrivate::notify_helper (this=this@entry=0x15a47e0, receiver=receiver@entry=0x24617a0, e=e@entry=0x7f8c4c001350) at kernel/qapplication.cpp:4567
#14 0x00007f8cd54d825b in QApplication::notify (this=0x7fff997c6e10, receiver=0x24617a0, e=0x7f8c4c001350) at kernel/qapplication.cpp:4428
#15 0x00007f8cd6df3af6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#16 0x00007f8cd63aa63e in QCoreApplication::notifyInternal (this=0x7fff997c6e10, receiver=receiver@entry=0x24617a0, event=event@entry=0x7f8c4c001350) at kernel/qcoreapplication.cpp:946
#17 0x00007f8cd63ae171 in sendEvent (event=0x7f8c4c001350, receiver=0x24617a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x14b5220) at kernel/qcoreapplication.cpp:1570
#19 0x00007f8cd63ae4a3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463
#20 0x00007f8cd63d8e83 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#21 postEventSourceDispatch (s=0x158a150) at kernel/qeventdispatcher_glib.cpp:279
#22 0x00007f8cd013df05 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f8cd013e248 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f8cd013e304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f8cd63d9016 in QEventDispatcherGlib::processEvents (this=0x14b6b00, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#26 0x00007f8cd557b1ae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x00007f8cd63a938f in QEventLoop::processEvents (this=this@entry=0x7fff997c6c40, flags=...) at kernel/qeventloop.cpp:149
#28 0x00007f8cd63a9618 in QEventLoop::exec (this=this@entry=0x7fff997c6c40, flags=...) at kernel/qeventloop.cpp:204
#29 0x00007f8cd63aecf6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#30 0x00007f8cd54d3ffc in QApplication::exec () at kernel/qapplication.cpp:3828
#31 0x00000000004449a2 in main (argc=<optimized out>, argv=0x7fff997c6f58) at /build/buildd/k3b-2.0.2/src/main.cpp:165

Reported using DrKonqi
Comment 1 Herbert Carl Meyer 2013-11-13 01:57:28 UTC
Created attachment 83541 [details]
New crash information added by DrKonqi

k3b (2.0.2) on KDE Platform 4.11.2 using Qt 4.8.5

- What I was doing when the application crashed:
As duplicated report, attempting to load disk after failure to verify

-- Backtrace (Reduced):
#6  0x00000036c7e85efb in K3b::Job::waitForMedium(K3b::Device::Device*, QFlags<K3b::Device::MediaState>, QFlags<K3b::Device::MediaType>, K3b::Msf const&, QString const&) () from /lib64/libk3blib.so.6
#7  0x00000036c7eea966 in K3b::VerificationJob::slotMediaLoaded() () from /lib64/libk3blib.so.6
[...]
#10 0x00000036c7e9302f in K3b::Device::DeviceHandler::finished(K3b::Device::DeviceHandler*) () from /lib64/libk3blib.so.6
#11 0x00000036c7e94058 in K3b::Device::DeviceHandler::jobFinished(bool) () from /lib64/libk3blib.so.6
#12 0x00000036ab79232e in QObject::event(QEvent*) () from /lib64/libQtCore.so.4
Comment 2 Jekyll Wu 2013-11-13 02:31:52 UTC
*** Bug 289551 has been marked as a duplicate of this bug. ***
Comment 3 Andrew Crouthamel 2018-10-31 03:58:33 UTC
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!
Comment 4 Herbert Carl Meyer 2018-10-31 13:28:38 UTC
This has not occurred again, with newer versions of K3. Close the bug. Thank you.
Comment 5 Andrew Crouthamel 2018-10-31 14:43:34 UTC
Thanks for the update!