* Scenario: Editing a shared document with Libreoffice Online, CODE version (Collabora Online Development Edition), integrated with OwnCloud 9. * Events: Edit some text, fill some pages (more than one, say 2 or 3) Move the cursor to page 3, and write something more Wait until Autosave feature kicks in and autosaves the document. * Results: The cursor in the doc returns to the beginning of document. This happens also on big documents, not only on 2-3 pages. This makes CODE unusable for us, since this annoys users heavily, and severely interferes the ongoing work. * Expected results: Autosave does its job and you can continue working wherever you are in the document, without disturbances. * Possible workarounds: Might it be possible to disable Autosave feature until this is fixed. I haven't found the way to do it though. In standard LibreOffice, the autosave feature can be disabled in some of the Options menus, but I can't find any "Options" menus in Libreoffice Online-Collabora (could someone please tell me how to do it if possible?) I'm currently investigating modifing a file called LOOLWSD.XML, which mustbe somewhere in the Docker image for CODE. Any help would be appreciated.
Versions: This version of Collabora Online Development Edition (CODE) is powered by LOOLWSD 2.1.2 (git hash: 4f4593a) LOKit Collabora Office 5.3-15 (git hash: 6a0cbf1)
Tried to disable Autosave by using LOOL_NO_AUTOSAVE variable: https://gerrit.libreoffice.org/gitweb?p=online.git;a=blob_plain;f=loolwsd/README.vars;hb=41a1c0b3f953664edfe448ec60f4d11ceab5e86e I had to regenerate my image by editing the start-libreoffice.sh script and modifying the last line: su -c "export LOOL_NO_AUTOSAVE=1; /usr/bin/loolwsd --version --o:sys_template_path=/opt/lool/systemplate --o:lo_template_path=/opt/collaboraoffice5.3 --o:child_root_path=/opt/lool/child-roots --o:file_server_root_path=/usr/share/loolwsd" -s /bin/bash lool Then rebuilt my image with a new Dockerfile: FROM collabora/code ADD start-libreoffice.sh / ENTRYPOINT bash start-libreoffice.sh And then started again Collabora with my modified image. But it does not work as expected. WHen I modify a document, after some 15 seconds of inactivity it autosaves and takes me to the first page. Grrrrr...
I have checked that the environment variable is indeed passed on to the loolwsd process (by looking at /proc/<pid>/environ)
Hmm, interesting. Shouldn't auto save with that variable set. I think worth setting the log level to trace in loolwsd.xml and see the logs. They should be helpful in figuring out what is going on.
Can you give me some directions about the exact steps for doing it, please? I'm not familiar with loolwsd XML file... Thanks in advance. Regards Jorge
There must be loolwsd.xml somewhere in the docker image. In /etc/loolwsd/loolwsd.xml I think. Open that (and yeah first apt-get update && apt-get install vim because docker image doesn't have a text editor by default ;). Find this[1] line and change the string inside the <logging></logging> tags to trace. (I would also change line 42 flush property to true). Restart the docker image and now docker logs -f <docker_id> would give you trace level logs. When autosave is triggered, it should print something. Analyzing that peice of log should help. [1] https://gerrit.libreoffice.org/gitweb?p=online.git;a=blob;f=loolwsd.xml.in;h=8ec29c82b5614c9746ab45bf85b4ac6ecf8abc5f;hb=HEAD#l33
I did what you said, you can find the log here: https://pastebin.com/Y8s598UR I think I have managed to display only the relevant part, when the Autosave is invoked. Thanks again.
Interestingly, I couldn't reproduce it on my local build. I tried it on a 2 page writer document and autosave happened when I was on page 2. After the autosave finished (indicated by 'Document saved' label on the bottom right toolbar) I was still on page 2 - no jumping. I guess you are doing something different than what I understood from the bug report ? in which case it might help if you expound on it a bit.
This can easily be tested by opening a document and not do anything for about two and a half minutes. Make sure to not even scroll or change window focus. Just place the cursor somewhere in the document and after that time it jumps back to absolute home position.
(In reply to Ruudsch Ma' Hinda from comment #9) > This can easily be tested by opening a document and not do anything for > about two and a half minutes. Make sure to not even scroll or change window > focus. > > Just place the cursor somewhere in the document and after that time it jumps > back to absolute home position. The original report was about autosave, while in your case I see no reference to editing the document at all. I have the same experience as Pranav, the cursor stays in place. It would be interesting to see the logs.
Well, my bug has disappeared. I have reinstalled my LOOL server (created new amazon instance, followed installation of docker CODE image, reconfigured Owncloud to point to the new instance), and now the problem does not happen. Autosave saves the document and keeps the cursos where it is. Probably this error was due to the tests I had to do when installing it for the first time, until I got it working (hostnames, virtual hosts, certificates, etc). Thanks to all, and my apologies for the time I made you waste :-)