ioBroker.admin
ioBroker.admin copied to clipboard
[bug]: Error in GUI! when displaying update instructions for host
No existing issues.
- [X] There is no existing issue for my problem.
Describe the bug
Got the "Error in GUI!" screen, when displaying the instructions, how to update the js-controller.
To Reproduce
- went to the tab "hosts" because of the notification symbol there
- got the display for updating the js-controller to V5.0.16, hit that button
- got the modal displaying the changelog, hit the button for displaying the instructions
- for the fraction of an second there was some page or modal displayed, then the error screen appeared
Expected behavior
Getting instructions displayed, how to update the js-controller.
Screenshots & Logfiles
Adapter version
admin v6.12.0
js-controller version
5.0.12
Node version
v18.17.1
Operating system
Debian GNU/Linux 11 (bullseye)
Additional context
Followed the instructions for displaing things in the browser console, here is the screen shot:
Is this the log when you reproduced the error while the console was already opened? Else please try to do so, else it is very unlikely to reproduce it for us.
Yes, the shown console log was already open, when I began to reproduce the error, as in the description for error reproduction stated.
And the error is reproduceable? Can you show the menu and the button on a screenshot which produces the issue.
The error is reliably reproducable by opening the hosts tab, klicking the update-button in the "available" column and then hitting the button for displaing the instructions (mouse cursor is shown on the button for the next step on both images):
The next screen is already the big screen "Error in the GUI".
Unfortunately I cannot replicate this and the logged error is not very helpful. I am somehow wondering why you dont have the option to update via UI even though you are running on Debian
The problem is still reproducible here, so how can I help? How can I create a more helpful debug output?
I'm not in a rush, to perform the update, so we can take some more days, to find out something.
(I could go through the CLI upgrade steps, according to this forum post, this worked out last time, half a year ago, but then the problem might vanish and hide something deeper...)