"waiting for image" issues

[rustdesk]

Unresolved

• Connected waiting for image on one specific device #5608
• "waiting for image" when locked screen on windows server 2012 (installed) #2175
• Waiting for screen transmission！ #6419

[Aqua1ung]

Just FYI, I am getting this one on Android with the latest Rustdesk nightly as of Sept. 24, 2023. Client on Clear Linux, server on Android.

[mclovin-2k]

I'm facing the same issue when I try to connected to a locked Android phone with Rustdesk v1.2.3.
I think this issue was happening since v1.2.1, but you can workaround this by clicking cancel button on the "waiting for image" dialog.
Since v1.2.2, clicking cancel button will disconnect the device, which make Rustdesk completely unusable on Android.

[Aqua1ung]

The current workaround is to click the Home button (which will make the "Successful/Cancel" window disappear), and then click on the screen. (You may need to enable "Mobile Actions" to see the "Home" button.)

[Aqua1ung]

Apparently this workaround ^ no longer works with the latest nightly (Oct. 30).

[Aqua1ung]

The workaround started working again with the latest 2 releases.

[rustdesk]

https://www.reddit.com/r/rustdesk/comments/18ig4ap/succesful_connected_waiting_for_image/

This was a rough one to fix.

The issue is evidently the Windows Lock Screen on login.

The fix was to install the program on both ends. Using the standalone at either end would not suffice.

Once installed, change the security settings to allow for keyboard and mouse.

This enables the ability to send a CTRL-ALT-DELETE, which magically then shows a picture of the lock screen on the rmote computer and enables logging in and finally remote operation.

[mclovin-2k]

https://www.reddit.com/r/rustdesk/comments/18ig4ap/succesful_connected_waiting_for_image/

This was a rough one to fix.
The issue is evidently the Windows Lock Screen on login.
The fix was to install the program on both ends. Using the standalone at either end would not suffice.
Once installed, change the security settings to allow for keyboard and mouse.
This enables the ability to send a CTRL-ALT-DELETE, which magically then shows a picture of the lock screen on the rmote computer and enables logging in and finally remote operation.

But Android didn't have this issue until v1.2.1 or v1.2.0.
Could you maybe fix this on Android first, please?
I think quickest way to do this is revert related code to older version or just remove this dialog on Android client.

[asdf4w3t5]

after arch linux update now rustdesk is getting this error. But I guess many devices have had it for a while

I can see their mouse moving but can't see the screen lol

FWIW I installed the flatpak and it all works now. I'll just delete the other version.