Good evening,

since I installed KDE 4.8 everytime I boot I get a crash report.
Sometimes I get a second crash report which I figured is connected to KMix in this case I have to start KMix manually...

So, the crashes are connected to plasma applets or system trays. How do I find out which one causes the other crash and more important how do I shut down the crashes completely?

I already reinstalled all KDE packages, but it didn't help.

Thanks in regard.

you can try resetting your plasma desktop to the defaults and then adding widgets and panels back to determine which is causing the crash, resetting in of itself may resolve your problem if it's a corrupt rc or setting incompatibility file that's the cause

Code: Select all

kquitapp plasma-desktop
 sleep 20s
 mkdir -p $HOME/plasma-config/
 mv $(kde4-config --localprefix)/share/config/plasma-desktop* $HOME/plasma-config/
plasma-desktop &

What does the crash report say?

I would guess that it's related to the activity manager, as far as I know it's a known bug in 4.8.

@google01103

I tried to reset plasma, but it still crashes.
I'll upload the crash report from the reboot after plasma reset.

@Hans
Sure thing.

The report itself is empty.

If you go to the Developer Information tab, it should print out a backtrace. If you need to - please install debug symbols to get a more complete trace. Once you have that backtrace, please post that here.

bcooksley wrote:If you go to the Developer Information tab, it should print out a backtrace. If you need to - please install debug symbols to get a more complete trace. Once you have that backtrace, please post that here.

Since I get the same crash.. here is the backtrace:
(I'm (almost) certain that arch installs debugging symbols and development versions of packages automatically, but the trace still contains the "??()" `s, any idea to fix that ?)

Code: Select all

Application: KDE Daemon (kdeinit4), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0056c21780 (LWP 604))]

Thread 3 (Thread 0x7f003954c700 (LWP 669)):
#0  0x00007f0051145cd6 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#1  0x00007f0051146c5d in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007f00511475f2 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#3  0x00007f003960bb66 in ?? () from /usr/lib/libgio-2.0.so.0
#4  0x00007f005116c186 in ?? () from /usr/lib/libglib-2.0.so.0
#5  0x00007f0046fdd354 in ?? () from /usr/lib/libGL.so.1
#6  0x00007f00554b2daa in start_thread () from /lib/libpthread.so.0
#7  0x00007f005422555d in clone () from /lib/libc.so.6
#8  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f0038b3f700 (LWP 686)):
#0  0x00007f00554b5dcf in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0
#1  0x00007f0051146e73 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007f0051147289 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007f005586f126 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#4  0x00007f005583ee52 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#5  0x00007f005583f0a7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#6  0x00007f005573fd17 in QThread::exec() () from /usr/lib/libQtCore.so.4
#7  0x00007f005581ec9f in ?? () from /usr/lib/libQtCore.so.4
#8  0x00007f0055742d3b in ?? () from /usr/lib/libQtCore.so.4
#9  0x00007f0046fdd354 in ?? () from /usr/lib/libGL.so.1
#10 0x00007f00554b2daa in start_thread () from /lib/libpthread.so.0
#11 0x00007f005422555d in clone () from /lib/libc.so.6
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f0056c21780 (LWP 604)):
[KCrash Handler]
#6  0x00007f0054177975 in raise () from /lib/libc.so.6
#7  0x00007f0054178deb in abort () from /lib/libc.so.6
#8  0x00007f00541709ce in __assert_fail_base () from /lib/libc.so.6
#9  0x00007f0054170a72 in __assert_fail () from /lib/libc.so.6
#10 0x00007f0030f7c54b in snd_hctl_handle_events () from /usr/lib/libasound.so.2
#11 0x00007f0030f879a9 in snd_mixer_handle_events () from /usr/lib/libasound.so.2
#12 0x00007f003124984d in ?? () from /usr/lib/kde4/kded_kmixd.so
#13 0x00007f00312420aa in ?? () from /usr/lib/kde4/kded_kmixd.so
#14 0x00007f00558590d6 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#15 0x00007f00549b08c4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#16 0x00007f00549b5743 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0x00007f0056608646 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#18 0x00007f005584006c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#19 0x00007f005584390a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#20 0x00007f005586ec93 in ?? () from /usr/lib/libQtCore.so.4
#21 0x00007f00511468bd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0x00007f00511470b8 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x00007f0051147289 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0x00007f005586f0bf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0x00007f0054a53f1e in ?? () from /usr/lib/libQtGui.so.4
#26 0x00007f005583ee52 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0x00007f005583f0a7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0x00007f0055843c05 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#29 0x00007f00420f8e35 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#30 0x00000000004083e4 in _start ()


(May not be relevant) Also, when I have a script containing the use of kdialog enabled at startup, two instances of the "Crash Reporting Assistant" shows up, apparently for the same crash.

Thanks manasij7479 for posting the backtrace.

So, I'm not the only one.
I will have to be patient.

This is https://bugs.kde.org/show_bug.cgi?id=209975 which is probably an ALSA bug. At least some comments indicate, that running some ALSA setup tools fixes the issue.

cfeck wrote:This is https://bugs.kde.org/show_bug.cgi?id=209975 which is probably an ALSA bug. At least some comments indicate, that running some ALSA setup tools fixes the issue.

Guten Abend

I have to thank you for the link. It seems to be solved now after running

Code: Select all

alsactl init

as root.

I got no crash report after boot for the first time!

Thanks!!

SPK wrote:

Code: Select all

alsactl init

Unfortunately, that did not prevent the crash message for me.
(Maybe because I played around with alsamixer quite a bit)

@manasij7479: I would recommend following that bug for possible fixes to your issue, as those who are working on the bug are likely to know more about this issue.