(gelöst) GUI-Fehler beim öffnen des Objek-Datenbaums
-
@bosc4895 sagte in GUI-Fehler beim öffnen des Objek-Datenbaums:
sofort einen GUI-Fehler bekam.
was ist das?
-
@thomas-braun said in GUI-Fehler beim öffnen des Objek-Datenbaums:
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.17.1 v16.17.1 8.15.0 4.0.23 bosc4895 bosc4895 adm dialout cdrom sudo audio video plugdev games users input render net dev gpio i2c spi iobroker /home/bosc4895 Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease Hit:3 https://deb.nodesource.com/node_16.x bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. nodejs: Installed: 16.17.1-deb-1nodesource1 Candidate: 16.17.1-deb-1nodesource1 Version table: *** 16.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf PackageMOD-EDIT: Code in code-tags gesetzt und Post formatiert
-
@bosc4895 aahh.
und was kommt dann wenn du tust was da steht? -
iob repo list iob update -
Haltet mich bitte nicht für bescheuert, Fehler gefunden.
Es liegt nicht am Raspi bzw ioBroker, sondern an Microsoft Edge.
Ich verwende normalerweise nie einen anderen Browser, habe warum auch immer das System unter Chrome aufgerufen und bekomme keine Fehlermeldungen -
@bosc4895 sagte in (gelöst) GUI-Fehler beim öffnen des Objek-Datenbaums:
Ich verwende normalerweise nie einen anderen Browser
Solltest du vielleicht mal ändern.
-
@bosc4895 kannst du die Frage noch beantworten um die Ursache zu finden
@homoran sagte in (gelöst) GUI-Fehler beim öffnen des Objek-Datenbaums:
@bosc4895 aahh.
und was kommt dann wenn du tust was da steht? -
Hier dann die Fehlercodes die angezeigt werden.
DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. at Ks (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:26162) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27463) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27920) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27725) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27920) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27920) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27725) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27725) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27920) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27920) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27725) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:30653) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27725) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27725) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) at Xs (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27725) at Ie (http://192.168.178.5:8081/static/js/3961.a98ff7ab.chunk.js:16:27612) -
Du hast dort noch ein Fehler
stabil .. was ist das !?
Zeige mal das angefragte :
@thomas-braun sagte in (gelöst) GUI-Fehler beim öffnen des Objek-Datenbaums:
@bosc4895iob repo list iob update -
Die beiden Fehler im LOG tauchen sofort auf nachdem der ioBroker startet.
iob repo list
stable : http://download.iobroker.net/sources-dist.json
beta : http://download.iobroker.net/sources-dist-latest.jsonActive repo(s): stable
iob update
Used repository: stable
Adapter "admin" : 6.2.22 , installed 6.2.22
Adapter "alexa2" : 3.19.9 , installed 3.19.9
Adapter "backitup" : 2.4.12 , installed 2.4.12
Adapter "daswetter" : 3.1.3 , installed 3.1.3
Adapter "fullybrowser" : 2.1.2 , installed 2.1.2
Adapter "heatingcontrol": 2.8.7 , installed 2.8.7
Adapter "history" : 2.2.0 , installed 2.2.0
Adapter "hm-rega" : 3.0.40 , installed 3.0.40
Adapter "hm-rpc" : 1.15.12 , installed 1.15.12
Adapter "ical" : 1.13.1 , installed 1.13.1
Adapter "iot" : 1.11.9 , installed 1.11.9
Adapter "jarvis" : 3.0.14 , installed 3.0.14
Adapter "javascript" : 6.0.3 , installed 6.0.3
Controller "js-controller": 4.0.23 , installed 4.0.23
Adapter "linkeddevices": 1.5.5 , installed 1.4.3 [Updatable]
Adapter "nut" : 1.5.1 , installed 1.5.1
Adapter "pollenflug" : 1.0.6 , installed 1.0.6
Adapter "scenes" : 2.3.9 , installed 2.3.9
Adapter "shelly" : 6.0.0 , installed 6.0.0
Adapter "simple-api" : 2.7.0 , installed 2.7.2
Adapter "socketio" : 4.2.0 , installed 4.2.0
Adapter "tankerkoenig" : 2.1.1 , installed 2.1.1
Adapter "telegram" : 1.14.1 , installed 1.14.1
Adapter "text2command" : 2.2.2 , installed 2.2.2
Adapter "tr-064" : 4.2.16 , installed 4.2.16
Adapter "unifi" : 0.5.10 , installed 0.5.10
Adapter "vis" : 1.4.15 , installed 1.4.15
Adapter "vis-icontwo" : 0.89.0 , installed 0.89.0
Adapter "vis-inventwo" : 3.3.1 , installed 3.3.1
Adapter "vis-players" : 0.1.6 , installed 0.1.6
Adapter "vis-plumb" : 1.0.2 , installed 1.0.2
Adapter "vis-timeandweather": 1.2.2, installed 1.2.2
Adapter "web" : 4.3.0 , installed 4.3.0
Adapter "ws" : 1.3.0 , installed 1.3.0 -
@bosc4895 sagte in (gelöst) GUI-Fehler beim öffnen des Objek-Datenbaums:
Die beiden Fehler im LOG tauchen sofort auf nachdem der ioBroker startet.
Naja , der Screenshot hat mich Irretiert bzw. bin selber darauf reingefallen , weil der rest dazu fehlt und dann liest man halt stabil ... aber da fehlt noch was dahinter !
trage mal in repo stable ein
http://iobroker.live/repo/sources-dist.json
