Hi,

Thanks for reporting this bug. Unfortunately, the most useful bits from the backtrace above are missing. Any chance you could install debug packages for QtDBus, kdelibs and kdenetwork, and then trigger the crash again and paste a new backtrace here.

Ok I tried to add the qtdbus debug but did not see it however I was able to add everything else. This is what the new report looks like.

Application: Desktop Sharing (krfb), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f6d62afd397 in QDBusAbstractInterface::callWithArgumentList(QDBus::CallMode, QString const&, QList<QVariant> const&) () from /usr/lib64/libQtDBus.so.4
#6  0x00007f6d65e3a1aa in OrgFreedesktopAvahiEntryGroupInterface::Reset (this=0x0) at /usr/src/debug/kdelibs-4.4.1/dnssd/avahi_entrygroup_interface.h:94
#7  0x00007f6d65e396e4 in DNSSD::PublicServicePrivate::serverStateChanged (this=0x28d3530, s=<value optimized out>) at /usr/src/debug/kdelibs-4.4.1/dnssd/avahi-publicservice.cpp:203
#8  0x00007f6d65e39b96 in DNSSD::PublicServicePrivate::qt_metacall (this=0x28d3530, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd864b2d0)
    at /usr/src/debug/kdelibs-4.4.1/build/dnssd/avahi-publicservice_p.moc:77
#9  0x00007f6d641d6aef in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x00007f6d65e3bbc3 in OrgFreedesktopAvahiServerInterface::StateChanged (this=0x7fffd864b100, _t1=1, _t2=<value optimized out>)
    at /usr/src/debug/kdelibs-4.4.1/build/dnssd/avahi_server_interface.moc:197
#11 0x00007f6d65e3bc6b in OrgFreedesktopAvahiServerInterface::qt_metacall (this=0x26c0230, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd864b6d0)
    at /usr/src/debug/kdelibs-4.4.1/build/dnssd/avahi_server_interface.moc:137
#12 0x00007f6d62aed9a6 in ?? () from /usr/lib64/libQtDBus.so.4
#13 0x00007f6d62af843f in ?? () from /usr/lib64/libQtDBus.so.4
#14 0x00007f6d641d3a29 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#15 0x00007f6d64b0376c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007f6d64b09d6b in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f6d659e8f8e in KApplication::notify (this=0x7fffd864c300, receiver=0x26c0230, event=0x29561a0) at /usr/src/debug/kdelibs-4.4.1/kdeui/kernel/kapplication.cpp:302
#18 0x00007f6d641c3cec in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#19 0x00007f6d641c6467 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#20 0x00007f6d641ed693 in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007f6d616c2d90 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f6d616c6bf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f6d616c6dac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f6d641ed1d3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007f6d64bb253e in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007f6d641c2612 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f6d641c29ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f6d641c672b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#29 0x000000000040c0f7 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdenetwork-4.4.1/krfb/main.cpp:109

please install:

qt4-debug
kdelibs4-debug
kdenetwork4-debug

if you can't find them activate the debug medias

This looks like a core kdelibs bug (related to the Avahi daemon): bug 215288..

Is there more you need from me. If so let me know if it is a duplicate just let me know and I will put it on my list to follow.
Thanks

@Dario: yes, I agree. Marking as a duplicate.

@William: Dario is right - the crash is actually occurring in another library, so I'll mark this as a duplicate of that bug. You should automatically be subscribed to the other bug when this happens.

*** This bug has been marked as a duplicate of bug 215288 ***