Steps how to reproduce with "LibreOffice 3.6.4.3 rc" German UI/ German Locale [Build-ID: 2ef5aff] {pull date 2012-11-28} on German WIN7 Home Premium (64bit) 1. Launch LibO, if necessary menu 'Tools -> options -> LibO -> General -> Use LibO File dialog 2. From Start Center open New Text document, type few words 3. menu 'File -> Save -> <... Connect to server> Dialog opens 3. Name = Collab Type = FTP Host = bielefeldundbuss.de Login = f0023e73 Path = <ok> > Folder becomes created in overview in "Locations" pane 4. Click "Collab" Folder in overview pane > Dialog appears and asks for password 5. Password = ngoagnoi6lf <ok> > Folder Listing on Server appears 6. Save document as mycummy.odt, > you will see it in the folder 7. Close Document 8. Menu 'Open -> Location-Collab > Still Server Contents listed 9. Click your Dummy Document > Appears in File Name Pane 10. <Open> Bug: General Input- / Output Error
On pc Debian x86-64 with 3.6 sources updated today (commit b14f981e055bde9243c82d3ca5bbd3e469a7eb40), I don't reproduce this. I just put "test2" on the file. Sorry if it's a naive idea/obvious..., but it could be interesting to know if it's the opening process which fails or if it's the saving process. Did you retrieve the file from your ftp in your local disk and open it with LO to check if it was ok?
@Julien: Thank you for testing. I did not check that particular document, but for me that's a general problem i saw with various documents. I can open your document you left on the sever via Seamonkey browser without problems (Writer is listed as helper application), and save it again. But file open fails via Libreoffice dialogs. You really followed my steps 8 and following or did you a trick like "via browser" or similar? You can see in my steps that I saved the document on the server in step 6. I really did that from LibO, no trick with other software. But I get the error message when I try from LibO (It does not matter whether I try from LibO dialog or OS dialog. Same result with 3.5.7.2 (you can simply use <ftp://f0023e73@bielefeldundbuss.de/> in the file name pane as in OS dialog). Older versions and AOOo crash when I try that proceeding.
Rainer: I just tried to read the file I had put from LO and saw that you added "and more tested". To answer to your question, first I didn't understand because I didn't see "Connect to server" so I retrieved a file from Filezilla first but there was a password. Then I understood with Libo File Dialog and made the whole thing from LO (save + open) So, perhaps Windows only bug?
Inspired by Julien's results I tried Ubuntu 12 64 bit with LibO 3.5.4.2, and I was able to open the documents on my server without any problems following the modified proceeding (instructions step 8 and following) for 3.5 with ftp://f0023e73@bielefeldundbuss.de/ in the filename input pane So this problem seems to be WIN only?
On Win7 64 with 3.6.3.2 (build 58f22d5), I can reproduce the problem, so put the status at "NEW".
“Lotus Symphony Release 3.0.1 Revision 20120110.2000” on German WIN7 Home Premium (64bit) does the job without a murmur, so we should be able, too. For the sake of completeness: I also see the problem when I try to open the document with "read only" checked. This bug has impact to TDF documents interchange, document sharing and co working, so I increase severity to "Major"
Rainer: do you have the same with WebDav, ssh or Windows shared directories? (I don't even succeed in configuring the last one on LO)
@Julien: Unfortunately ftp is the only possibility where I know what that is ...
I gave a try to ssh, impossible to save something on it. put fdo#57806 in see also
Just for information, on MacOS 10.7 with LO 3.6.3, I can save and open a file on an ftp. (However, I can't even access ssh location)
bfoman: would it be possible by any chance to have a bt (even if it's not a crash)?
Confirmed with: LO 3.6.3.2 Build ID: 58f22d5 Windows XP Professional SP3 Got General Input- / Output Error and "Object not accessible. The object cannot be accessed due to insufficient user rights." error. I haven't been asked for a password while opening and did not selected Remember password at saving. As for bt - should I break after that error?
When Remember password at saving is selected I just have General IO error.
Rainer: had you get exactly the same message as the bfoman's one? (without checking remember password)
The first part of the message is exactly mine, I can't tell what causes that he can see additional info "Object not accessible ...", currently I do not understand that "remember password" thingy, I will do some additional tests tomorrow.
Opening a document via FTP in Writer File - Open - (example) ftp://server/document.odt causes the same error. Tested with: Windows 7 Professional 64-bit Windows 8 Pro 64-bit LibreOffice 4.0.3.3 (Build ID: 0eaa50a932c8f2199a615e1eb30f7ac74279539) LibreOffice 4.1.0.0.beta1 Build ID: 5271b34bec742e190e2fe5a7dadb7334a705b54 Searched for the problem with Process Monitor (Sysinternals). Reason for this error: LibreOffice wants to write a temporary file on C: instead of writing to the temp-directory of the user. Writing and deleting directly on C: is not allowed in Win 7 and 8 as normal user, only as admin. When you start LibreOffice as admin, everything is ok, but not as usual (domain-)user.
news4roland: thank you for your interesting feedback. Tor: the last feedback could help to solve this tracker but looking at ucb/source/ucp/ftp with grep or Opengrok, I don't know where is the Windows specific part. Any code pointer/idea?
** 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 (4.4.1 or later) 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) http://downloadarchive.documentfoundation.org/libreoffice/old/ 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
** 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.0.5 or 5.1.2 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) http://downloadarchive.documentfoundation.org/libreoffice/old/ 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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.2.7 or 5.3.3 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) http://downloadarchive.documentfoundation.org/libreoffice/old/ 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! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Resolving this bug with INSUFFICIENT since it's so old that is probably obsolete by now, is too generic and doesn't include enough how to reproduce information.