Closed simmstein closed 4 years ago
Hi, is this error happens for new created documents after update or only to older ones? Is this error for each file or only for some specific?
It happens for creating a new file or opening an existing one. Tested with .docx, .xlsx and .pptx. Not reproduced with Google Chrome 86.0.4240.183 (Build officiel) on debian 10 Not reproduced with Firefox 78.4.0esr on debian 10.
Client side screenshot:
To be clear
Your problem is actual on Google Chrome Version 83.0.4103.116 (Developer Build) on Debian 10 and not actual on Google Chrome 86.0.4240.183 (Build officiel) on debian 10
I understand that 83 version of Chrome is not very old, but I'm not sure we guarantee working of older version of Chrome in latest releases.
Is there any reason you could not update chrome 83 to 86?
Sorry the browser version was not complete : Chromium v83.0.4103.116 (Developer Build) built on Debian 10.4, running on Debian 10.6 (64-bit). This the version of Chromium packaged in Debian 10 (buster) (package: chromium
).
Is there any reason you could not update chrome 83 to 86?
Because this not Google Chrome but Chromium and Chromium is packaged by Debian (so stability + security). Btw, 6.0.1 should not break 6.0.0, right?
Yeah, I've agree with you, something is not right in this
I'll try to reproduce your issue
I've just checked my test server with 6.0.1 installed
And used VirtualBox with Debain with Chromium Version 83.0.4103.116 (Developer Build) built on Debian 10.4, running on Debian 10.6 (64-bit)
to access it
Everything seems fine for me
I think you'r problem is related with font installed on your server
Do you install some additional fonts on your system (on server side)?
Could you attach /usr/share/fonts
of your server?
Some of files are symlinks so I transformed them to real files. The archive is quite large:
Installed your fonts
Everything is fine for me
One thing is strange for me, just noticed now:
You said you got error:
[2020-11-05T09:57:23.714] [ERROR] nodeJS - changesError: docId = 1249301444 Error: Uncaught TypeError: yc.rQb is not a function Script: https://xxxxx/v5.2.8-24//sdkjs/common/libfont/wasm/fonts.js Line: 37:174 userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36 platform: Linux x86_64 isLoadFullApi: false isDocumentLoadComplete: false StackTrace: TypeError: yc.rQb is not a function
at https://xxxxx/v5.2.8-24//sdkjs/common/libfont/wasm/fonts.js:37:174
at https://xxxxx/v5.2.8-24//sdkjs/common/libfont/wasm/fonts.js:37:181
Why there is 5.2.8 version in logs? Did you upgrade from 5.2.8 straight to 6.0.1?
Maybe your chromium got cache from older version?
My history of apt said that onlyoffice-documentserver:amd64
was upgraded from the version 6.0.0-105
to the version 6.0.1-32
.
v5.2.8-24
is a part of the request made by the onlyoffice connector in my nextcloud instance.
This is not right, maybe you're enable Nextcloud Community DocumentServer? It's based on our product but pretty outdated,
maybe you're enable Nextcloud Community DocumentServer
Nope!
I if run supervisorctl stop all
, the result is:
ds:metrics: stopped
ds:spellchecker: stopped
ds:docservice: stopped
ds:converter: stopped
and:
On this problem chromium pc could you see which address you see in Debugger for FrameEditor?
You see version 6.0.1.32
If you see 5.2.8.24 something wrong
If everything is fine with this version - you should find why there is 5.2.8 version in logs, I have no idea, unless those some lefovers from Community DocumentServer
As I said, this is my server.
How can I regenerate fonts.js?
@simmstein on your screen version 6.0.0.105 in header, but you said you upgraded to 6.0.1
Could you open this page on both chromium and on some working browser and compare content of fonts.js, do they have same version in commented header?
How can I regenerate fonts.js?
You can run font generation process via this instruction
After comparison, the fonts.js was in cache and I had to remove the Cache folder to force the reload. Sorry about that, onlyoffice works fine. Thank you very much @ShockwaveNN!
Do you want to request a feature or report a bug?
This is a bug.
What is the current behavior?
Upgrade to 6.0.1: Uncaught TypeError: yc.rQb is not a function
Client side: the document is not loaded Server side: an error is triggered
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Upgrade to 6.0.1.
What is the expected behavior?
Document loaded and editable.
Did this work in previous versions of DocumentServer?
Yes.
DocumentServer version:
onlyoffice-documentserver_6.0.1-32_amd64
Operating System:
Ubuntu 16.04.7 LTS
Browser version:
Version 83.0.4103.116 (Developer Build) built on Debian 10.4, running on Debian 10.6 (64-bit)
Additional logs