Bug 279271 - kded crash when starting amarok
Summary: kded crash when starting amarok
Status: RESOLVED DUPLICATE of bug 209975
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 10:00 UTC by Christian Schmitt
Modified: 2011-08-30 06: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 Christian Schmitt 2011-08-03 10:00:11 UTC
Application: kded4 ($Id$)
KDE Platform Version: 4.7.00 (4.7.0) (Compiled from sources)
Qt Version: 4.7.3
Operating System: Linux 2.6.39-gentoo-r3 x86_64
Distribution: "Gentoo Base System release 2.0.3"

-- Information about the crash:
- What I was doing when the application crashed:

Logging into a kde 4.7.0 session and starting amarok crashes kded.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Daemon (kdeinit4), signal: Aborted
[Current thread is 1 (Thread 0x7f235f793760 (LWP 4841))]

Thread 3 (Thread 0x7f23491f7700 (LWP 4893)):
#0  0x00007f2359a99388 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#1  0x00007f2359a9a2f9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f2359a9acf2 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f23496c5e44 in ?? () from /usr/lib64/libgio-2.0.so.0
#4  0x00007f2359ac1851 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x00007f235df35ebc in start_thread () from /lib64/libpthread.so.0
#6  0x00007f235ccb0e0d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f2343fff700 (LWP 4894)):
#0  0x00007f235cca7f73 in poll () from /lib64/libc.so.6
#1  0x00007f2359a9a464 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f2359a9a95f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f235e2d9d76 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007f235e2ae012 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#5  0x00007f235e2ae294 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#6  0x00007f235e1c3f64 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4
#7  0x00007f235e28fc60 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#8  0x00007f235e1c67c5 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007f235df35ebc in start_thread () from /lib64/libpthread.so.0
#10 0x00007f235ccb0e0d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f235f793760 (LWP 4841)):
[KCrash Handler]
#6  0x00007f235cc0cb35 in raise () from /lib64/libc.so.6
#7  0x00007f235cc0deda in abort () from /lib64/libc.so.6
#8  0x00007f235cc055a1 in __assert_fail () from /lib64/libc.so.6
#9  0x00007f2341089849 in snd_hctl_handle_events () from /usr/lib64/libasound.so.2
#10 0x00007f2341094ad9 in snd_mixer_handle_events () from /usr/lib64/libasound.so.2
#11 0x00007f23413457e2 in Mixer_ALSA::prepareUpdateFromHW (this=0x20b9810) at /var/tmp/portage/kde-base/kmix-4.7.0/work/kmix-4.7.0/kmix/backends/mixer_alsa9.cpp:571
#12 0x00007f2341351f00 in Mixer_Backend::readSetFromHW (this=0x20b9810) at /var/tmp/portage/kde-base/kmix-4.7.0/work/kmix-4.7.0/kmix/backends/mixer_backend.cpp:103
#13 0x00007f2341352540 in Mixer_Backend::qt_metacall (this=0x20b9810, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7fff7dd7fe50) at /var/tmp/portage/kde-base/kmix-4.7.0/work/kmix-4.7.0_build/kmix/mixer_backend.moc:82
#14 0x00007f235e2c359f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#15 0x00007f235e30bf4e in QSocketNotifier::activated(int) () from /usr/lib64/qt4/libQtCore.so.4
#16 0x00007f235e2c9bb3 in QSocketNotifier::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007f235d44169c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#18 0x00007f235d4461fa in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#19 0x00007f235f0f82c2 in KApplication::notify (this=0x7fff7dd80810, receiver=0x1d7e030, event=0x7fff7dd80540) at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kdeui/kernel/kapplication.cpp:311
#20 0x00007f235e2aeccb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#21 0x00007f235e2d9718 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#22 0x00007f2359a99f1a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f2359a9a6f8 in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f2359a9a95f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f235e2d9d3a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#26 0x00007f235d4e75e6 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#27 0x00007f235e2ae012 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#28 0x00007f235e2ae294 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#29 0x00007f235e2b277b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#30 0x00007f235138d8cc in kdemain (argc=1, argv=0x1b50560) at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kded/kded.cpp:924
#31 0x0000000000407377 in launch (argc=1, _name=0x40d6f8 "kded4", args=0x0, cwd=0x0, envc=0, envs=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40d305 "0") at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kinit/kinit.cpp:734
#32 0x000000000040a24b in main (argc=2, argv=0x7fff7dd810f8, envp=0x7fff7dd81110) at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kinit/kinit.cpp:1849

Reported using DrKonqi
Comment 1 Olivier Trichet 2011-08-05 15:27:03 UTC

*** This bug has been marked as a duplicate of bug 242678 ***
Comment 2 Christian Schmitt 2011-08-30 06:43:00 UTC
This big is rather a duplicate of 209975. Changing accordingly.

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