If the document is not saved after modification and the browser is refreshed, the document will not be able to be loaded

Chenkai · May 18, 2023, 6:44am

Hi ,

If the document is not save after modification and the browser is refreshed, this document will never be able to be opened again.Why is this? Is there anything that needs to be done?

Best Regards.

Tex · May 18, 2023, 8:20am

Hi @Chenkai,

Thanks for posting.

If the document is not save after modification and the browser is refreshed, this document will never be able to be opened again.

So, you’re able to open/create a new document fine… but trying to reopen an old one causes COOL to get stuck on that screen?

Could you please give more info of your setup?

Q1] Can you give me your:

Help > About info?

Q2] How are you running Collabora? (OS? Browser version?)

Q3] Are there any errors appearing in the commandline when you try to open the old document? (File permission problems?)

Chenkai · May 18, 2023, 10:39am

Hi @Tex

repro steps:
1.Open a. docx document
2.Enter or modify some content, but close or refresh the browser without clicking save
3.If open this document again, Collaborateonline will not be able to display the document and will prompt error. The image above shows

Q1] Can you give me your:

Help > About info?

image1911×744 87 KB

Q2] How are you running Collabora? (OS? Browser version?)
OS： Linux version 5.15.0-58-generic (buildd@lcy02-amd64-101) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023

Browser version：Microsoft Edge 113.0.1774.42

Q3] Are there any errors appearing in the commandline when you try to open the old document? (File permission problems?)

May 18 18:56:00 hkco coolwsd[463892]: kit-463892-439325 2023-05-18 18:56:00.850766 +0800 [ kitbroker_0cb ] TRC Purging dead sessions, have 1 active sessions.| kit/Kit.cpp:807
May 18 18:56:00 hkco coolwsd[463892]: kit-463892-439325 2023-05-18 18:56:00.850743 +0800 [ kitbroker_0cb ] TRC ToMaster-603: isDocLoaded state after loadDocument: false| kit/ChildSession.cpp:249
May 18 18:56:00 hkco coolwsd[463892]: kit-463892-439325 2023-05-18 18:56:00.850722 +0800 [ kitbroker_0cb ] ERR ToMaster-603: Failed to get LoKitDocument instance for [file:///tmp/user/docs/H5ZEK>
May 18 18:56:00 hkco coolwsd[439325]: frk-439325-439325 2023-05-18 18:56:00.850689 +0800 [ forkit ] TRC ppoll start, timeoutMicroS: 1000000 size 1| net/Socket.cpp:339
May 18 18:56:00 hkco coolwsd[439325]: frk-439325-439325 2023-05-18 18:56:00.850669 +0800 [ forkit ] TRC #13: setupPollFds getPollEvents: 0x1| net/Socket.hpp:876
May 18 18:56:00 hkco coolwsd[439325]: frk-439325-439325 2023-05-18 18:56:00.850584 +0800 [ forkit ] TRC cleanupChildren reaped 0 children to have 2 left: 463892 464703 | kit/ForKit.cpp:327
May 18 18:56:00 hkco coolwsd[439325]: frk-439325-439325 2023-05-18 18:56:00.850565 +0800 [ forkit ] TRC cleanupChildren with 2 children| kit/ForKit.cpp:292
May 18 18:56:00 hkco coolwsd[439325]: frk-439325-439325 2023-05-18 18:56:00.850549 +0800 [ forkit ] TRC forkLibreOfficeKit limit: 0| kit/ForKit.cpp:444
May 18 18:56:00 hkco coolwsd[439325]: frk-439325-439325 2023-05-18 18:56:00.850527 +0800 [ forkit ] TRC #13: Revents: 0x0| net/Socket.hpp:1316
May 18 18:56:00 hkco coolwsd[439325]: frk-439325-439325 2023-05-18 18:56:00.850509 +0800 [ forkit ] TRC #13: Starting handling poll events of forkit at index 0 (of 1): 0x0| net/Socket.cpp:435
May 18 18:56:00 hkco coolwsd[439325]: frk-439325-439325 2023-05-18 18:56:00.850474 +0800 [ forkit ] TRC Poll completed with 1 live polls max (1000000us)| net/Socket.cpp:357
May 18 18:56:00 hkco coolwsd[463892]: kit-463892-439325 2023-05-18 18:56:00.850434 +0800 [ kitbroker_0cb ] FTL Failed to load the document. Setting TerminationFlag| kit/Kit.cpp:1484
May 18 18:56:00 hkco coolwsd[463892]: Failed to load the document. Setting TerminationFlag
May 18 18:56:00 hkco coolwsd[463892]: kit-463892-439325 2023-05-18 18:56:00.850394 +0800 [ kitbroker_0cb ] TRC #16: Wrote 50 bytes of 50 buffered data| net/Socket.hpp:1457
May 18 18:56:00 hkco coolwsd[439295]: wsd-439295-464702 2023-05-18 18:56:00.850371 +0800 [ docbroker_0cb ] TRC ppoll start, timeoutMicroS: 5000000 size 2| net/Socket.cpp:339
May 18 18:56:00 hkco coolwsd[439295]: wsd-439295-464702 2023-05-18 18:56:00.850358 +0800 [ docbroker_0cb ] TRC #20: setupPollFds getPollEvents: 0x1| net/Socket.hpp:876
May 18 18:56:00 hkco coolwsd[439295]: wsd-439295-464702 2023-05-18 18:56:00.850343 +0800 [ docbroker_0cb ] TRC #35: setupPollFds getPollEvents: 0x1| net/Socket.hpp:876
May 18 18:56:00 hkco coolwsd[439295]: wsd-439295-464702 2023-05-18 18:56:00.850328 +0800 [ docbroker_0cb ] TRC Poll: current activity:

Tex · May 18, 2023, 12:58pm

Thanks. For searchability, let me reproduce your info below:

Error

Failed to load the document. Please ensure the file type is supported and not corrupted, and try again.

About

COOLWSD version:
22.05.12.2 (git hash: c0a4f61)
LOKit version:
built on a great technology base
Collabora Office 22.05.11.1 (git hash: 20d7735)
Served by: Ubuntu 22.04.1 LTS 9aea8bba

Hmmm, I also notice you’re on:

25.05.11

Mind updating to:

25.05.14

Maybe that might have fixed your issue.

Browser version：Microsoft Edge 113.0.1774.42

Edge? On Ubuntu? Hmmm, do other browsers cause this same thing too?

Failed to get LoKitDocument instance for [file:///tmp/user/docs/H5ZEK>

Hmmm… Doing a search for this error + file:///tmp/user/docs leads to some older Nextcloud/bugs (that were already fixed), like:

Hmmm… can you explain your current setup a little more?

So, you’re

running COOL on Ubuntu
Accessing COOL from a (different computer via Edge?)

Are you running COOL in a container or proxy or something else like that?

Chenkai · May 19, 2023, 1:19am

Hi @Tex

Are you running COOL in a container or proxy or something else like that?

Yes,running COOL on Ubuntu.
Accessing COOL from a (different computer via Edge?)
Yes,Google browser access is the same issue.

Our QA is using version 25.05.11
Our product uses 22.05.14.3, we tested, without this issue .Thank you for your reply.

Thanks

Tex · June 1, 2023, 3:04am

Our QA is using version 25.05.11
Our product uses 22.05.14.3, we tested, without this issue .Thank you for your reply.

So, if I’m reading this correctly, the issue was fixed in 22.05.14?