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

Crash mRemoteNG work with two monitors #1745

Closed
dmalyshok opened this issue May 6, 2020 · 4 comments
Closed

Crash mRemoteNG work with two monitors #1745

dmalyshok opened this issue May 6, 2020 · 4 comments

Comments

@dmalyshok
Copy link

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

  1. Work with mremote on extended monitor
  2. Disconect extended monitor
  3. Mremote -> do reconect
  4. Crash

Context

Your Environment

  • Version used:
  • Operating System and version (e.g. Windows 10 1709 x64):
@Benchwork
Copy link

just for clarification, the extended monitor is on your computer and not the remote computer correct? also can you tell me how the monitor was connected? eg. hdmi/displayport/usb-c/RGB

thank you

@dmalyshok
Copy link
Author

dmalyshok commented May 7, 2020

RGB
yes work with two local monitors

https://imgur.com/a/tRd0D8z
125 scale and the same resolution 1920x1080

thank you for replay

@Benchwork
Copy link

does it actually crash or just disappear off the screen and become unusable? if I am using mRemoteNG on my 2nd screen and I disconnect it, some times it seems like mRemoteNG Stays in the same place instead of getting adjusted to to the new screen layout.
image
when this happens, I then have to shift+right-click on mRemoteNG and click on move,
image
(your mouse will change to a 4-way arrow)
image
and then use arrow keys to move it into the screen. in my example I would use the left arrow key.

this is not a fix its a workaround for my issue, not sure if that helps.

@farosch
Copy link
Member

farosch commented May 24, 2020

Most likely not related to mRemoteNG but your graphics driver / dockdriver / windows version used.
We had issues like these before: #1592 #1343
Unfortunalety you failed in including any kind of relevant information, that's why I will close this issue.
If you decide to fill in a proper issue or update this one with the needed information we will be glad to help you ;)

@farosch farosch closed this as completed May 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants