Bug 136414

Summary: Regression in selecting download directory - kget attempts to save file under the name of directory
Product: [Applications] kget Reporter: Andrey Borzenkov <arvidjaar>
Component: generalAssignee: KGet authors <kget>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Kget file selection after going Up
Kget error dialog attempting to save file with highlighted directory name
Kget file selection dialog with cleared file name

Description Andrey Borzenkov 2006-10-28 14:43:32 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Mandriva RPMs
OS:                Linux

This appeared in 3.5.5. 3.5.4 was OK.

The problem happens the very first time kget is started, e.g. you click on file in Konqueror, select Save and up comes kget file selection dialog. Then the following happens:

1. I start in some directory, e.g. in this case ~/Download
2. I press Up to go to parent directory. Now the directory Download is highlighted. See first screenshot.
3. If I now press Save, I get an error "File file:///home/bor/Download" already exists. Do you want to replace it?" (second screenshot)
4. If I press cancel, the original file name is cleared (see third screenshot).
Comment 1 Andrey Borzenkov 2006-10-28 14:44:23 UTC
Created attachment 18299 [details]
Kget file selection after going Up
Comment 2 Andrey Borzenkov 2006-10-28 14:45:23 UTC
Created attachment 18300 [details]
Kget error dialog attempting to save file with highlighted directory name
Comment 3 Andrey Borzenkov 2006-10-28 14:46:12 UTC
Created attachment 18301 [details]
Kget file selection dialog with cleared file name
Comment 4 Jason W 2007-05-25 01:53:03 UTC
I had this as well with 3.5.5.  Seems a potentially serious error if it leads to someone inadvertently overwriting a directory.

While I wanted to second his report, I'd also like to mention that the issue seems to have disappeared with 3.5.7.  Same for you Andrey?
Comment 5 Andrey Borzenkov 2007-06-02 10:08:54 UTC
Apparently, yes; I cannot reproduce it anymore using the above sequence. So I guess it can be closed (do we have "fixed by itself" resolution? :)
Comment 6 Urs Wolfer 2007-06-02 10:36:38 UTC
Seems to be fixed.