[systemsettings] [Bug 345459] New: Changing 'Downloads' default path attempts to move *ALL* files in $HOME to new location

Steven Gilberd steve at erayd.net
Tue Mar 24 02:56:14 GMT 2015


https://bugs.kde.org/show_bug.cgi?id=345459

            Bug ID: 345459
           Summary: Changing 'Downloads' default path attempts to move
                    *ALL* files in $HOME to new location
           Product: systemsettings
           Version: 5.2.1
          Platform: Gentoo Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: NOR
         Component: kcm_desktoppath
          Assignee: unassigned-bugs at kde.org
          Reporter: steve at erayd.net

Changing the default 'Download' path, then selecting 'yes' when asked whether I
would like existing files to be moved to the new location results in an attempt
to move *ALL* files in $HOME to $NEW_DOWNLOADS_DIR/$USER/. This completely
trashes the user's homedir.

If the new destination is an ephimeral location such as /tmp, the files may be
permanently lost if the user does not know where their files have gone before
the destination is cleared.

Reproducible: Always

Steps to Reproduce:
1. Ensure that the current default downloads (~/Downloads) directory exists.
2. In System Settings >> Applications >> Paths, change the default directory to
a new location.
3. When asked whether to move existing files, choose 'Yes'.

Actual Results:  
Without any further prompting, an attempt is made to move everything in the
user's home directory into a subfolder of the new default download location
(i.e. move $HOME/* to $NEW_DOWNLOAD_TARGET/$USERNAME/*).

Expected Results:  
The contents of the current default download location should be moved to the
new default download location. *ONLY* these files should be moved. Everything
else in the user's home directory should be left untouched.

This was reproduced on a new gentoo system, using @kde-frameworks-5.7 and
@kde-plasma-5.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list