Bug 275401 - getting "KDE Daemon closed unexpectedly" message
Summary: getting "KDE Daemon closed unexpectedly" message
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2011-06-11 15:56 UTC by Buddy Goudeau
Modified: 2018-10-27 04:09 UTC (History)
4 users (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 Buddy Goudeau 2011-06-11 15:56:57 UTC
Version:           unspecified (using KDE 1.2) 
OS:                Linux

Every time I boot into PCLinuxOS FullMonty i get the message "KDE Daemon closed unexpectedly"

Reproducible: Always
Comment 1 Christoph Feck 2011-06-12 03:13:45 UTC
Please add the backtrace of the crash. For more information, see http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting
Comment 2 nyuszika7h 2011-07-30 11:57:44 UTC
I get the same error with Arch Linux 3.0-ARCH since I upgraded to the latest version of KDE from the testing repository.
Comment 3 quinntin 2011-07-30 23:30:18 UTC
Happens here too (KDE 4.7). It always crashes upon login (KMix crashes too but can be restarted).

----------------------------------------------

Application: kded4 ($Id$)
KDE Platform Version: 4.7.00 (4.7.0)
Qt Version: 4.7.3
Operating System: Linux 2.6.39-ARCH i686

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The crash can be reproduced every time.

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

Thread 3 (Thread 0xaedffb70 (LWP 1126)):
#0  0xb5b16d10 in clock_gettime () from /lib/librt.so.1
#1  0xb6cba425 in ?? () from /usr/lib/libQtCore.so.4
#2  0xb6d8ce26 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb6d8d17a in ?? () from /usr/lib/libQtCore.so.4
#4  0xb6d8b9c3 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb6d8ba5d in ?? () from /usr/lib/libQtCore.so.4
#6  0xb5a651ec in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#7  0xb5a66067 in ?? () from /usr/lib/libglib-2.0.so.0
#8  0xb5a666da in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#9  0xb6d8c4a7 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#10 0xb6d5d1fd in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#11 0xb6d5d441 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0xb6c60abb in QThread::exec() () from /usr/lib/libQtCore.so.4
#13 0xb6d3dd9d in ?? () from /usr/lib/libQtCore.so.4
#14 0xb6c63913 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb6bedc77 in start_thread () from /lib/libpthread.so.0
#16 0xb5fde43e in clone () from /lib/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 2 (Thread 0xae4d2b70 (LWP 1177)):
#0  0xb76ed424 in __kernel_vsyscall ()
#1  0xb5fd3d4e in poll () from /lib/libc.so.6
#2  0xb5a74e6b in g_poll () from /usr/lib/libglib-2.0.so.0
#3  0xb5a662b6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0xb5a66aeb in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#5  0xae58aae1 in ?? () from /usr/lib/libgio-2.0.so.0
#6  0xb5a8d2e4 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb6bedc77 in start_thread () from /lib/libpthread.so.0
#8  0xb5fde43e in clone () from /lib/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb5682b60 (LWP 1115)):
[KCrash Handler]
#7  0xb76ed424 in __kernel_vsyscall ()
#8  0xb5f39b8f in raise () from /lib/libc.so.6
#9  0xb5f3b515 in abort () from /lib/libc.so.6
#10 0xb5f32655 in ?? () from /lib/libc.so.6
#11 0xb5f32707 in __assert_fail () from /lib/libc.so.6
#12 0xadb9e3ae in snd_hctl_handle_events () from /usr/lib/libasound.so.2
#13 0xadbab441 in snd_mixer_handle_events () from /usr/lib/libasound.so.2
#14 0xadc691e1 in ?? () from /usr/lib/kde4/kded_kmixd.so
#15 0xadc808be in ?? () from /usr/lib/kde4/kded_kmixd.so
#16 0xadc8082e in ?? () from /usr/lib/kde4/kded_kmixd.so
#17 0xb6d645ad in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#18 0xb6d7335a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#19 0xb6dc1f45 in QSocketNotifier::activated(int) () from /usr/lib/libQtCore.so.4
#20 0xb6d7a6ff in QSocketNotifier::event(QEvent*) () from /usr/lib/libQtCore.so.4
#21 0xb628f084 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#22 0xb6294433 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#23 0xb747a8b1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#24 0xb6d5e1be in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#25 0xb6d8bb48 in ?? () from /usr/lib/libQtCore.so.4
#26 0xb5a65c4f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb5a663b0 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0xb5a666da in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb6d8c44a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0xb63426ba in ?? () from /usr/lib/libQtGui.so.4
#31 0xb6d5d1fd in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#32 0xb6d5d441 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0xb6d61bad in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#34 0xb628ced4 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#35 0xb520c7f9 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#36 0x0804f29a in _start ()

Report to https://bugs.kde.org
Comment 4 Christoph Feck 2011-07-30 23:56:10 UTC
Re comment #3, this is bug 278839 (and duplicates).
Comment 5 sombragris 2011-08-21 19:53:27 UTC
I'm seeing KDE Daemon crash *every time* at bootup, too. I'm using Slackware-current 64bit (post 13.37), with KDE SC 4.7.

Backtrace is as follows:


Application: KDE Daemon (kdeinit4), signal: Aborted
[Current thread is 1 (Thread 0x7f0d918ac780 (LWP 2290))]

Thread 2 (Thread 0x7f0d79da2700 (LWP 2333)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f0d79da1ab0 in ?? ()
#2  0x00007fff685ff7b2 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f0d918ac780 (LWP 2290)):
[KCrash Handler]
#6  0x00007f0d8e4b0fc5 in raise () from /lib64/libc.so.6
#7  0x00007f0d8e4b2976 in abort () from /lib64/libc.so.6
#8  0x00007f0d8e4a98a5 in __assert_fail () from /lib64/libc.so.6
#9  0x00007f0d73b2352b in snd_hctl_handle_events () from /usr/lib64/libasound.so.2
#10 0x00007f0d73b2e2c9 in snd_mixer_handle_events () from /usr/lib64/libasound.so.2
#11 0x00007f0d73de7669 in ?? () from /usr/lib64/kde4/kded_kmixd.so
#12 0x00007f0d73df4ea7 in ?? () from /usr/lib64/kde4/kded_kmixd.so
#13 0x00007f0d73df4e0d in ?? () from /usr/lib64/kde4/kded_kmixd.so
#14 0x00007f0d9028a60f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt/lib/libQtCore.so.4
#15 0x00007f0d902d211e in QSocketNotifier::activated(int) () from /usr/lib64/qt/lib/libQtCore.so.4
#16 0x00007f0d9029001b in QSocketNotifier::event(QEvent*) () from /usr/lib64/qt/lib/libQtCore.so.4
#17 0x00007f0d8f408724 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt/lib/libQtGui.so.4
#18 0x00007f0d8f40d1ba in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt/lib/libQtGui.so.4
#19 0x00007f0d91297d96 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#20 0x00007f0d902751ac in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt/lib/libQtCore.so.4
#21 0x00007f0d9029fbc9 in ?? () from /usr/lib64/qt/lib/libQtCore.so.4
#22 0x00007f0d8ae378f3 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f0d8ae380d0 in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f0d8ae3836d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f0d902a01ff in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt/lib/libQtCore.so.4
#26 0x00007f0d8f4ac79e in ?? () from /usr/lib64/qt/lib/libQtGui.so.4
#27 0x00007f0d90274562 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt/lib/libQtCore.so.4
#28 0x00007f0d902747ac in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt/lib/libQtCore.so.4
#29 0x00007f0d90278c4b in QCoreApplication::exec() () from /usr/lib64/qt/lib/libQtCore.so.4
#30 0x00007f0d81f189b7 in kdemain () from /usr/lib64/libkdeinit4_kded4.so
#31 0x0000000000407316 in _start ()
Comment 6 Christoph Feck 2011-08-21 22:37:42 UTC
Guys, why do you add backtraces to a bug report when you do not know if the original reporter is speaking of the same bug?

Regarding comment #5, this is also bug 278839.
Comment 7 Andrew Crouthamel 2018-09-22 01:42:01 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-27 04:09:55 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!