I get an "I/O error" trying to save any libreoffice file into a directory mounted via sshfs who only accept own definied "user:group" permissions.
Following the pid with strace i ve noticed libreoffice do a
chown("/home/zmo/.libreoffice/3/user/backup/prova_libreoffice0.ods", 847, 847) = 0
during the save procedure. As mentioned above, my directory does not permit to store "user:user" files.
How can i workaround that, and first of all, which is the main reason to call chown/chmod saving files?
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Dear bug submitter!
Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.
To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement
Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.
not tested yet
3.6.3 on RFR 17 64 bit works correctly
(installed package : yum install fuse-sshfs.x86_64)
meanwhile, closing as WFM
If problem still exist, please, reopen this bug
I confirm the bug which I reproduce with version 184.108.40.206 (Build ID: 360m1 (Build:2))
I use Kubuntu 12.10 quantal.
I mounted manually a sshfs directory from a NAS (synology DS213, DSM 4.1). I can use all files in this mounted directory with dolphin, kate, and other applications (BTW identification done with RSA keys). I can open the same text document with Kate and LibreOffice. I can save it in Kate but NOT with LibreOffice. However, with LibreOffice I can save under another name or export as pdf. I guess that "overwriting" with the same name is for some reason not possible. I hope this help.
I had the same bug on latest Ubuntu 14.04 LTS 64 Bit Intel. I am mounting a share over sshfs from my Synology Diskstation. Opening files, and saving under a new(!) filename worked out of the box. Saving to an existing (e.g. the original filename) led to the I/O error.
I fiddled around with the sshfs mount options, and in the end one of the workaround options ("truncate") did work for me, i.e. if I mount using:
sshfs me@diskstation:/ diskstation -o workaround=truncate
does the trick.
Never confirmed by QA team - moving to UNCONFIRMED.
it was confirmed by other users though... so status NEW.
anyway has anybody the chance to retest with current LibO 220.127.116.11 and give an update of the bug status?
I can confirm this bug with LibreOffice 18.104.22.168 430m0(Build:2) on Ubuntu 14.04.2 64 bit.
I can confirm this bug with LibreOffice 22.214.171.124. The workaround=truncate does the trick for me as well.
OS: Linux Mint 7.2 64 bit.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice
(5.1.5 or 5.2.1 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!