TouchUI loads on Raspberry Pi used as desktop

[xh3dx]

I have a raspberry pi, used as a desktop, running full raspbian in my garage next to my 3d printer. When ever i pull up the octoprint site for my printer, it loads TouchUI automatically, which i don't want it to. When i go to the touch UI settings, there is no option to "Toggle TouchUI." Is there a fix for this?

I have tried by disabling both "Start TouchUI Automatically" options in the settings but this doesn't help.

[spiff72]

Chiming in with the same issue. Running on a 1920x1080 monitor, chromium as the browser, on a Raspi 4 with 4GB RAM. Can't for the life of me get rid of the touch UI interface on this machine. Other machines it works fine.

[spiff72]

One additional comment - while I don't have a "Toggle TouchUI" option, I do have a Toggle Touchscreen Mode option (which doesn't help). I also turned off all of the options that should start it automatically (based on resolution and touchscreen being present).

[spiff72]

And one LAST clarification! The Pi that I am running this on is NOT the pi that is running my Octoprint server. Totally separate machine, but on the same network, of course...

Thanks!

[stale]

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.

[spiff72]

Bumping this, as it is still an issue for me...

[xh3dx]

Are we to expect no response from the developer? I still have this issue. Raspberry Pi 4 (4GB)

[BillyBlaze]

Sorry for the long delay, the problem is caused by this commit and the message of this fix is:

You could disable TouchUI while using the bootloader, therefor the bootloader would fail to start because 'OctoPrint loaded without TouchUI'. Therefor always load TouchUI based on the user-agent string we custom set in chromium.xinit

Anyhow I will fix this in the next release.

[github-actions]

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.