Hello, I have noticed for a little while already that if I link some files to an activity, then display these files in a folderview and then right click and rename the file, not only it disappear from the list of linked files in the folderview (which could be fine) but it also disappear altogether from the actual place the file is in and no file with the new name is there instead. A new file however appears in the home folder with a name like "R{b�W�އm" which does have the content of the lost file. So in the end no data is being lost but it is a rather confusing behaviour. In dolphin however, it is not possible to rename files when displaying the path activities:/current which prevents the above problem happening. Probably folder view displaying activities:/current should be read only like in dolphin. (although activity folder in dolphin is also not strictly read only and allows you to create new text files within it, leading the the same kind of behaviour > the created text file is moved to home with a corrupted name) I noticed this bug back in plasma 5.7 and still present in 5.9.0. Sorry for not reporting before. Cheers Gauthier
Ivan?
> text files within it, leading the the same kind of behaviour > the created text > file is moved to home with a corrupted name This is a bug in activities kio - everything needs to be read-only. I'll check. > folderview and then right click and rename the file, But I'd say this is a bug in the folderview - that it behaves differently to dolphin.
Can you elaborate on what the bug in FV / the different behavior is?
Not sure whether last comment was addresses to Ivan or me... In FV in activity folder you can: Rename files Copy files Cut files Deleted files Create new files (text or html) Create links But you can't: Paste into it Create folders Now in dolphin you can: Copy files Deleted files Create new files (text or html) Create links But you can't: Rename files Cut files Paste into it Create folders Now it seems to me that it does make sense to allow for copy...and maybe delete files (can be convenient)...but not anything else in activity folders to avoid mishandling data (option is to have both FV and dolphin completely read only on activity folders). Thanks for looking into this. And btw amazing work on 5.9.0...very very slick so far!
Can't reproduce disappearance/strange renaming of linked file in: KDE neon Developer Edition - Unstable Branches Plasma: 5.11.90 Frameworks: 5.42.0 Qt: 5.9.3 Kernel 4.10.0-42-generic
Dolphin enables Cut and Rename only if the folder "supports moving". FolderView enables Cut only when "supports deleting" and always enables renaming. Also, FolderView only updates the actions before opening the context menu which means shortcuts are not updated immediately and stay enabled when selecting another file.
I just run into this problem, too. I have some activities with folder view, added one Libreoffice spreadsheet from a subfolder of my home folder to one activity so it was showing up on thaat desktop. Then I renamed it at the desktop and it disappeared. I found it after some search with a cryptic name Rk�?�{�.j�Z��l moved into the home folder. I tested the bug doing the same procedure with a textfile, similar result, but the file was called ��-��m. I think for some people that is like a data loss.
I can confirm that behavior :renaming a file in folder view showing files link to activities, lead to the filename being corrupt and moved to the home folder under new corrupt name. Plasma version 5.18.5 Framework: 5.70.0 Qt: 5.14.2 Fedora 32
Currently the behavior is plasmashell doesn't allow you to rename the file on the desktop.
(In reply to Fushan Wen from comment #9) > Currently the behavior is plasmashell doesn't allow you to rename the file > on the desktop. Even more so, renaming is now impossible anywhere in the "Activity folder", whereas opened in a folder view widget or in dolphin. Should the bug be marked as solved since it cannot be reproduced? Perhaps edits in the activity folder should now become a feature request, referencing this bug to not reproduce it when implementing the feature?