The simple answer is to upgrade to the current version of SimpleHelp which allows for Wayland displays (v5.4). That should resolve your issue, as it has for me in places where Wayland is used. If you’re out of a support contract - it’s a really good reason to renew it. This is a big update if you have Linux clients out there as the other workarounds are super janky and unreliable.
While on the topic of displays not coming up… I had a “similar” issue tonight. I just did a fresh install of 22.04 LTS and ran into one minor issue, which could entirely be my fault. Initially I downloaded the remote support agent, unpacked it, and launched it from the GUI. I went to access via my server and got a grey screen - couldn’t do a thing (and, nothing on the remote host screen indicating anything had changed).
I then tried to launch it using the CLI commands and this time it took a second once I connected to it from my server, but once “optimizing connection” completed, the remote screen got a secondary security popup to allow the remote viewing of the screen. Once that was accepted, I could see the desktop & control. However, when trying to install the remote access service, the user was prompted for their password as another layer of security. That was complete and the remote access agent is now installed. Entirely possible I didn’t wait long enough the first time around and I’m simply an impatient man.
As for the additional layers of security on the host side - I suppose this works a lot like MacOS forcing the user to confirm letting their guard down to certain applications. From the “Remote Assistance” standpoint it’s another hurdle to get the client connected, but from a security standpoint I 100% support these additional measures as the user should be aware of what they’re granting to their device in all transparency.
I think this issue (of Wayland display issues) can safely be closed now