Version: kde4d (using KDE 4.3.0) Compiler: gcc 4, i86_x64 OS: Linux Installed from: Fedora RPMs Daemon crashed during a (long - 240Mb) update on Fedora 11 x86_64. The backtrace seems to finger nanosleep(), which I didn't see listed in the other kded4 crash reports. Note that the daemon restarted and hasn't crashed again. Backtrace: Application: KDE Daemon (kded4), signal SIGABRT 0x00000031f5ea3e61 in nanosleep () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fdc5e87b820 (LWP 2906))] Thread 2 (Thread 0x7fdc4c973910 (LWP 3026)): #0 0x00000031f5ed4f73 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00000030b803b05c in ?? () from /lib64/libglib-2.0.so.0 #2 0x00000030b803b3a0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x000000347bf6840e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #4 0x000000347bf3e5f2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x000000347bf3e9c4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x000000347be56f6b in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x000000347bf21f08 in ?? () from /usr/lib64/libQtCore.so.4 #8 0x000000347be59cd5 in ?? () from /usr/lib64/libQtCore.so.4 #9 0x00000031f6e0686a in start_thread (arg=<value optimized out>) at pthread_create.c:297 #10 0x00000031f5ede25d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fdc5e87b820 (LWP 2906)): [KCrash Handler] #5 0x00000031f5e332f5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x00000031f5e34b20 in *__GI_abort () at abort.c:88 #7 0x00000031f5e7005d in __libc_message (do_abort=2, fmt=0x7fff4cf24220 "config/beeeeb3dfe132a8a0633a017c99ce0c0-x86-64.cache-2\n7fdc5e8bf000-7fdc5e8c6000 r--s 00000000 fd:00 787341", ' ' <repeats 21 times>, "/usr/lib64/gconv/gconv-modules.cache\n7fdc5e8c6000-7fdc5e8c8000 rw-p 7fdc"...) at ../sysdeps/unix/sysv/linux/libc_fatal.c:170 #8 0x00000031f5e75a26 in malloc_printerr (action=3, str=0x31f5f35d48 "double free or corruption (!prev)", ptr=<value optimized out>) at malloc.c:6196 #9 0x000000347be9c9dc in QString::free(QString::Data*) () from /usr/lib64/libQtCore.so.4 #10 0x00000030674b2fc9 in ?? () from /usr/lib64/libkio.so.5 #11 0x00000030675213b7 in ?? () from /usr/lib64/libkio.so.5 #12 0x000000306752142e in KDirWatch::~KDirWatch() () from /usr/lib64/libkio.so.5 #13 0x0000003066606235 in KLibrary::resolveFunction(char const*) () from /usr/lib64/libkdeinit4_kded4.so #14 0x00000030666084e5 in KLibrary::resolveFunction(char const*) () from /usr/lib64/libkdeinit4_kded4.so #15 0x000000306660aa54 in KLibrary::resolveFunction(char const*) () from /usr/lib64/libkdeinit4_kded4.so #16 0x000000347bf54fdc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #17 0x000000347bf4ef93 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #18 0x0000003068b8ee2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x0000003068b95e5e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #20 0x0000003066204b16 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #21 0x000000347bf3fcbc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #22 0x000000347bf6aa72 in ?? () from /usr/lib64/libQtCore.so.4 #23 0x000000347bf6846d in ?? () from /usr/lib64/libQtCore.so.4 #24 0x00000030b8037abe in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #25 0x00000030b803b278 in ?? () from /lib64/libglib-2.0.so.0 #26 0x00000030b803b3a0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #27 0x000000347bf683b6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #28 0x0000003068c21b6e in ?? () from /usr/lib64/libQtGui.so.4 #29 0x000000347bf3e5f2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #30 0x000000347bf3e9c4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x000000347bf40b79 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #32 0x000000306660b37b in kdemain () from /usr/lib64/libkdeinit4_kded4.so #33 0x00000031f5e1ea2d in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff4cf25908) at libc-start.c:220 #34 0x0000000000400709 in _start () Current language: auto; currently minimal
This remembered me bug 165548 but the backtrace is different. As this only happened on a special situation it is unlikely that someone can reproduce it at will to fix it. Install the "kdelibs5-debuginfo" packages and, if you experience this issue again in any other update, please paste the backtrace here. (hopefully it will be complete) Thanks
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!
This bug (from 2009 for Fedora 11) is long dead, and the (automated?) "needs info" reminder should not, in my opinion, be jogging me for a open needsinfo for this. In any case, the bug (as far as I can remember) never happened again after I installed the debug packages, so there was never any occasion to reply, and I presume that I assumed that the bug was automatically closed when F11 was retired.