| Summary: | SFTP: when saving a file in a folder, that does not have write permission, the file is saved as empty | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] kiofuse | Reporter: | andriy.parhomenko |
| Component: | general | Assignee: | a.saoutkin |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | fabian, kio-bugs-null, sitter |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
andriy.parhomenko
2024-01-31 23:32:09 UTC
Doesn't seem to happen with kwrite. Are you sure this isn't simply caused by sublime text? KWrite does not use kio-fuse, it uses kio, as far as I know. The problem is with non-kde software, which would use gvfs normally. Sublime Text works perfectly in Gnome. I obviously routed kwrite through fuse :) gedit also works fine. > Maybe, this happens because of the bug, mentioned in TODO:
> "Bugfixes:
> - Check whether write access works before writing into the cache:
> Currently write access it not explicitly checked at all, possibly leading to data loss"
That shouldn't happen with sftp, which supports direct read/write and thus the file based cache isn't used.
That the folder needs write permissions implies that it wants to create a new file, probably for the create, write, rename dance. Creation and rename do perform proper access checks though in any case, as would f(data)sync.
Please try with "kio-fuse -d" (you might have to kill the running one first) and maybe even strace on sublime text.
My guess is that the create/write/rename dance is used, but the write for some reason doesn't happen successfully. That requires that creation was successful though, which contradicts missing write permissions on the containing folder.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |