Closed tibmeister closed 3 years ago
Turns out it's the UI Customizer plugin that breaks TouchUI. Very disappointed, I've used TouchUI for some time now, > 2 years, but it seems that I cannot use it anymore unless this issue get's fixed.
I'm not so sure it's just that plugin--I'm getting similar behavior. No errors logged, and TouchUI seems to get through the connecting to TouchUI, loading octoprint, and loading TouchUI steps, but then crashes to a white screen which eventually returns to the TouchUI "error, tap to retry" screen. Attached are my logs from my last boot. octoprint.log
same problem here, with uicustomizer on, touchui constantly crashes with a white screen 1-2s after loading... when turning uicustomizer off, touchui works as expected!
is there any known fix to that?
another problem, sorry for posting it here, but the relevant thread/issue has been locked: i'm also monitoring that chromium puts heavy stress on my pi, i think i'm almost unable now to use it without active cooling. can it be that this is all linked together, and maybe an other version of chromium would make more sense in terms of stability and/or CPU usage? please see at issue #174 for details about the CPU-usage, it first occurred a few years back and never got sorted... as it seems there are quite a lot users affected.
same problem here, with uicustomizer on, touchui constantly crashes with a white screen 1-2s after loading... when turning uicustomizer off, touchui works as expected!
Same for me! :-(
It looks like there is a solution for this problem:
This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
TouchUI loads, the interface pops up with some boxes for the icons, then goes to white screen and starts loading TouchUI all over again. No errors or anything in the octoprint.log, so not sure what's going on. Fresh install (Octoprint 0.18.0) on rPi3B+