Version: 1.2.1 (using KDE 4.2.4) OS: Linux Installed from: Unlisted Binary Package Sometimes when I try to open file on ftp server in Dolphin I get an error message that Dolphin is unable to open that file and I should check my permissions. Permissions were fine and when I tried to open that file again one second later, it worked. Similar thing happens when I copy a lot of files at once, sometimes in the middle of progress I get the error message that Dolphin couldn't copy this file. When I tried to copy that file again, everything was fine. It doesn't really disturbs because it happens hardly ever but I should report it. I didn't install any plugins.
Sorry, I made a mistake with first part of this bug (opening the files). So far I was using bluefish to edit files o FTP server and there wasn't any problem. When I opened the file with KWrite, then I got an error which I descriped and it actually happens very often.
As bluefish is an GTK, non-KDE application it is using another method to communicate with the FTP files. Are you getting this error oftenly if you try to browse that FTP server with Dolphin/Konqueror/or the file dialog of any KDE app ? Have you tried with any other FTP server (just to test) ? Thanks
Yes, on other servers it happens too. On about 25 tested files this bug occured just once.
My experience is similar (v. 4.2.4). For example, I try to open a file on the local ftp server (vsftpd) with okular. Then I see a downloading progress bar and finally get `Could not open ftp://myserver.mynet/path_to_file/file.pdf`. The server log reads: CONNECT: Client "192.168.*.*" [ftp] OK LOGIN: Client "192.168.*.*", anon password "<no_password>" [ftp] OK DOWNLOAD: Client "192.168.*.*", "/path_to_file/file.pdf", 70223748 bytes, 3231.26Kbyte/sec This happens quite often. Sometimes (rarely) downloading fails: [ftp] FAIL DOWNLOAD: Client "192.168.*.*", "/path_to_file/file.pdf", 0.00Kbyte/sec
Please follow the instructions at http://www.konqueror.org/investigatebug/#http in order to get a log from kio_ftp, thanks.
see comment #5.