Bug 379812 - Unable to write a remote tex file via kile
Summary: Unable to write a remote tex file via kile
Status: RESOLVED WORKSFORME
Alias: None
Product: kile
Classification: Applications
Component: user interface (show other bugs)
Version: 2.1.3
Platform: Ubuntu Linux
: NOR critical
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-14 13:19 UTC by Nauman Ahmed
Modified: 2022-12-06 05:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nauman Ahmed 2017-05-14 13:19:33 UTC
When I try to write to a remote tex file in a mounted file system. I receive the following error: 

"The document could not be saved, as it was not possible to write to /run/user/10024/gvfs/sftp:host=officepc,user=nauman/data/mytex.tex.

Check that you have write access to this file or that enough disk space is available."

Obviously the disk is not full. I have also tried by giving full permissions on the file but it doesn't work.  So much so it also deletes all the contents of the file when kile is closed. For a local tex file it works perfectly. I am running Ubuntu 16.04. My kile version is 2.1.3 using KDE Development Platform 4.14.16

best regards

Nauman
Comment 1 Christoph Feck 2017-05-15 23:01:36 UTC
Please check if this also happens when using an sftp:// path, instead of using gvfs.
Comment 2 Nauman Ahmed 2017-05-21 20:39:09 UTC
(In reply to Christoph Feck from comment #1)
> Please check if this also happens when using an sftp:// path, instead of
> using gvfs.

It is indeed an sftp:// path that is created automatically when a remote directory is mounted using Ubuntu "Connect to Server" i.e. I mounted the directory using sftp://nauman@officepc/data. Kate, which is another KDE software, works perfectly fine. Moreover it also works in my other laptop which has Ubuntu 14.04, Kile version 2.1.3 using KDE Development Platform 4.13.3.
Comment 3 Christoph Feck 2017-05-30 10:30:00 UTC
Thanks for the update, changing status.
Comment 4 Justin Zobel 2022-11-06 09:24:38 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-11-21 05:13:07 UTC
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!
Comment 6 Bug Janitor Service 2022-12-06 05:19:46 UTC
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!