Application that crashed: kded4 Version of the application: $Id: kded.cpp 944898 2009-03-26 13:01:25Z dfaure $ KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.28-15-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: Screen is not correct reserlution, it is smaller and had large amount of black to bottom of screen and to right of screen. This may be fixed in next KUbuntu. I am using KUbuntu 9.4 with amd 64. -- Backtrace: Application: KDE Dæmon (kdeinit4), signal: Aborted [KCrash Handler] #5 0x00007f46c2ea7fb5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x00007f46c2ea9bc3 in *__GI_abort () at abort.c:88 #7 0x00007f46c2ee7228 in __libc_message (do_abort=2, fmt=0x7f46c2fb1488 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:170 #8 0x00007f46c2eeccb8 in malloc_printerr (action=2, str=0x7f46c2fb15b8 "malloc(): memory corruption (fast)", ptr=<value optimized out>) at malloc.c:5994 #9 0x00007f46c2ef0351 in _int_malloc (av=0x7f46c31e2a00, bytes=64) at malloc.c:4172 #10 0x00007f46c2ef1828 in *__GI___libc_malloc (bytes=64) at malloc.c:3551 #11 0x00007f46c374b9bd in operator new () from /usr/lib/libstdc++.so.6 #12 0x00007f46c6574e58 in QMetaMethod::invoke (this=0x7fffcea7de50, object=0x1f84d10, connectionType=Qt::QueuedConnection, returnValue= {<QGenericArgument> = {_data = 0x0, _name = 0x0}, <No data fields>}, val0={_data = 0x0, _name = 0x0}, val1={_data = 0x0, _name = 0x0}, val2={_data = 0x0, _name = 0x0}, val3= {_data = 0x0, _name = 0x0}, val4={_data = 0x0, _name = 0x0}, val5={_data = 0x0, _name = 0x0}, val6={_data = 0x0, _name = 0x0}, val7={_data = 0x0, _name = 0x0}, val8={_data = 0x0, _name = 0x0}, val9={_data = 0x0, _name = 0x0}) at kernel/qmetaobject.cpp:1560 #13 0x00007f46c47df1f6 in qDBusUpdateDispatchStatus (connection=<value optimized out>, new_status=DBUS_DISPATCH_DATA_REMAINS, data=0x1f84d10) at ../../include/QtCore/../../src/corelib/kernel/qmetaobject.h:118 #14 0x00007f46bafa77bd in ?? () from /lib/libdbus-1.so.3 #15 0x00007f46bafaa605 in ?? () from /lib/libdbus-1.so.3 #16 0x00007f46bafbdcbb in dbus_watch_handle () from /lib/libdbus-1.so.3 #17 0x00007f46c47dff22 in QDBusConnectionPrivate::socketRead (this=0x1f84d10, fd=5) at ./qdbus_symbols_p.h:181 #18 0x00007f46c4822406 in QDBusConnectionPrivate::qt_metacall (this=0x1f84d10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffcea7e090) at .moc/release-shared/moc_qdbusconnection_p.cpp:89 #19 0x00007f46c6581ea2 in QMetaObject::activate (sender=0x2084c50, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xffffffffffffffff) at kernel/qobject.cpp:3113 #20 0x00007f46c65b90fe in QSocketNotifier::activated (this=0xffc, _t1=5) at .moc/release-shared/moc_qsocketnotifier.cpp:83 #21 0x00007f46c6586a73 in QSocketNotifier::event (this=0x2084c50, e=0x7fffcea7e660) at kernel/qsocketnotifier.cpp:316 #22 0x00007f46c3b31f4d in QApplicationPrivate::notify_helper (this=0x1fc6840, receiver=0x2084c50, e=0x7fffcea7e660) at kernel/qapplication.cpp:4056 #23 0x00007f46c3b3a18a in QApplication::notify (this=0x7fffcea7e980, receiver=0x2084c50, e=0x7fffcea7e660) at kernel/qapplication.cpp:4021 #24 0x00007f46c4c44abb in KApplication::notify (this=0x7fffcea7e980, receiver=0x2084c50, event=0x7fffcea7e660) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302 #25 0x00007f46c656c6ac in QCoreApplication::notifyInternal (this=0x7fffcea7e980, receiver=0x2084c50, event=0x7fffcea7e660) at kernel/qcoreapplication.cpp:610 #26 0x00007f46c6595d09 in socketNotifierSourceDispatch (source=0x1fca3b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #27 0x00007f46c25c520a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #28 0x00007f46c25c88e0 in ?? () from /usr/lib/libglib-2.0.so.0 #29 0x00007f46c25c8a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #30 0x00007f46c6595a8f in QEventDispatcherGlib::processEvents (this=0x1f4de70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #31 0x00007f46c3bcabdf in QGuiEventDispatcherGlib::processEvents (this=0xffc, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #32 0x00007f46c656af42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -827856768}) at kernel/qeventloop.cpp:149 #33 0x00007f46c656b314 in QEventLoop::exec (this=0x7fffcea7e8c0, flags={i = -827856688}) at kernel/qeventloop.cpp:201 #34 0x00007f46c656d5e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #35 0x00007f46bb1e2cf7 in kdemain (argc=1, argv=0x1f8ad70) at /build/buildd/kde4libs-4.3.2/kded/kded.cpp:938 #36 0x0000000000407215 in launch (argc=1, _name=0x40a4d5 "kded4", args=<value optimized out>, cwd=0x0, envc=0, envs=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40a3a1 "0") at /build/buildd/kde4libs-4.3.2/kinit/kinit.cpp:677 #37 0x0000000000408d3f in main (argc=2, argv=0x7fffcea7f498, envp=0x7fffcea7f4b0) at /build/buildd/kde4libs-4.3.2/kinit/kinit.cpp:1740 Reported using DrKonqi
@David: could this be a Qt-dbus upstream issue ? Thanks
The crash happens at new(), and it detects a memory corruption. So the corruption has to be created earlier, and it could be anywhere :( There is very little chance this is D-Bus related at all.
I agree with comment #2. I was about to say the same. If this crash isn't reproducible, I'm afraid we'll have to close the bug, we can't guess where the memory corruption happened.
@akb1982@hotmail.co.uk: is this bug reproducible? (does it always crash?) Thanks
Sorry, I've been away for a while. No this crash happened once, but I thought that I should report it to help others out. I don't know much about programming. I have Upgraded to Kubuntu 9.10 and have not had any problems since.
Thank you. Closing as this was a one time incident with lower possibilities of reproducing/fixing.