Bug 174723

Summary:	The application KMix (kmix) crashed and caused the signal 6 (SIGABRT).
Product:	[Applications] kmix	Reporter:	Abbas Rizvi <yayoo>
Component:	general	Assignee:	Christian Esken <esken>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	finex, Regnaron
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Abbas Rizvi 2008-11-09 16:50:28 UTC

Version:           3.0 (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

Everytime about 10 mins after KDE starts I get this Error and kmix crashes..  However if i restart it it works fine and does not crash.

The application KMix (kmix) crashed and caused the signal 6 (SIGABRT).

Application: KMix (kmix), signal SIGABRT
(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)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb64388d0 (LWP 5338)]
(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)
[KCrash handler]
#6  0xb7f6c430 in __kernel_vsyscall ()
#7  0xb7dc0880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb7dc2248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb757d795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb757d872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb757d915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb798d57a in ?? () from /usr/lib/libsolid.so.4
#13 0xb798d87f in ?? () from /usr/lib/libsolid.so.4
#14 0xb768aa60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb768b7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb799f883 in ?? () from /usr/lib/libsolid.so.4
#17 0xb79c549e in ?? () from /usr/lib/libsolid.so.4
#18 0xb79c558a in ?? () from /usr/lib/libsolid.so.4
#19 0xb74e226e in ?? () from /usr/lib/libQtDBus.so.4
#20 0xb74e9627 in ?? () from /usr/lib/libQtDBus.so.4
#21 0xb7685771 in QObject::event () from /usr/lib/libQtCore.so.4
#22 0xb6cb38ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#23 0xb6cbb76e in QApplication::notify () from /usr/lib/libQtGui.so.4
#24 0xb7bf772d in KApplication::notify () from /usr/lib/libkdeui.so.5
#25 0xb7675e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#26 0xb7676ae5 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#27 0xb7676cdd in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#28 0xb76a082f in ?? () from /usr/lib/libQtCore.so.4
#29 0xb665b6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb665eda3 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb665ef61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb76a0478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#33 0xb6d4dee5 in ?? () from /usr/lib/libQtGui.so.4
#34 0xb767452a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#35 0xb76746ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#36 0xb7676da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#37 0xb6cb3767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#38 0xb7f05abb in kdemain () from /usr/lib/libkdeinit4_kmix.so
#39 0x080485a2 in _start ()
#0  0xb7f6c430 in __kernel_vsyscall ()

Comment 1 FiNeX 2008-11-10 14:37:22 UTC

If you have some free time, you could install the debug enabled packages in order to provide a more useful backtrace (see this guide:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
)

Thanks! :)

Comment 2 Oliver Putz 2008-11-23 19:33:28 UTC

Might be related to bug #170873 and / or bug #173564. But as neither of those bugs can be reproduced by the reporter, a better backtrace for this one would be nice indeed (see comment #1).

Comment 3 Christian Esken 2008-12-07 17:36:09 UTC


*** This bug has been marked as a duplicate of bug 174380 ***