Bug 174031 - kmix crashes when envyng loads nvidia driver
Summary: kmix crashes when envyng loads nvidia driver
Status: RESOLVED DUPLICATE of bug 174037
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-01 13:01 UTC by kioftes
Modified: 2008-11-06 19:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kioftes 2008-11-01 13:01:37 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

kmix crashes when loading nvidia drivers with envyng. Causes signal 6 (SIGABRT). I am running kubuntu intrepid (AMD64), with kde 4.1.2 on a geforce 6100. The pc is an acer laptop, aspire 9302wsmi series. Backtrace:


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)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f76b24b16f0 (LWP 5570)]
(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)
[KCrash handler]
#5  0x00007f76b1d25fd5 in raise () from /lib/libc.so.6
#6  0x00007f76b1d27b43 in abort () from /lib/libc.so.6
#7  0x00007f76b09f66b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007f76b09f67fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007f76b124f363 in ?? () from /usr/lib/libsolid.so.4
#10 0x00007f76b124f677 in ?? () from /usr/lib/libsolid.so.4
#11 0x00007f76b0afb134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#12 0x00007f76b125ed02 in ?? () from /usr/lib/libsolid.so.4
#13 0x00007f76b12818ac in ?? () from /usr/lib/libsolid.so.4
#14 0x00007f76b0746ea3 in ?? () from /usr/lib/libQtDBus.so.4
#15 0x00007f76b074deef in ?? () from /usr/lib/libQtDBus.so.4
#16 0x00007f76b0af5da5 in QObject::event () from /usr/lib/libQtCore.so.4
#17 0x00007f76afb51c3d in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#18 0x00007f76afb599ea in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0x00007f76b191ab8b in KApplication::notify () from /usr/lib/libkdeui.so.5
#20 0x00007f76b0ae6d61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#21 0x00007f76b0ae79fa in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#22 0x00007f76b0b0f4d3 in ?? () from /usr/lib/libQtCore.so.4
#23 0x00007f76ad1add3b in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#24 0x00007f76ad1b150d in ?? () from /usr/lib/libglib-2.0.so.0
#25 0x00007f76ad1b16cb in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#26 0x00007f76b0b0f15f in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#27 0x00007f76afbe3a9f in ?? () from /usr/lib/libQtGui.so.4
#28 0x00007f76b0ae5682 in QEventLoop::processEvents ()
   from /usr/lib/libQtCore.so.4
#29 0x00007f76b0ae580d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0x00007f76b0ae7cbd in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#31 0x00007f76b208152a in kdemain () from /usr/lib/libkdeinit4_kmix.so
#32 0x00007f76b1d11466 in __libc_start_main () from /lib/libc.so.6
#33 0x0000000000400659 in _start ()
#0  0x00007f76b1d9b5f0 in nanosleep () from /lib/libc.so.6
Comment 1 Oliver Putz 2008-11-02 11:26:23 UTC
Hello,

Thanks for your report. It sounds as if you are able to reproduce the crash. So 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?
Comment 2 Christian Esken 2008-11-06 19:43:57 UTC
Strangely enough, I receive 2 pretty similar bug reports of this within 1,5 hours. Probably one original, and one downstream report. Marking this as a dup of the other.

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