Bug 320151 - krdc blocks on startup while waiting for zeroconf
Summary: krdc blocks on startup while waiting for zeroconf
Status: RESOLVED WORKSFORME
Alias: None
Product: krdc
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.10.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-23 00:13 UTC by Dima Ryazanov
Modified: 2023-02-01 05:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dima Ryazanov 2013-05-23 00:13:46 UTC
When I start krdc, it freezes for 10-15 seconds before displaying a list of computers it finds. It's quite annoying, since I can't even connect to any of the bookmarked computers until krdc finishes displaying the results.

Reproducible: Always

Steps to Reproduce:
1. Start krdc
2.
3.
Actual Results:  
All of the UI is frozen for 10-15 seconds.

Expected Results:  
I should be able to use krdc immediately, and zeroconf resolution should be done in the background.

Here's a stacktrace from gdb. Note the "dbus_connection_send_with_reply_and_block" call.

(gdb) bt
#0  0x00007ffff3fbc3cd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ffff160f450 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2  0x00007ffff160e31d in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3  0x00007ffff15f8fc4 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4  0x00007ffff15fa434 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5  0x00007ffff15f976c in dbus_connection_send_with_reply_and_block () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#6  0x00007ffff5d750db in q_dbus_connection_send_with_reply_and_block (error=0x7fffffffcb70, timeout_milliseconds=-1, message=0xd77350, connection=<optimized out>)
    at qdbus_symbols_p.h:135
#7  QDBusConnectionPrivate::sendWithReply (this=0x886ee0, message=..., sendMode=1, timeout=-1) at qdbusintegrator.cpp:1907
#8  0x00007ffff5d6182b in QDBusConnection::call (this=this@entry=0xbead98, message=..., mode=mode@entry=QDBus::Block, timeout=<optimized out>) at qdbusconnection.cpp:597
#9  0x00007ffff5d80f96 in QDBusAbstractInterface::callWithArgumentList (this=this@entry=0x7fffffffce90, mode=mode@entry=QDBus::Block, method=..., args=...)
    at qdbusabstractinterface.cpp:468
#10 0x00007ffff6a324b9 in ServiceResolverNew (flags=8, aprotocol=-1, domain=..., type=..., name=..., protocol=-1, interface=-1, this=0x7fffffffce90)
    at ../../dnssd/avahi_server_interface.h:215
#11 DNSSD::RemoteService::resolveAsync (this=0x894980) at ../../dnssd/avahi-remoteservice.cpp:63
#12 0x00007ffff6a2ec1a in DNSSD::ServiceBrowserPrivate::gotNewService (this=0x889c20, name=..., type=..., domain=...) at ../../dnssd/avahi-servicebrowser.cpp:117
#13 0x00007ffff6a2f189 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./avahi-servicebrowser_p.moc:60
#14 DNSSD::ServiceBrowserPrivate::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./avahi-servicebrowser_p.moc:51
#15 0x00007ffff61550ef in QMetaObject::activate (sender=0x8ad150, m=m@entry=0x7ffff6c47bc0 <OrgFreedesktopAvahiServiceBrowserInterface::staticMetaObject>, 
    local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fffffffd120) at kernel/qobject.cpp:3539
#16 0x00007ffff6a3f807 in OrgFreedesktopAvahiServiceBrowserInterface::ItemNew (this=<optimized out>, _t1=21, _t2=1, _t3=..., _t4=..., _t5=..., _t6=5)
    at avahi_servicebrowser_interface.moc:136
#17 0x00007ffff6a3f95e in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at avahi_servicebrowser_interface.moc:65
#18 OrgFreedesktopAvahiServiceBrowserInterface::qt_static_metacall (_o=0x8ad150, _c=<optimized out>, _id=<optimized out>, _a=0x7fffffffd3c0)
    at avahi_servicebrowser_interface.moc:56
#19 0x00007ffff6a3fb3b in OrgFreedesktopAvahiServiceBrowserInterface::qt_metacall (this=0x8ad150, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffffffd3c0)
    at avahi_servicebrowser_interface.moc:107
#20 0x00007ffff5d71063 in QDBusConnectionPrivate::deliverCall (this=0x886ee0, object=0x8ad150, msg=..., metaTypes=..., slotIdx=8) at qdbusintegrator.cpp:951
#21 0x00007ffff615a5be in QObject::event (this=0x8ad150, e=<optimized out>) at kernel/qobject.cpp:1194
#22 0x00007ffff4c248ec in QApplicationPrivate::notify_helper (this=this@entry=0x66ef40, receiver=receiver@entry=0x8ad150, e=e@entry=0xbecd10) at kernel/qapplication.cpp:4567
#23 0x00007ffff4c2725b in QApplication::notify (this=this@entry=0x7fffffffdee0, receiver=receiver@entry=0x8ad150, e=e@entry=0xbecd10) at kernel/qapplication.cpp:4428
#24 0x00007ffff5931af6 in KApplication::notify (this=0x7fffffffdee0, receiver=0x8ad150, event=0xbecd10) at ../../kdeui/kernel/kapplication.cpp:311
#25 0x00007ffff614063e in QCoreApplication::notifyInternal (this=0x7fffffffdee0, receiver=receiver@entry=0x8ad150, event=event@entry=0xbecd10)
    at kernel/qcoreapplication.cpp:946
#26 0x00007ffff6144171 in sendEvent (event=0xbecd10, receiver=0x8ad150) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#27 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x648400) at kernel/qcoreapplication.cpp:1570
#28 0x00007ffff61444a3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463
#29 0x00007ffff616ee83 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#30 postEventSourceDispatch (s=s@entry=0x6730a0) at kernel/qeventdispatcher_glib.cpp:279
#31 0x00007ffff1a7ff05 in g_main_dispatch (context=0x674430) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3054
#32 g_main_context_dispatch (context=context@entry=0x674430) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3630
#33 0x00007ffff1a80248 in g_main_context_iterate (context=context@entry=0x674430, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3701
#34 0x00007ffff1a80304 in g_main_context_iteration (context=0x674430, may_block=1) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3762
#35 0x00007ffff616f016 in QEventDispatcherGlib::processEvents (this=0x649d60, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#36 0x00007ffff4cca1ae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x00007ffff613f38f in QEventLoop::processEvents (this=this@entry=0x7fffffffdd40, flags=...) at kernel/qeventloop.cpp:149
#38 0x00007ffff613f618 in QEventLoop::exec (this=this@entry=0x7fffffffdd40, flags=...) at kernel/qeventloop.cpp:204
#39 0x00007ffff6144cf6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#40 0x0000000000415ae0 in ?? ()
#41 0x00007ffff3ef0ea5 in __libc_start_main (main=0x415150, argc=1, ubp_av=0x7fffffffe038, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, 
    stack_end=0x7fffffffe028) at libc-start.c:260
#42 0x0000000000415dc9 in _start ()
Comment 1 Andrew Crouthamel 2018-11-10 03:14:18 UTC
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!
Comment 2 Andrew Crouthamel 2018-11-20 04:07:29 UTC
Dear Bug Submitter,

This is a reminder that 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-02 02:04:16 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-17 05:15:52 UTC
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!
Comment 5 Bug Janitor Service 2023-02-01 05:05:17 UTC
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!