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.31-17-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: I added two konqueror web short cuts. I wanted to add new short cut for one entry but the "Change..." button remained dimmed if I selected that row from the shortcut list. So I double clicked the row, and it seems the possibility to edit the entry was presented, but something went kaboom along with. Note 1: It seems I was able to successfully edit the web shortcut (while writing this report). Note 2: After the modification finished, the "Change..." button was undimmed. -- Backtrace: Application: KDE Daemon (kdeinit4), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 QMetaObject::activate (sender=0x2f006500720061, m=<value optimized out>, local_signal_index=1, argv=0x7fffa9cc0a50) at kernel/qobject.cpp:3183 #6 0x00007f686c3473fa in QDBusConnectionPrivate::callWithCallbackFailed (this=0x7f686c55cba0, _t1=<value optimized out>, _t2=<value optimized out>) at .moc/release-shared/moc_qdbusconnection_p.cpp:112 #7 0x00007f686c310fef in QDBusConnectionPrivate::processFinishedCall (call=0x780340) at qdbusintegrator.cpp:1689 #8 0x00007f686c316196 in QDBusConnectionPrivate::sendWithReplyAsync (this=0x667ed0, message=<value optimized out>, receiver=0x673ce0, returnMethod=0x7f6867f0199c "1recreateDone()", errorMethod=0x0, timeout=<value optimized out>) at qdbusintegrator.cpp:1899 #9 0x00007f686c30015a in QDBusConnection::callWithCallback (this=0x75b4f0, message=..., receiver=0x0, returnMethod=0x7f6870323700 "\002", errorMethod=0xa1 <Address 0xa1 out of bounds>, timeout=0) at qdbusconnection.cpp:461 #10 0x00007f686c31d7a8 in QDBusAbstractInterface::callWithCallback (this=<value optimized out>, method=..., args=<value optimized out>, receiver=<value optimized out>, returnMethod=<value optimized out>, errorMethod=<value optimized out>) at qdbusabstractinterface.cpp:471 #11 0x00007f6867efc87f in runBuildSycoca (callBackObj=0x673ce0, callBackSlot=0x7f6867f0199c "1recreateDone()") at ../../kded/kded.cpp:94 #12 0x00007f6867eff3c4 in Kded::qt_metacall (this=0x673ce0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa9cc0f50) at ./kded.moc:82 #13 0x00007f68702a3ddc in QMetaObject::activate (sender=0x674310, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x7f6870323700) at kernel/qobject.cpp:3113 #14 0x00007f687029dd83 in QObject::event (this=0x674310, e=0x5) at kernel/qobject.cpp:1075 #15 0x00007f686e23eefc in QApplicationPrivate::notify_helper (this=0x6749d0, receiver=0x674310, e=0x7fffa9cc1550) at kernel/qapplication.cpp:4056 #16 0x00007f686e2461ce in QApplication::notify (this=0x7fffa9cc18a0, receiver=0x674310, e=0x7fffa9cc1550) at kernel/qapplication.cpp:4021 #17 0x00007f686ee75ab6 in KApplication::notify (this=0x7fffa9cc18a0, receiver=0x674310, event=0x7fffa9cc1550) at ../../kdeui/kernel/kapplication.cpp:302 #18 0x00007f687028ec2c in QCoreApplication::notifyInternal (this=0x7fffa9cc18a0, receiver=0x674310, event=0x7fffa9cc1550) at kernel/qcoreapplication.cpp:610 #19 0x00007f68702b9862 in QCoreApplication::sendEvent (this=0x67eca0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 QTimerInfoList::activateTimers (this=0x67eca0) at kernel/qeventdispatcher_unix.cpp:572 #21 0x00007f68702b725d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165 #22 0x00007f686d16fbce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #23 0x00007f686d173598 in ?? () from /lib/libglib-2.0.so.0 #24 0x00007f686d1736c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #25 0x00007f68702b71a6 in QEventDispatcherGlib::processEvents (this=0x674b70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #26 0x00007f686e2d34be in QGuiEventDispatcherGlib::processEvents (this=0x7f686c55cba0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #27 0x00007f687028d532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #28 0x00007f687028d904 in QEventLoop::exec (this=0x7fffa9cc17f0, flags=) at kernel/qeventloop.cpp:201 #29 0x00007f687028fab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #30 0x00007f6867effceb in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../kded/kded.cpp:938 #31 0x0000000000406da8 in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40a299 "0") at ../../kinit/kinit.cpp:677 #32 0x0000000000408cc0 in main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1740 Reported using DrKonqi
Using Kubuntu 9.10 (everything up-to-date). I was using Konqueror menu Settings / Configure Konqueror => Web Shortcuts. Without selecting any entries, I pressed the "New" button to add new entry, and when finished (no shortcut selected after this), I pressed "New" again to add another entry. I can now produce the "Change..." and "Delete" buttons remaining dimmed even if selected (it is possible to edit the entry by double-clicking). But I cannot produce the kded4 crash that triggered the bug report widget. The key point here is that no shortcut item should be selected when creating new one. Adding one or two entries makes no difference in reproducing the behavioral anomaly, but I do not know if it matters for the crash. Returning from "Change..." pop-up editing window with both "Cancel" or "OK" buttons fixes the behavioral anomaly.
As the crash is being tracked at bug 203285, I'm going to change this into a normal report about the other problem you described. Regards
Checked this issue with Kubuntu 10.10 (kde 4.6.2) and master/branch 4.6 compiled from sources, adding a web shurtcut, selecting it in the list enables the "Change..." and "Delete" buttons. I can not reproduce this issue here. Please try again with an up to date kde, thanks.
Cannot reproduce neither the crash nor the issue mentioned in comment #1. Feel free to reopen this ticket if the problem persists for you in the latest version of KDE, v4.7.2 as of this response.