Every time I access the network inside dolphin, it complains that "KDE has been built without Zeroconf support." Unfortunately, it won't go away no matter what, it reappears as soon as moving to the next network directory. Here are three scenarios I can think of: 1.) The power user: "I am well aware of that, now go away, please." 2,) The regular user without specific knowledge: "OK, but it works, so what do I miss? Could something break?" 3.) The beginner for whom everything has been taken care of so far: "What's that? Did I do something wrong? Help!" -) A simple notification that indicates possible missing functionality should probably not appear in red, and it should be gone for good once it was read and closed. -) If instead it is of such importance that every network operation triggers it anew, I would probably like to know more about it - be more descriptive or provide a link for further info. -) Besides, the "close" icon inside that red notification bar says "Close document" which seems a bit odd. Reproducible: Always
Created attachment 80402 [details] example screenshot
Thanks for the bug report. I guess that these error messages come from the "network:" kioslave.
Hi, seems that is rather from the zeroconf:/ kio-slave, see http://lxr.kde.org/source/kde/kdenetwork/kdnssd/ioslave/dnssd.cpp#164
IMHO, if a function is not working due to missing dependencies (which may actually be by choice), then the user should not be bothered with a non-working UI, especially if it's a non-vital, non-core feature.
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 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!
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!
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!