When using GPU acceleration, pages appear blank or fail to load

[helfrichmichael]

When testing on an existing PrusaSlicer docker instance with the most recent commit update, I noticed that I cannot login to the Printables site via the prompt that is provided in PrusaSlicer.

If I manually open a Terminal, go into bash, cd into the squashfs-root folder, and then run ./AppRun and attempt to log in, the window will actually show content.

Nothing stands out in the logs, but one possibility is there is an issue with me using the --data-dir request.

The workaround for now to stay logged in to PrusaSlicer + Printables, is manually open follow the steps above and login and then restart the PrusaSlicer instance that is automatically started in the container.

Likely an issue with GTK more specifically.

[helfrichmichael]

1f850c5 aims to address this

[helfrichmichael]

Login works now, but the Prusa Connect page is very odd. This is consistently what I see. Need to check what the logs say and figure out why this is only loading the page partially.

[helfrichmichael]

The error for reference might be fine since I am attempting to use OctoPrint (via the Physical Printer tab and that works). If others who use Prusa Connect can confirm it's functioning, that'd be immensely helpful!

[2024-07-15 19:41:32.956938] [0x000014e03a4e9d80] [error]   Failed communication with Prusa Account: 0x9fbbdc8 action failed (401): {"detail":"Authentication credentials were not provided."}
[2024-07-15 19:41:33.518193] [0x000014e03a4e9d80] [error]   WebKit runtime error: {"action":"ERROR","error":"{}","critical":false}
[2024-07-15 19:41:34.208731] [0x000014e03a4e9d80] [error]   Failed communication with Prusa Account: 0x9fbc0a8 action failed (401): {"message": "Missing or invalid security token", "code": "UNAUTHORIZED"}
[2024-07-15 19:41:35.518596] [0x000014e03a4e9d80] [error]   WebKit runtime error: {"action":"ERROR","error":"{\"status\":401}","critical":false}

[vajonam]

hmm seeing samething, login works, prusaconnect is empty.

[helfrichmichael]

I confirmed with another individual that they don't see anything on PrusaConnect either outside of the docker container, so this might be a PrusaSlicer issue or WAI.

…

On Fri, Jul 26, 2024 at 12:57 PM vajonam ***@***.***> wrote: hmm seeing samething, login works, prusaconnect is empty. — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACFRZYQETR76B2ZNY5FBZSTZOJ5YXAVCNFSM6AAAAABK2QHEYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJTGE2DCNBZG4> . You are receiving this because you were assigned.Message ID: ***@***.***>