https://bugs.kde.org/show_bug.cgi?id=388025

            Bug ID: 388025
           Summary: Failed to create backup copy
           Product: kate
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kwrite-bugs-n...@kde.org
          Reporter: davestechs...@gmail.com
  Target Milestone: ---

Version 17.12.0
Arch Linux (fully updated)

To reproduce:
Kate Settings > Open/Save > Advanced tab
Under "Backup on Save" check local files and remote files. Apply. 
All other settings can be default.

Mount an SSHFS share. Save a file to that location. After saving it, attempt to
modify it and save it again (which will cause Kate to produce a backup file).
(You may need to close it and reopen the file before modifying. But I'm not
sure about that step.)

Expected result:

File is saved, backup copy is made and no error messages are producted.

Actual result - error message shown next:

Failed to create backup copy. -- Kate

For file /home/user/documents/test.txt no backup copy 
could be created before saving. 
If an error occurs while saving, you might lose the 
data of this file. 
A reason could be that the media you write to is full 
or the directory of the file is read-only for you.

[Try to Save Nevertheless]
[Cancel]

I checked permissions and disk space. Both are fine. Permissions have not
changed, my user owns the file and the containing directory and has rw
permissions. I'm using only about 2% of the space on the device.

Other editors (e.g., nano) work normally. If I disable creating backups in Kate
settings, Kate works normally and I do not receive any error messages.

On my systems that are still running Kate 17.08.3, saving to the SSHFS mounts
works as expected with backups. The problem happens when Kate is upgraded from
17.08.3 to 17.12.0 with no other changes to SSHFS or anything else (as far as I
can tell - of course, the Kate upgrade comes with a lot of other packages too,
so I cannot rule out some other component as being the cause of of issue).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to