Bug 234049 - Kmix crashes on startup on mandriva 2010.0
Summary: Kmix crashes on startup on mandriva 2010.0
Status: RESOLVED DUPLICATE of bug 209975
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-11 15:22 UTC by B. van der Harg
Modified: 2010-04-11 15:37 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 B. van der Harg 2010-04-11 15:22:28 UTC
Application that crashed: kmix
Version of the application: 3.5
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-desktop586-3mnb i686
Distribution: "Mandriva Linux 2010.0"

What I was doing when the application crashed:
Basically when kde loads kmix tends to crash. When I start it manually kmix does work. I'm running kde 4.3.5 btw.

 -- Backtrace:
Application: KMix (kdeinit4), signal: Aborted
[KCrash Handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb5e54611 in raise () from /lib/i686/libc.so.6
#8  0xb5e55f62 in abort () from /lib/i686/libc.so.6
#9  0xb5e4d69e in __assert_fail () from /lib/i686/libc.so.6
#10 0xb3ce7075 in snd_hctl_handle_events () from /usr/lib/libasound.so.2
#11 0xb3cf2be1 in snd_mixer_handle_events () from /usr/lib/libasound.so.2
#12 0xb3e4dfd0 in Mixer_ALSA::prepareUpdateFromHW (this=0x8394838) at /usr/src/debug/kdemultimedia-4.3.5/kmix/mixer_alsa9.cpp:570
#13 0xb3e58e3e in Mixer_Backend::readSetFromHW (this=0x8394838) at /usr/src/debug/kdemultimedia-4.3.5/kmix/mixer_backend.cpp:100
#14 0xb3e58171 in Mixer_Backend::qt_metacall (this=0x8394838, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfb31bd8) at /usr/src/debug/kdemultimedia-4.3.5/build/kmix/mixer_backend.moc:71
#15 0xb7622144 in QMetaObject::activate (sender=0x8389838, from_signal_index=4, to_signal_index=4, argv=0xbfb31bd8) at kernel/qobject.cpp:3112
#16 0xb7622e65 in QMetaObject::activate (sender=0x8389838, m=0xb76fe8b0, local_signal_index=0, argv=0xbfb31bd8) at kernel/qobject.cpp:3186
#17 0xb765d885 in QSocketNotifier::activated (this=0x8389838, _t1=11) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#18 0xb7626c8f in QSocketNotifier::event (this=0x8389838, e=0xbfb31f64) at kernel/qsocketnotifier.cpp:316
#19 0xb618b68c in QApplicationPrivate::notify_helper (this=0x824e510, receiver=0x8389838, e=0xbfb31f64) at kernel/qapplication.cpp:4065
#20 0xb61930ce in QApplication::notify (this=0x8248788, receiver=0x8389838, e=0xbfb31f64) at kernel/qapplication.cpp:3605
#21 0xb6becb31 in KApplication::notify () from /usr/lib/libkdeui.so.5
#22 0xb760bc0e in QCoreApplication::notifyInternal (this=0x8248788, receiver=0x8389838, event=0xbfb31f64) at kernel/qcoreapplication.cpp:610
#23 0xb7637c88 in socketNotifierSourceDispatch (source=0x8250728) at ../../src/corelib/kernel/qcoreapplication.h:213
#24 0xb5d7ab92 in IA__g_main_context_dispatch (context=0x82506a0) at gmain.c:1960
#25 0xb5d7e468 in g_main_context_iterate (context=0x82506a0, block=<value optimized out>, dispatch=1, self=0x824e600) at gmain.c:2591
#26 0xb5d7e58e in IA__g_main_context_iteration (context=0x82506a0, may_block=1) at gmain.c:2654
#27 0xb76378f1 in QEventDispatcherGlib::processEvents (this=0x824e4f0, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:406
#28 0xb622d4ba in QGuiEventDispatcherGlib::processEvents (this=0x824e4f0, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#29 0xb760a26d in QEventLoop::processEvents (this=0xbfb321c4, flags=) at kernel/qeventloop.cpp:149
#30 0xb760a6b9 in QEventLoop::exec (this=0xbfb321c4, flags={i = 0}) at kernel/qeventloop.cpp:201
#31 0xb760cb50 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#32 0xb618b504 in QApplication::exec () at kernel/qapplication.cpp:3525
#33 0xb3e36013 in kdemain (argc=3, argv=0x8205118) at /usr/src/debug/kdemultimedia-4.3.5/kmix/main.cpp:71
#34 0x0804da54 in _start ()

This bug may be a duplicate of or related to bug 213862

Reported using DrKonqi
Comment 1 Dario Andres 2010-04-11 15:37:29 UTC
This is being tracked at bug 209975. Regards

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