Application: plasma-desktop (0.3) KDE Platform Version: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)) (Compiled from sources) Qt Version: 4.6.0 Operating System: Linux 2.6.31-17-generic i686 Distribution: Ubuntu 9.10 -- Information about the crash: I was doin noting but a normal use an Plasma crashed. The Backtrace looks like it a Bug in glib. I know that tis bug exists but I don't know if my bug is related to that one. -- Backtrace: Application: Plasma-Arbeitsfläche (plasma-desktop), signal: Aborted The current source language is "auto; currently c++". [Current thread is 1 (Thread 0xb785c760 (LWP 1893))] Thread 2 (Thread 0xaacb5b70 (LWP 2105)): #0 0x0056d422 in __kernel_vsyscall () #1 0x001ece15 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:122 #2 0x00cac78d in __pthread_cond_wait (cond=0xab43930, mutex=0xab43918) at forward.c:139 #3 0x08210307 in QWaitConditionPrivate::wait (this=0xab15ec8, mutex=0xab15ec4, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 QWaitCondition::wait (this=0xab15ec8, mutex=0xab15ec4, time=4294967295) at thread/qwaitcondition_unix.cpp:159 #5 0x089ef102 in QHostInfoAgent::run (this=0xab15eb8) at kernel/qhostinfo.cpp:252 #6 0x0820f3ae in QThreadPrivate::start (arg=0xab15eb8) at thread/qthread_unix.cpp:244 #7 0x001e880e in start_thread (arg=0xaacb5b70) at pthread_create.c:300 #8 0x00c9f7ee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb785c760 (LWP 1893)): [KCrash Handler] #6 0x0056d422 in __kernel_vsyscall () #7 0x00bfd4d1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0x00c00932 in *__GI_abort () at abort.c:92 #9 0x00c33ee5 in __libc_message (do_abort=2, fmt=0xcf7438 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 #10 0x00c3dff1 in malloc_printerr (action=<value optimized out>, str=0x6 <Address 0x6 out of bounds>, ptr=0xb180068) at malloc.c:6217 #11 0x00c42806 in *__GI___libc_free (mem=0x6) at malloc.c:3677 #12 0x08209a1d in qFree (ptr=0xb180068) at global/qmalloc.cpp:60 #13 0x08321064 in ~QMetaCallEvent (this=0xac81ae8, __in_chrg=<value optimized out>) at kernel/qobject.cpp:562 #14 0x083138f5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9cec688) at kernel/qcoreapplication.cpp:1361 #15 0x08313a4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #16 0x0833d0df in QCoreApplication::sendPostedEvents (s=0x9d11b20) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #17 postEventSourceDispatch (s=0x9d11b20) at kernel/qeventdispatcher_glib.cpp:276 #18 0x015c4e88 in g_main_dispatch (context=0x9d11a98) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960 #19 IA__g_main_context_dispatch (context=0x9d11a98) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513 #20 0x015c8730 in g_main_context_iterate (context=0x9d11a98, block=<value optimized out>, dispatch=1, self=0x9d0ec30) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591 #21 0x015c8863 in IA__g_main_context_iteration (context=0x9d11a98, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654 #22 0x0833cbd5 in QEventDispatcherGlib::processEvents (this=0x9d0e360, flags=...) at kernel/qeventdispatcher_glib.cpp:407 #23 0x01e1bb75 in QGuiEventDispatcherGlib::processEvents (this=0x9d0e360, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #24 0x0830f4c9 in QEventLoop::processEvents (this=0xbfaafac4, flags=) at kernel/qeventloop.cpp:149 #25 0x0830f91a in QEventLoop::exec (this=0xbfaafac4, flags=...) at kernel/qeventloop.cpp:201 #26 0x08313b0f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #27 0x01d5e237 in QApplication::exec () at kernel/qapplication.cpp:3570 #28 0x0026d06e in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so #29 0x080485cb in _start () This bug may be a duplicate of or related to bug 220029. Possible duplicates by query: bug 220547, bug 220452, bug 220029, bug 208467, bug 198366. Reported using DrKonqi
Yes, this is a glibc issue: bug 196207. There is a way to really check it, but only if the crash is reproducible (It seems this was a random one) Regards *** This bug has been marked as a duplicate of bug 196207 ***
*** Bug 224109 has been marked as a duplicate of this bug. ***