Version: (using Devel) Installed from: Compiled sources OS: Linux Go to "Network" in Dolphin Places panel, click on Network. Click on "Add network folder". Select some remote connection type (for example, samba or sftp), fill with your data, click save&connect and... Konqueror (not Dolphin) opens showing the smb:// or fish:// location. I've started a process in Dolphin and ended with a Konqueror window opened and Dolphin with no clues about this new remote location. Expected behavior: Dolphin should add by default a new location to the Places panel, using the name the user labelled the connection in the wizard, and content should be displayed (after authorization, of course) in Dolphin.
I know that this bug is probably not directly related to Dolphin (remote:// is not Dolphin) but I cannot find the proper place where to fill the bug. Please reassign if needed, and please consider that this could be a junior job and that I'm willing in helping fix the problem. Thanks.
Created attachment 25091 [details] Use KRun instead of KToolInvocation::invokeBrowser This patch _should_ fix the behavior, that the new connection is opened in Konqueror instead of the responsible app for the according URL. But it currently doesn't work as expected, after finishing the wizard nothing happens - maybe someone with some more KDE/Qt knowledge can take a look at this.
Several bugs are 'waiting' for KToolInvocation::invokeFileManager(QString), which will be provided in KDE 4.2 as stated by 'aseigo' on #plasma: 01:42:37 < eliasp> aseigo: do you know, whether there are any plans to provide KToolInvocation::invokeFileManager() as you wrote here: http://bugs.kde.org/show_bug.cgi?id=151474#c2 01:43:09 < eliasp> could also be handy for bug 161384 01:43:36 < eliasp> and just discovered another one, where it might be handy... entering ~/ or /etc or another local URL into krunner starts konqueror... 01:44:25 <@aseigo> eliasp: yeah, i plan on that in 4.2. i'm going to also add an entry for that to the Default Applications control panel, and then hook those two things together 01:45:03 <@aseigo> eliasp: that's the main reason i haven't done the KToolInvocation thing yet 01:45:39 < eliasp> aseigo: nice to hear... so this bugs shouldn't be solved yet using a temporary workaround.. just wait, until kdelibs provides this in 4.2 .. ### So forget the patch I provided previously... just wait until the necessary KToolInvocation features are provided by the upcoming 4.2/SVN and make KToolInvocation run the filemanager instead of the browser.
I think this problem has really been fixed.