Short version: PrusaSlicer's embedded web browser ("physical printer" tab of PrusaSlicer) is unable to load the Octoprint UI after upgrading to Octoprint 1.11.6.
Background: I have PrusaSlicer 2.9.4 configured with a "physical printer" defined for octopi.local using an application API key. My normal workflow is to slice, then click the option to "upload and print", whereupon PrusaSlicer connects to Octoprint, uploads, and starts the print via REST. I can then switch to PrusaSlicer's "Physical Printer" tab, which loads the Octoprint UI using the web browser embedded in PrusaSlicer.
All the above was working correctly with Octoprint 1.11.5. After upgrading to 1.11.6 today, PrusaSlicer's "Physical Printer" tab would not load the Octoprint UI. It connects, but is stuck displaying "Loading OctoPrint's UI, please wait" and never loads the page. Reboots of Pi and PC did not help. A standalone web browser (Edge) from the same PC loads the UI just fine.
Note that PrusaSlicer can still connect, can still upload gcode, and can still start the print via REST as always, so this isn't a network problem or API key problem. But the embedded web browser on PrusaSlicer's "Physical Printer" tab is unable to load the Octoprint 1.11.6 UI.
I rolled back to 1.11.5, and PrusaSlicer is again able to load the Octoprint UI correctly.
System bundle attached. These logs include output for both 1.11.6 and 1.11.5. For example, Octoprint.log initially shows 1.11.6 running; the restart at line 257 is after I reinstalled 1.11.5 and restarted the service. The timestamps there can be used to differentiate 1.11.6 and 1.11.5 in the other logs.
