Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screen resolution problem. Screen goes black second time connect #6071

Closed
buestad opened this issue Oct 17, 2023 · 4 comments
Closed

Screen resolution problem. Screen goes black second time connect #6071

buestad opened this issue Oct 17, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@buestad
Copy link

buestad commented Oct 17, 2023

Bug Description

I have a host running 1920x1080 and a client running 1680x1050. If I log in to the host and change to full screen and change the resolution in the RustDesk top menu to 1680x1050 it works fine the first time connecting.

The next time I connect the screen is black on the client. I can see the mouse moving on the host and I notice that the resolution on the host has changed, but the resolution on the client RustDesk menu is still 1920x1080. It is also not possible too change the resolution on the RustDesk menu

To fix this I have to uninstall RustDesk on the host and remove all settings in C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\RustDesk

How to Reproduce

See desc

Expected Behavior

See desc

Operating system(s) on local side and remote side

windows 10 -> windows 10

RustDesk Version(s) on local side and remote side

1.2.3 and 1.2.4

Screenshots

First time:
image

Second time:
image

Additional Context

No response

@buestad buestad added the bug Something isn't working label Oct 17, 2023
@rustdesk
Copy link
Owner

@fufesou

@buestad
Copy link
Author

buestad commented Oct 17, 2023

About the deletion of host data. It might just be that the host gets new ID, and the settings is stored on the client?

@rustdesk
Copy link
Owner

Close as fix merged

@vgdh
Copy link

vgdh commented Nov 21, 2023

same issue with the 1.2.3 version, but works well on the nightly build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants