Bug 243683 - Kmix crashed on startup
Summary: Kmix crashed on startup
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-07-05 20:18 UTC by Eric MacAlexsen
Modified: 2010-08-19 02:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric MacAlexsen 2010-07-05 20:18:19 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.13-server-1mnb i686
Distribution: "Mandriva Linux 2010.0"

What I was doing when the application crashed:
Started system, first thing to come up was Kmix crash report

 -- Backtrace:
Application: KMix (kdeinit4), signal: Aborted
[KCrash Handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb5e3d611 in raise () from /lib/i686/libc.so.6
#8  0xb5e3ef62 in abort () from /lib/i686/libc.so.6
#9  0xb5e3669e in __assert_fail () from /lib/i686/libc.so.6
#10 0xb3cca075 in snd_hctl_handle_events () from /usr/lib/libasound.so.2
#11 0xb3cd5be1 in snd_mixer_handle_events () from /usr/lib/libasound.so.2
#12 0xb3e30fd0 in Mixer_ALSA::prepareUpdateFromHW (this=0x8c23428) at /usr/src/debug/kdemultimedia-4.3.5/kmix/mixer_alsa9.cpp:570
#13 0xb3e3be3e in Mixer_Backend::readSetFromHW (this=0x8c23428) at /usr/src/debug/kdemultimedia-4.3.5/kmix/mixer_backend.cpp:100
#14 0xb3e3b171 in Mixer_Backend::qt_metacall (this=0x8c23428, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfc36bb8) at /usr/src/debug/kdemultimedia-4.3.5/build/kmix/mixer_backend.moc:71
#15 0xb760b144 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb760be65 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb7646885 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#18 0xb760fc8f in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#19 0xb617468c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#20 0xb617c0ce in QApplication::notify () from /usr/lib/libQtGui.so.4
#21 0xb6bd5b31 in KApplication::notify (this=0x8b18a90, receiver=0x8c20800, event=0xbfc36f44) at /usr/src/debug/kdelibs-4.3.5/kdeui/kernel/kapplication.cpp:302
#22 0xb75f4c0e in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#23 0xb7620c88 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb5d63b92 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb5d67468 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb5d6758e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb76208f1 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#28 0xb62164ba in ?? () from /usr/lib/libQtGui.so.4
#29 0xb75f326d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb75f36b9 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0xb75f5b50 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0xb6174504 in QApplication::exec () from /usr/lib/libQtGui.so.4
#33 0xb3e19013 in kdemain (argc=3, argv=0x8af85e8) at /usr/src/debug/kdemultimedia-4.3.5/kmix/main.cpp:71
#34 0x0804da54 in launch (argc=3, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x8af87d7 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x8050e85 "0") at /usr/src/debug/kdelibs-4.3.5/kinit/kinit.cpp:677
#35 0x0804e717 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at /usr/src/debug/kdelibs-4.3.5/kinit/kinit.cpp:1169
#36 0x0804eb64 in handle_requests (waitForPid=<value optimized out>) at /usr/src/debug/kdelibs-4.3.5/kinit/kinit.cpp:1362
#37 0x0804f85f in main (argc=2, argv=0xbfc37a74, envp=0xbfc37a80) at /usr/src/debug/kdelibs-4.3.5/kinit/kinit.cpp:1793

Reported using DrKonqi
Comment 1 Nicolas L. 2010-08-19 02:54:57 UTC

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