kmix crash when change volume using thinkpad key

[Magi Su]

I am using thinkpad t400. and when I changed the volume of the system using volume up/down key , kmix crash.

backtrace:
Application: KMix (kmix), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f0cf74be6f0 (LWP 5995)]
[KCrash handler]
#5 0x00007f0cf709413e in ?? () from /usr/lib/libkdeinit4_kmix.so
#6 0x00007f0cf70967c2 in ?? () from /usr/lib/libkdeinit4_kmix.so
#7 0x00007f0cf5b0d134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#8 0x00007f0cf4b5df57 in QAction::triggered () from /usr/lib/libQtGui.so.4
#9 0x00007f0cf4b5e720 in QAction::activate () from /usr/lib/libQtGui.so.4
#10 0x00007f0cf696fdc9 in KGlobalAccelPrivate::_k_invokeAction (
    this=0x19fd4e0, actionId=@0x1a68600, timestamp=4099689)
    at /usr/include/qt4/QtGui/qaction.h:195
#11 0x00007f0cf69731de in KGlobalAccel::qt_metacall (this=0x19fdc50,
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffff4eeb80)
    at /build/buildd/kde4libs-4.1.2/obj-x86_64-linux-gnu/kdeui/kglobalaccel.moc:69
#12 0x00007f0cf5b0d134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#13 0x00007f0cf696f714 in OrgKdeKdedGlobalAccelInterface::invokeAction (
    this=0x19dd240, _t1=<value optimized out>, _t2=4099689)
    at /build/buildd/kde4libs-4.1.2/obj-x86_64-linux-gnu/kdeui/kdedglobalaccel_interface.moc:117
#14 0x00007f0cf69719fb in OrgKdeKdedGlobalAccelInterface::qt_metacall (
    this=0x19fd508, _c=QMetaObject::InvokeMetaMethod,
    _id=<value optimized out>, _a=0x7fffff4eef60)
    at /build/buildd/kde4libs-4.1.2/obj-x86_64-linux-gnu/kdeui/kdedglobalaccel_interface.moc:91
#15 0x00007f0cf5758ea3 in ?? () from /usr/lib/libQtDBus.so.4
#16 0x00007f0cf575feef in ?? () from /usr/lib/libQtDBus.so.4
#17 0x00007f0cf5b07da5 in QObject::event () from /usr/lib/libQtCore.so.4
#18 0x00007f0cf4b63c3d in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#19 0x00007f0cf4b6b9ea in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0x00007f0cf692cb8b in KApplication::notify (this=0x191d2c0,
    receiver=0x19fd508, event=0x1a67cc0)
    at /build/buildd/kde4libs-4.1.2/kdeui/kernel/kapplication.cpp:311
#21 0x00007f0cf5af8d61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#22 0x00007f0cf5af99fa in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#23 0x00007f0cf5b214d3 in ?? () from /usr/lib/libQtCore.so.4
#24 0x00007f0cf21bfd3b in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#25 0x00007f0cf21c350d in ?? () from /usr/lib/libglib-2.0.so.0
#26 0x00007f0cf21c36cb in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#27 0x00007f0cf5b2115f in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#28 0x00007f0cf4bf5a9f in ?? () from /usr/lib/libQtGui.so.4
#29 0x00007f0cf5af7682 in QEventLoop::processEvents ()
   from /usr/lib/libQtCore.so.4
#30 0x00007f0cf5af780d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0x00007f0cf5af9cbd in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#32 0x00007f0cf709352a in kdemain () from /usr/lib/libkdeinit4_kmix.so
#33 0x00007f0cf6d23466 in __libc_start_main () from /lib/libc.so.6
#34 0x0000000000400659 in _start ()
#0 0x00007f0cf6dad5f0 in __nanosleep_nocancel () from /lib/libc.so.6

[Jonathan Thomas (echidnaman)]

Hi,

Sorry it took so long for us to get around to this bug. If you are still experiencing this in Kubuntu 9.04 and/or with KDE 4.2, could you please install kdemultimedia-dbg and get a new backtrace? Thanks in advance.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!