| Username : Date : Action : Comments [ close all ] |
|
|
|
pirnaver : 29/04/02 04:11 PM : Incident created |
|
- I can't save files that I open directly from a ftp server.
Note that I can upload / download it, I just can't save it if I open it directly e.g with kwrite.
I think this worked in KDE 2.2.1 but not in KDE 2.2.2 and KDE 3.0.1.
|
|
|
|
Linegod_7611 : 29/04/02 04:53 PM : Reply received |
|
- They are most likely being loaded read-only. You could copy and paste them to a
new document and save them, or save them first, and then open them for viewing.
------
Note: If this answer resolves your problem, please remember to close this question.
|
|
|
|
pirnaver : 29/04/02 06:39 PM : More info provided |
|
- Original file is deleted when I try to save it (file that opened from a ftp server) and empty .part file gets uploaded. Kwrite reports that file is not saved.
/tmp/kde-gregor/
-rw------- 1 gregor gregor 3 apr 29 18:28 kwriteJzP2qa.txt
-rw------- 1 gregor gregor 0 apr 29 18:26 kwriteJzP2qa.txt.part
|
|
|
|
ecb : 30/04/02 11:27 PM : More info requested |
|
- I'd say you just have to save them under a new name / path, otherwise, since
they've been created for viewing, they'll be deleted right after.
ECB
|
|
|
|
pirnaver : 01/05/02 01:28 AM : More info provided |
|
- I just noticed that this DOES work on some other ftp servers.
Problems with passive file transfer?
|
|
|
|
Linegod_7611 : 01/05/02 12:06 PM : Reply received |
|
- I've been trying this on several different boxes, and it appears that behind the
firewall, it will not end the file properly, leaving '.part' (partial), and will not 'stop'
to allow a save. This does not happen will all passive transfers however, so I can't
say for certain if it is a 'KDE' problem, or a firewall/ftp server problem.
|
|
|
|
pirnaver : 01/05/02 07:54 PM : More info provided |
|
- I am not behind a firewall. The ftp server (on which I can't save files) is using proftpd. I also installed proftpd localy and I can save files on it just fine. Strange...
|
|
|
|
pirnaver : 01/08/02 10:43 PM : Incident closed |
|
- It seems it has something to do with permissions not being set corectly on the server...
|
|
|
