Bug 217178

Summary: setting desktop path moves/copies all files/directories from /home into /home/downloads
Product: [Applications] systemsettings Reporter: m.wege
Component: kcm_desktoppathAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: faure
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description m.wege 2009-12-03 11:13:02 UTC 
Version:            (using KDE 4.3.4)
Installed from:    Ubuntu Packages

I just saw that the paths in the systemsettingsmodule where incorrect (I had set them before correctly), so I attempted to correct them. Appart from Autostart they had all been reset to /home . So I set them correctly to

/home/user/Downloads
/home/user/Musik
/home/user/Pictures
/home/user/Movies

Then I got asked if I wanted items to be moved to new locations. I said no, because they are allready there.

Then the following happened: My complete /home was moved/copied (partly copied, partly moved) to /home/user/Downloads, so I had /home/user/Downloads/Movies and so on. Also the .kde and evering thing else was moved/copied, so that some apps crashed and I am still busy recovering my system. Please put the priority of the bug to "severe".
Comment 1 Christoph Feck 2009-12-03 11:44:37 UTC 

*** This bug has been marked as a duplicate of bug 193057 ***
Comment 2 Christoph Feck 2009-12-03 11:49:02 UTC 
According to bug 193057 the bug should have been fixed for KDE Workspace 4.3.4. It may be possible that either Ubuntu's packages do not include the commit 1055428, or that the fix is wrong. In the latter case, please reopen bug 193057.
Comment 3 David Faure 2009-12-03 12:02:04 UTC 
Are you sure you said "no" about moving the files? I just re-tested and the message box buttons are correctly handled - yes moves, no doesn't move.

I also re-tested, and my fix for bug 193057 works: the user is not asked anymore when the old path is the home directory. Surprising that you still had the bug with 4.3.4, indeed....