Version: (using KDE 4.1.2) OS: Linux Installed from: Ubuntu Packages 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 0xb65398d0 (LWP 6246)] (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 0xb806c430 in __kernel_vsyscall () #7 0xb7ec1880 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb7ec3248 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb767e795 in qt_message_output () from /usr/lib/libQtCore.so.4 #10 0xb767e872 in qFatal () from /usr/lib/libQtCore.so.4 #11 0xb767e915 in qt_assert () from /usr/lib/libQtCore.so.4 #12 0xb7a8e57a in ?? () from /usr/lib/libsolid.so.4 #13 0xb7a8e87f in ?? () from /usr/lib/libsolid.so.4 #14 0xb778ba60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0xb778c7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb7aa0883 in ?? () from /usr/lib/libsolid.so.4 #17 0xb7ac649e in ?? () from /usr/lib/libsolid.so.4 #18 0xb7ac658a in ?? () from /usr/lib/libsolid.so.4 #19 0xb75e326e in ?? () from /usr/lib/libQtDBus.so.4 #20 0xb75ea627 in ?? () from /usr/lib/libQtDBus.so.4 #21 0xb7786771 in QObject::event () from /usr/lib/libQtCore.so.4 #22 0xb6db48ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #23 0xb6dbc76e in QApplication::notify () from /usr/lib/libQtGui.so.4 #24 0xb7cf872d in KApplication::notify () from /usr/lib/libkdeui.so.5 #25 0xb7776e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #26 0xb7777ae5 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #27 0xb7777cdd in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #28 0xb77a182f in ?? () from /usr/lib/libQtCore.so.4 #29 0xb675c6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #30 0xb675fda3 in ?? () from /usr/lib/libglib-2.0.so.0 #31 0xb675ff61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #32 0xb77a1478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #33 0xb6e4eee5 in ?? () from /usr/lib/libQtGui.so.4 #34 0xb777552a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #35 0xb77756ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #36 0xb7777da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #37 0xb6db4767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #38 0xb8006abb in kdemain () from /usr/lib/libkdeinit4_kmix.so #39 0x080485a2 in _start () #0 0xb806c430 in __kernel_vsyscall ()
Why don't create a file crach report upload that we just add it and send? Or put a sender on crash? That we just press one button that fill exactly all data. An example is the newest Netbeans crash report. I think that it will help much more and turn easy the reporting for newest users. Thank you. Francisco Ernesto Teixeira http://www.heidisql.com/
Well, the crash report won't help much, as the software is apparently built without debug information ("(no debugging symbols found)"). But lets try anyway: Please describre, when the crash happens? What did you do, is it reproducable, ...?
Could you please have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports, try to install the debugging packages for your distribution and post a more verbose backtrace?
This may be related to bug 173966 (similar backtrace). There are a lot of these backtraces of Kmix crashing in Kubuntu after updating apps or the entire distro, also after installing NVidia or ATI drivers.
Yeah! I'm using the NVidia driver. I followed the Christian advice and installed the kde-base-dbg that comes with the Qt4 dbg packages and I'm waiting for one crash and put it here.
Merging every crash with KMix and libsolid in the same bug report. Hopefully in this way we will receive really useful stack traces. *** This bug has been marked as a duplicate of bug 174380 ***