https://bugs.kde.org/show_bug.cgi?id=383069
Albert Vaca <albertv...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Albert Vaca <albertv...@gmail.com> ---
I can effectively confirm that this is an SSHFS 3.0 bug, which has been fixed
in 3.1 but for some reason reintroduced in 3.2 (??).
We already have a fix for it on the desktop side [1], that disables the buggy
feature of SSHFS. But, since we can't guarantee distros are gonna adopt the
fixed version of KDE Connect before they adopt SSHFS 3.0 (or 3.2) I've also
written a "fix" for the Android app, which will just abort the transfer with an
error. This way, at least we don't cause data corruption/loss.
[1]
https://commits.kde.org/kdeconnect-kde/aec736fe562f7bf35663557ba6629fa53bc45a71
[2]
https://commits.kde.org/kdeconnect-android/83c8a30a715470ff7208bd217d3373a34ecd7e98
--
You are receiving this mail because:
You are watching all bug changes.
