Bug 248261 - Kmix crashes on computer startup.
Summary: Kmix crashes on computer startup.
Status: RESOLVED DUPLICATE of bug 209975
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: 3.6
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-18 16:45 UTC by simont
Modified: 2010-08-19 02:55 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 simont 2010-08-18 16:45:54 UTC
Application: kmix (3.6)
KDE Platform Version: 4.4.3 (KDE 4.4.3)
Qt Version: 4.6.2
Operating System: Linux 2.6.33.5-desktop-2mnb x86_64
Distribution: "Mandriva Linux 2010.1"

-- Information about the crash:
Kmix crashes at nearly every boot. Problem appeared just after the upgrade from Mandirva 2010.0 to Mandriva 2010.1.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: KMix (kdeinit4), signal: Aborted
[KCrash Handler]
#5  0x00007fb4816d7925 in raise () from /lib64/libc.so.6
#6  0x00007fb4816d8f40 in abort () from /lib64/libc.so.6
#7  0x00007fb4816d0871 in __assert_fail () from /lib64/libc.so.6
#8  0x00007fb4845ade1a in snd_hctl_handle_events () from /usr/lib64/libasound.so.2
#9  0x00007fb4845b78e9 in snd_mixer_handle_events () from /usr/lib64/libasound.so.2
#10 0x00007fb475ba74ce in Mixer_ALSA::prepareUpdateFromHW (this=0x12cd240) at /usr/src/debug/kdemultimedia-4.4.3/kmix/mixer_alsa9.cpp:570
#11 0x00007fb475bba327 in Mixer_Backend::readSetFromHW (this=0x4a6) at /usr/src/debug/kdemultimedia-4.4.3/kmix/mixer_backend.cpp:103
#12 0x00007fb475bb9e73 in Mixer_Backend::qt_metacall (this=0x12cd240, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc2a512b0)
    at /usr/src/debug/kdemultimedia-4.4.3/build/kmix/mixer_backend.moc:82
#13 0x00007fb482d37b5f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#14 0x00007fb482d839ee in QSocketNotifier::activated(int) () from /usr/lib64/libQtCore.so.4
#15 0x00007fb482d3ec83 in QSocketNotifier::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x00007fb481eca7cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007fb481ed0dcb in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#18 0x00007fb483256e46 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#19 0x00007fb482d24d5c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#20 0x00007fb482d4e5fa in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007fb47e364d20 in g_main_dispatch (context=0xfc8560) at gmain.c:1960
#22 IA__g_main_context_dispatch (context=0xfc8560) at gmain.c:2513
#23 0x00007fb47e368b88 in g_main_context_iterate (context=0xfc8560, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#24 0x00007fb47e368d3c in IA__g_main_context_iteration (context=0xfc8560, may_block=1) at gmain.c:2654
#25 0x00007fb482d4e243 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007fb481f7958e in ?? () from /usr/lib64/libQtGui.so.4
#27 0x00007fb482d23682 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007fb482d23a5c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007fb482d2779b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#30 0x00007fb475b8ea0a in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdemultimedia-4.4.3/kmix/main.cpp:72
#31 0x0000000000406b08 in _start ()

This bug may be a duplicate of or related to bug 243683, bug 209975.

Possible duplicates by query: bug 243683, bug 242678, bug 234049, bug 215581, bug 214884.

Reported using DrKonqi
Comment 1 Nicolas L. 2010-08-19 02:55:03 UTC

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