TouchUI stop refreshing HDMI Display #281
Comments
|
still have this problem |
|
I have the same issue. |
|
Thanks all for reporting this issue. I am trying to reproduce the issue but sofar I have no success. Could anyone please share your octoprint.log so I could possible identify a suspect. |
|
this is my last log, it happened 2x in those prints. once it happens again I will post a log immediately. Thanks for resurrecting/merging this issue. |
|
hmm, seems like everyone who has this issue have a big log file with a repeating Could you confirm how you login? Do you have autoLoginAs enabled or do you manually login with TouchUI? |
|
I have logged in with touch UI when prompted, then saved PW.
…On Thu, Mar 14, 2019 at 3:40 PM Paul de Vries ***@***.***> wrote:
hmm, seems like everyone who has this issue have a big log file with a
repeating Socket message held back, but backlog full. Throwing message
away.
Could you confirm how you login? Do you have autoLoginAs enabled or do you
manually login with TouchUI?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#281 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQM5l3KJIPw9rYOl_ly9aWQP8-6xwrOUks5vWqXDgaJpZM4aJ3kg>
.
--
-Jared
|
|
Hi @foosel, sorry to intrude you with this issue on this tracker, but I am unable to find a good way to reproduce the following issue and to find out if this is a OctoPrint issue:
Do you want to move this issue over to the OctoPrint issue tracker to have more information? |
So that indicates that the web frontend did not authenticate with the websocket. It should do that immediately after (passive) login. For some reason it is not doing it, which makes me think it might be an issue of some stale version of the web interface in the browser's cache that doesn't yet do the authentication. I've had two people run into this now due to a weird situation in their OctoPrint install, caused by some old files lying around, see this FAQ entry. Maybe this is a similar situation?
This is true. The fix for OctoPrint/OctoPrint#2898 introduced the message backlog in order to make this process less side effect heavy for third party plugins. This backlog usually should not fill up - that it does indicates that for some reason the socket authentication is not happening. Does TouchUI rely on any kind of API key based authentication or does it just use stock auth? |
|
Thanks for your time and the response!
This could very well be the issue, there have been some issues with caching before and a latest Pull Request disables the entire cache.
No, TouchUI does not rely on API keys and use stock auth. The philosophy of TouchUI is to transform the layout and to minimize any side-effects on OctoPrint core functionality. |
|
+all, can you try updating the bootloader to the latest version to see if this issue still persists? |
|
I updated the bootloader... but now I'm getting a login screen and I don't know why. |
|
Good, this is expected. We only need to setup the autoLogin feature on your touchscreen:
|
|
Okay, all is working now. Lets see if the screen dies again in a few days. |
|
I will let you know as well. Just updated the bootloader.
…On Sun, Mar 17, 2019 at 6:13 PM Jason Axelrod ***@***.***> wrote:
Okay, all is working now. Lets see if the screen dies again in a few days.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#281 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQM5l0x9Ql1mEKXcewnq6DLBVTcK4Kecks5vXr3_gaJpZM4aJ3kg>
.
--
-Jared
|
|
It froze again. Worse than before. I used to be able to still navigate the menus, it just never updated the print status. Now I can't navigate the menus at all. The mouse cursor shows up, but nothing changes. |
|
That sounds like a different issue; can you start by sharing the latest octoprint.log? |
|
this is still happening ;/ little to no improvement. |
|
This is my experience. I have 2 printers with 7" and one with 3.5". Both
have the same issue.
…On Wed, May 15, 2019, 11:42 AM Martijn Janssen ***@***.***> wrote:
So it's not really depending on what type or size of screen you connect.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#281?email_source=notifications&email_token=AEBTTFZOVTGTV47LA7GY2PDPVQVNRA5CNFSM4GRHPEQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVPCKZI#issuecomment-492709221>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEBTTFYFNEDKRRHMDJYY2BLPVQVNRANCNFSM4GRHPEQA>
.
|
|
Does this issue also persist on OctoPrint 1.3.11? and whats the octoprint log of that? |
|
My preliminary finding is that in Octoprint 1.3.11 is does refresh and doesn't freeze up anymore. :-) But have to test some more. |
|
Unfortunately it didn't update again during my last print :-( It does respond to touch, like scrolling, but not all commands (like trying to get to the TouchUI submenu to refresh TouchUI) work. |
|
I also can not get to the touch ui settings menu now and that I'm running
on 1.3.11, this is happening on both of my printers.
…On Sat, May 18, 2019, 6:12 AM Martijn Janssen ***@***.***> wrote:
Unfortunately it didn't update again during my last print :-( It does
respond to touch, like scrolling, but not all commands (like trying to get
to the TouchUI submenu to refresh TouchUI) work.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#281?email_source=notifications&email_token=AEBTTF3RWCSJR26PH2KSDSTPV7JBLA5CNFSM4GRHPEQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVWLZAI#issuecomment-493665409>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEBTTF5RETDBOYGXAFRSR6DPV7JBLANCNFSM4GRHPEQA>
.
|
|
The issue about no able to open the TouchUI settings in 1.3.11 is already fixed (#299) and will be released in upcoming version. That OctoPrint stops refreshing is still a concern, any change to share your octoprint log again. |
|
The TouchUI settings issue isn't there all the time. After restarting the Pi or TouchUI it works just fine for a while. It is something in the menu in general, also not able to enter the Connection menu item. |
|
Here is my latest log
…On Sat, May 18, 2019 at 9:56 AM Martijn Janssen ***@***.***> wrote:
The TouchUI settings issue isn't there all the time. After restarting the
Pi or TouchUI it works just fine for a while. It is something in the menu
in general, also not able to enter the Connection menu item.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#281?email_source=notifications&email_token=AEBTTFZZAHHWHD24E72LADLPWADI5A5CNFSM4GRHPEQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVWPDUI#issuecomment-493679057>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEBTTF62OH3NRVQY6Y6BJHLPWADI5ANCNFSM4GRHPEQA>
.
--
-Jared
|
|
I dont see any log :( |
|
now?
…On Mon, May 20, 2019 at 5:07 AM Paul de Vries ***@***.***> wrote:
I dont see any log :(
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#281?email_source=notifications&email_token=AEBTTF3HYJ2WGZY72CQNGGLPWJS6DA5CNFSM4GRHPEQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVYFRIQ#issuecomment-493901986>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEBTTF7ZHPUZLAFT2NCNUE3PWJS6DANCNFSM4GRHPEQA>
.
--
-Jared
|
|
nope, no attachments. |
|
This is still happening to two different octo print instances on two different screens |
|
Me too, me too :( |
|
Still the same issue. Raspberry Pi 4B Octoprint log attached: |
|
Same issue here everything is up-to-date and it just happened a minute ago this isn't the first time it happens by the way |
|
I am having this issue as well. Same error message. This happens to me usually after the session has been running for some length of time (e.g. hours - but it varies). Given that, it seems logical to me that the browser session is timing out and there is a race condition occurring when everything tries to reconnect. Rather than trying to fix the race condition, perhaps it would be easier to try to either remove or postpone the timeout itself? Is there a browser setting for that? Or maybe something could generate ping events simulating user input periodically as a kind of keep-alive? Just a thought... |
|
@BillyBlaze - is there any way we can help? I know this is a old issue that still plagues us. I will gladly donate for your time. Over the past year it has been very tough to use my printer accurately, as I highly depend on the touchui for my printers. |
|
@Iciscron |
|
Just upgraded to Octoprint 1.40 and get this screen on the initial touchui startup. |
I dont know how did overlook this for a long time but in the TouchUI settings there is a "Refresh TouchUI" button which solves my problem completely |
|
ive been doing this for at least 6 months on 2x instances
…On Wed, Mar 4, 2020 at 2:18 PM AfroPsycho ***@***.***> wrote:
Same issue here everything is up-to-date and it just happened a minute ago
this isn't the first time it happens by the way
Maybe little refresh button will do the work whenever it happens I restart
the octoprint but refreshing the touchui would be easier
I dont know how did overlook this for a long time but in the TouchUI
settings there is a "Refresh TouchUI" button which solves my problem
completely
All I need was a little refresh button now when touchUI show outdated
information I can simply refresh it
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#281?email_source=notifications&email_token=AEBTTF7UGHBGRHKDOHQ3WP3RF2SSBA5CNFSM4GRHPEQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENZXHHA#issuecomment-594768796>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEBTTF2G5SDF6DMLAJAWSVLRF2SSBANCNFSM4GRHPEQA>
.
--
-Jared
|
Thanks for your feedback, All your suggestions would be something for OctoPrint because that is responsible for updating the information and keeping the connection alive with its websockets. All this is not managed nor manipulated by TouchUI. We only give it a bit of styling.
I really want to resolve this issue, however since I am unable to reproduce this issue I cant really help you. In addition to that; TouchUI doesn't not do manipulate the communication (WebSocket) connection. It's entirely managed by OctoPrint so if we do find the issue, I am afraid we need to fix that in either OctoPrint or the libary its using. |
I understand and agree in general. However in this case the embedded browser configuration is established by TouchUI (or rather the TouchUI install scripts) not OctoPrint. So if there is a browser setting that is incorrect it has to be changed in TouchUI. Also keep in mind that the run-time behavior of the TouchUI environment is significantly different than in other OctoPrint installs. Most people don't leave a browser window to OctoPrint open for 10+ hours. And even if they did their PC would probably go to sleep and the subsequent wakeup would trigger a refresh - thus avoiding the issue. Net net it seems like a cumulative system behavior that only manifests in TouchUI installs. Whatever the final fix involves it has to be diagnosed first at that level. |
I am not sure what you mean with browser configuration setup by TouchUI the installer; There is no such thing in the installer. However I cannot rule out that there is command line parameter like @Vertigo1206 mentioned that might trigger a race condition, but I think this would be highly unlikely. You can play with those parameters in the chromium.xinit file in the TouchUI-autostart folder.
Al-through I agree that a common user don't do this, I cannot rule out that people are doing this and have disabled sleep. Also you assume that a wakeup would trigger a refresh. WebSockets would be able to resubscribe to the feed without refreshing.
On first sight this seems true, however I still think this problem lies into re-subscription to WebSockets on the client-side. Since refreshing the browser will fix this issue; If there was a system wide problem (e.g. no more space to write) or an expired sessions then you wouldn't be able to do other things. My experience with failing WebSockets is typically a bug in the resubscription or the server-side timing out and not on the client. This is where I would start debugging; but since I am unable to reproduce this, I am therefor unable to find the potential issue. If you want to fix this; I would gladly give assistance. I would start by attaching the remote debugger and wait unilll it stop refreshing data and see what errors are thrown in the console or what the status is of the WebSockets in the network tab. (e.g. does it still receive events from the server-side) |
|
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. |
Hey,
i have found the following issue.
I can start prints at my Macbook, everything is working fine.
I can control the printer with the OctoPrint itself on the HDMI Touchscreen. But i can´t start a new print. The HDMI Display isn´t frozen but it doesn´t refresh the printing item area.
Thank you for your help!
octoprint.log
The text was updated successfully, but these errors were encountered: