Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

octoprint loaded without touchui #164

Closed
krea002 opened this issue Nov 5, 2017 · 12 comments
Closed

octoprint loaded without touchui #164

krea002 opened this issue Nov 5, 2017 · 12 comments
Labels

Comments

@krea002
Copy link

krea002 commented Nov 5, 2017

hi i am having an issue with touchui not booting on the local touch screen. yesterday everything was working well and after i finished my print i shut don the system when i booted it up to day i get an error. Octoprint loaded without Touchui tap to retry. i have retried several time s with no luck.

I then tried to uninstall the touchui plug in no luck.
i checked for updates only to find that the touchui is up to date.
i uninstalled all plugins to ensure they where not causing an issue and reinstalled touchui only, no luck.

@BillyBlaze
Copy link
Owner

Hi @krea002,

Can you provide me your OctoPrint log?

@BillyBlaze
Copy link
Owner

Any updates? if not I'm closing this issue.

@rcbadiale
Copy link

Hi, I am having the same problem, only tried to update though.

Here goes an Octoprint log:
octoprint (1).log

@BillyBlaze
Copy link
Owner

Can you try this out to see if it works again?

  1. Stop TouchUI:
sudo service touchui stop
  1. Remove default user in Chrome
rm -rf ~/.config/chromium/Default
rm -rf ~/.cache/chromium
  1. Start TouchUI
sudo service touchui start

@rcbadiale
Copy link

Hey! It works now!

Rebooted a few times and is all running fine.

Thank you!

@BillyBlaze
Copy link
Owner

Hi @rcbadiale,

Glad this fixed it, I will release in the upcoming release that TouchUI will always load if you're using TouchU with the autostart script to prevent this from happening again.

@krea002 does this also fix it for you?

@BillyBlaze
Copy link
Owner

I just released a new version of TouchUI, and in this version I will always enable TouchUI if it's getting loaded with the bootloader. This should prevent issues like this occurring.

@maganzi
Copy link

maganzi commented Jan 8, 2019

Hey i have the same issue. But this will don´t work for me.

img_2018

bildschirmfoto 2019-01-08 um 07 45 30

Please help me.

Can you try this out to see if it works again?

  1. Stop TouchUI:
sudo service touchui stop
  1. Remove default user in Chrome
rm -rf ~/.config/chromium/Default
rm -rf ~/.cache/chromium
  1. Start TouchUI
sudo service touchui start

octoprint.log

@BillyBlaze
Copy link
Owner

BillyBlaze commented Jan 8, 2019

Althrough the symptoms look the same; you've a different issue. The new ForceLogin plugin is not working with the out-dated bootloader. Try this steps, if that is not working please create a new issue:

  1. Update your bootloader
  2. Run sudo ~/TouchUI-autostart/helpers/install
  3. Setup autoLoginAs during the installation.

@maganzi
Copy link

maganzi commented Jan 9, 2019

it works! Thank you

@MrArmageddon
Copy link

Was having the same issue, and updating the bootloader, then setting the Auto Login fixed it. Thanks!

@github-actions
Copy link

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.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants