Bug 214067

Summary:	k3b sigsegv after ejecting dvd
Product:	[Applications] k3b	Reporter:	austeze
Component:	general	Assignee:	k3b developers <k3b>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	rakuco
Priority:	NOR	Keywords:	triaged
Version:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description austeze 2009-11-11 04:26:33 UTC

Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Slackware Packages

All that was done was I opened up the application, put in a blank dvd, then ejected the dvd. I walked into the other room and came back to see k3b had crashed due to sigsegv. Not sure why. Here is the backtrace report:
--------------------------------------------------------

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb4a3a700 (LWP 4132)]
[New Thread 0xb1bffb90 (LWP 4158)]
[New Thread 0xb23ffb90 (LWP 4157)]
[New Thread 0xb2dc9b90 (LWP 4133)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb500823c in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 4132)]

Thread 4 (Thread 0xb2dc9b90 (LWP 4133)):
#0  0xb5044137 in select () from /lib/libc.so.6
#1  0xb5d216d7 in ?? () from /usr/lib/libQtCore.so.4
#2  0xb5c5044e in ?? () from /usr/lib/libQtCore.so.4
#3  0xb5bca310 in start_thread () from /lib/libpthread.so.0
#4  0xb504bbee in clone () from /lib/libc.so.6

Thread 3 (Thread 0xb23ffb90 (LWP 4157)):
#0  0xb5bce0b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0xb5c4fe3e in ?? () from /usr/lib/libQtCore.so.4
#2  0xb5c4ffc5 in QThread::sleep () from /usr/lib/libQtCore.so.4
#3  0xb7e38b11 in K3b::MediaCache::PollThread::run () from /usr/lib/libk3b.so.6
#4  0xb5c5044e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb5bca310 in start_thread () from /lib/libpthread.so.0
#6  0xb504bbee in clone () from /lib/libc.so.6

Thread 2 (Thread 0xb1bffb90 (LWP 4158)):
#0  0xb5bce0b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0xb5c4fe3e in ?? () from /usr/lib/libQtCore.so.4
#2  0xb5c4ffc5 in QThread::sleep () from /usr/lib/libQtCore.so.4
#3  0xb7e38b11 in K3b::MediaCache::PollThread::run () from /usr/lib/libk3b.so.6
#4  0xb5c5044e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb5bca310 in start_thread () from /lib/libpthread.so.0
#6  0xb504bbee in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb4a3a700 (LWP 4132)):
#0  0xb500823c in nanosleep () from /lib/libc.so.6
#1  0xb500805f in sleep () from /lib/libc.so.6
#2  0xb633ced8 in ?? () from /usr/lib/libkdeui.so.5
#3  0x00000000 in ?? ()
#0  0xb500823c in nanosleep () from /lib/libc.so.6

Comment 1 Raphael Kubo da Costa 2009-11-11 04:30:34 UTC

Can you please compile your packages with debug information or install packages with them and then post a new backtrace in case this happens again? Thanks.

Comment 2 Andrew Crouthamel 2018-09-25 03:49:24 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 02:34:49 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!