| Summary: | Copying files to desktop when it's a folder view showing files linked to current activity produces randomly named copies in home folder | ||
|---|---|---|---|
| Product: | [Unmaintained] kactivitymanagerd | Reporter: | Paul Worrall <p.r.worrall> |
| Component: | kio | Assignee: | Ivan Čukić <ivan.cukic> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | alx.kuzza, nate, nicolas.fella, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 22.12.1 | |
| Sentry Crash Report: | |||
|
Description
Paul Worrall
2021-10-25 09:55:16 UTC
Actually, expected result 1 is probably wrong as the user would think a copy of the file has been made. Better if the drop menu said "Link file to current activity" instead of the Move/Copy/Link here options. I can reproduce this with "kioclient5 cp file:///home/user/foo.txt activities:/current/" Update, still an issue with an interesting twist. 1) copy a file into an activity view window (folder view or dolphin) , as the result a file with a garbage name is created (this bug), you can check a contents and it matches the source including a timestamp. 2) copy the same file again and a message appears that a target file already exists. Sounds like a product should be changed to kio-extras. There seem to be multiple layers to this bug. I don't see any random files in my home folder, but copying/moving/linking doesn't do anything. In fact the whole activities folder is read-only. "kioclient stat activities:/current/" gives "ACCESS 0500". Looks like a UI bug that it still allows you to try to copy something. To make linking via dnd actually work one would presumably need to implement WorkerBase::symlink() in the activities worker Somewhat related: https://bugs.kde.org/show_bug.cgi?id=463589 A possibly relevant merge request was started @ https://invent.kde.org/network/kio-extras/-/merge_requests/218 Git commit 5d7399b594459151e4e9bf6ccbd50d3319385312 by Nicolas Fella. Committed on 29/12/2022 at 14:02. Pushed by nicolasfella into branch 'master'. [activities] Mark worker as read-only It's not possible to modify anything through this worker, so mark it as not writable That way UIs like Dolphin know to not enable actions like creating or dropping files M +1 -1 activities/activities.json https://invent.kde.org/network/kio-extras/commit/5d7399b594459151e4e9bf6ccbd50d3319385312 Git commit 538222427f4d0a0e5502d9d946170d4f98f1fab9 by Nicolas Fella. Committed on 29/12/2022 at 16:38. Pushed by nicolasfella into branch 'release/22.12'. [activities] Mark worker as read-only It's not possible to modify anything through this worker, so mark it as not writable That way UIs like Dolphin know to not enable actions like creating or dropping files (cherry picked from commit 5d7399b594459151e4e9bf6ccbd50d3319385312) M +1 -1 activities/activities.json https://invent.kde.org/network/kio-extras/commit/538222427f4d0a0e5502d9d946170d4f98f1fab9 This "fixes" the issue by preventing any attempt to drop/copy anything into the activities folder. Implementing that dropping a file links the file to the activity could be a welcome addition, but currently not implemented at all |