Skip to content

[local] non-harmful but annoying error "File not accessible" when saving editor with file within .tar.gz archive

Bugzilla Link 436624
Status NEW
Importance P3 normal
Reported Jun 04, 2014 15:02 EDT
Modified Jun 04, 2014 16:24 EDT
Version 3.6
Reporter Andre Dietisheim

Description

Created attachment 243954
The error dialog that shows up even though the archive was updated.

Steps to reproduce:

  1. ASSERT: have a .tar.gz archive in your local filesystem (ex. /tmp/archive.tar.gz)
  2. EXEC: inspect archive in "Remote Systems" View / LOCALHOST connection
  3. EXEC: open file within the archive with some Eclipse Editor (ex. HTML/Text editor)
  4. EXEC: save editor
  5. ASSERT: synch-job is started and shows up in progress view

Result:
Archive is updated but you get an dialog that informs you that your file is not accessible: "File Not Accessible", "The file ... has been deleted or is not accessible. Do you want to save your changes or close the editor without saving?"
If you check the path that the dialogs gives you you'll see that the file does not exist. It's a tmp-file within RemoteSystemsTempFiles. There's no harm though, the archive was updated, the "error" is a non-relevant information, most likely outdated.

  1. EXEC: hit "Save" and confirm the upcoming file-dialog.

Result:
Error pops up again (see above, same dialog).

File Not Accessible _001.png

File Not Accessible _001.png