Version: SVN (using Devel) OS: Linux After starting kopete and choosing "Conenct" in its context menu, a second menu appeard and disappeared. After playing arround a bit with this anomaly I got the following crash: Thread 1 (Thread 0xb77d4780 (LWP 1894)): [KCrash Handler] #7 QList (this=0x7ac479c4) at ../../src/corelib/tools/qlist.h:118 #8 QWidget::actions (this=0x7ac479c4) at kernel/qwidget.cpp:3083 #9 0x049d505e in DBusMenuExporterDBus::GetChildren (this=0x87cb120, parentId=2049, names=...) at /usr/src/debug/libdbusmenu-qt-0.3.3/src/dbusmenuexporterdbus_p.cpp:51 #10 0x049d6565 in DBusMenuExporterDBus::qt_metacall (this=0x87cb120, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbf984a2c) at /usr/src/debug/libdbusmenu-qt-0.3.3/i686-redhat-linux-gnu/src/dbusmenuexporterdbus_p.moc:103 #11 0x045394cc in QDBusConnectionPrivate::deliverCall (this=0x87c5e20, object=0x87cb120, msg=..., metaTypes=..., slotIdx=7) at qdbusintegrator.cpp:909 #12 0x0453a7ed in QDBusConnectionPrivate::activateCall (this=0x87c5e20, object=0x87cb120, flags=4080, msg=...) at qdbusintegrator.cpp:819 #13 0x0453af3d in QDBusConnectionPrivate::activateObject (this=0x87c5e20, node=..., msg=..., pathStartPos=8) at qdbusintegrator.cpp:1388 #14 0x0453b49b in QDBusActivateObjectEvent::placeMetaCall (this=0x8d50170) at qdbusintegrator.cpp:1482 #15 0x043b3f7e in QObject::event (this=0x87cb120, e=0x8d50170) at kernel/qobject.cpp:1244 #16 0x0504c88c in QApplicationPrivate::notify_helper (this=0x861c5c0, receiver=0x87cb120, e=0x8d50170) at kernel/qapplication.cpp:4345 #17 0x05053206 in QApplication::notify (this=0xbf985444, receiver=0x87cb120, e=0x8d50170) at kernel/qapplication.cpp:3749 #18 0x05b6634b in KApplication::notify (this=0xbf985444, receiver=0x87cb120, event=0x8d50170) at /usr/src/debug/kdelibs-4.4.80/kdeui/kernel/kapplication.cpp:302 #19 0x043a1a73 in QCoreApplication::notifyInternal (this=0xbf985444, receiver=0x87cb120, event=0x8d50170) at kernel/qcoreapplication.cpp:726 #20 0x043a4d34 in sendEvent (receiver=0x0, event_type=0, data=0x85dfb60) at kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x85dfb60) at kernel/qcoreapplication.cpp:1367 #22 0x043a4eae in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1260 #23 0x043cc4f0 in sendPostedEvents (s=0x861e988) at kernel/qcoreapplication.h:220 #24 postEventSourceDispatch (s=0x861e988) at kernel/qeventdispatcher_glib.cpp:276 #25 0x004dd525 in g_main_dispatch (context=0x861e900) at gmain.c:1960 #26 IA__g_main_context_dispatch (context=0x861e900) at gmain.c:2513 #27 0x004e1268 in g_main_context_iterate (context=0x470490, block=1, dispatch=1, self=0x861c4b8) at gmain.c:2591 #28 0x004e1449 in IA__g_main_context_iteration (context=0x861e900, may_block=1) at gmain.c:2654 #29 0x043cbfd6 in QEventDispatcherGlib::processEvents (this=0x8626c68, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #30 0x050fccf6 in QGuiEventDispatcherGlib::processEvents (this=0x8626c68, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #31 0x043a060a in QEventLoop::processEvents (this=0xbf9853a4, flags=...) at kernel/qeventloop.cpp:149 #32 0x043a094a in QEventLoop::exec (this=0xbf9853a4, flags=...) at kernel/qeventloop.cpp:201 #33 0x043a4f77 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #34 0x0504b868 in QApplication::exec () at kernel/qapplication.cpp:3624 #35 0x080588f3 in main (argc=) at /usr/src/debug/kdenetwork-4.4.80/kopete/kopete/main.cpp:105 Reproducible: Didn't try
[Comment from a bug triager] - Do you use Desktop Compositing ? This may be related to bug 254066 (the root cause seems to be the same as the backtrace is mostly the same) Thanks
no I wasn't using composition
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
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 mark the bug 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 has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!