Version: (using KDE 4.2.2) Compiler: cc OS: Linux (i686) release 2.6.27-13-generic Installed from: Ubuntu Packages How to reproduce the bug: 1. In dolphin: Navigate to a folder on a remote computer using fish or ftp. 2. Create a so called place (the dolphin bookmark thing) to a remote folder. 3. In kate: Select File -> Open. 4. In the file dialog select the remote place. 5. Type letters in the text field labeled "Name". You will notice, that the file completion list, that pops up, uses the entries (files and dirs) from your home directory, rather than using the entries from the remote folder. This probably works in lots of applications (tested in kate and amarok) and seems to apply to the file save dialog as well. Thanks for fixing :)
Others involving confusion between remote and local locations in the file selector may be bug 187606 and bug 185463. Patch is attached to 185463, if you can compile from source then please try that.
(In reply to comment #1) > Others involving confusion between remote and local locations in the file > selector may be bug 187606 and bug 185463. Patch is attached to 185463, if you > can compile from source then please try that. I'm sorry, i can't compile from source. I've not enough time for that. :(
openSuSE KDE4.3Beta1, I see this exact behavior. If I save a network "places" location for quick access in the file dialog, it will work as long as the network share is mounted. The bug is that if you attempt to access the "places" location for a network location at a time when the network share is *not* mounted, then the stored location for that network location is "reset" to /home/$USER for some reason. This should not happen. In KDE3 if you saved/defined a "places" icon for a network location and then tried to access it when the drive was not mounted, you were just shown an empty directory listing (which is the correct behavior). The "places" definition remained intact and all you had to do was mount the drive and press F5 or refresh to access the files. Now in KDE4 if the network drive isn't mounted, your "places" definition is blown away due to KDE4 resetting it to a default value (this is the bug). I suspect the value is reset to whatever is defined in your "paths" settings as your default path. This needs to be fixed.
Works for me in KDE Frameworks 5.47.