Version: 4.6 (using KDE 4.6.5) OS: Linux I tried to make use of KDE's network capabilities and accessed a fish share via zeroconf ("zeroconf:/_ssh._tcp/x201"), but an empty directory is shown in konqueror. Accessing fish://x201.local:22 works fine. Konsole output: konqueror(4393)/kio (KIOJob) KIO::ListJobPrivate::slotRedirection: ListJob: Redirection from KUrl("zeroconf:/_ssh._tcp/x201") to KUrl("fish://x201.local:22") REJECTED! Workaround: With the help of rdieter of #fedora-kde, we found a workaround. if i add the following to "/usr/share/kde-settings/kde-profile/default/share/config/kdeglobals" in Fedora, it works. [KDE URL Restrictions][$i] rule_count=1 rule_1=redirect,zeroconf,,,fish,,,true I don't know if this is a concern in terms of security. If so, then kio_zeroconf should not show these network services at all. Otherwise zeroconf redirection should be allowed. Reproducible: Always Steps to Reproduce: Start konqueror and try to access a fish share ("network -> network services -> Remote Disk (fish) -> $host"). Make sure firewall allows zeroconf discovery and another host is available. Actual Results: A new empty directory opens, no error message in Dolphin except for console output. Expected Results: Either the requested files and folders of the remote host or visible error messages. Preferably the former. This has been tried on Fedora, Ubuntu and OpenSuSE, so i guess it's an upstream issue.
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!