starred/1Remote

Fork 0

mirror of https://github.com/1Remote/1Remote.git synced 2026-04-25 13:36:03 +03:00

[GH-ISSUE #881] RDP client window contents may be replaced by another RDP connection #3632

New issue

Closed

opened 2026-03-13 12:24:33 +03:00 by kerem · 5 comments

kerem commented

2026-03-13 12:24:33 +03:00

Owner

Originally created by @itagagaki on GitHub (Mar 3, 2025).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/881

Originally assigned to: @VShawn on GitHub.

I encountered a very strange behavior and will file the events as far as I can remember.

Connect to two RDP hosts A and B
Disable RDP functionality on A
Initiate a Windows reset on B (not sure if this is relevant)
A and B ware swapped. That is, B's screen appears in A's client window and an error screen (with a Reconnect button) appears in B's client window.
After clicking the Reconnect button on B's client window, the screens ware swapped again.
After clicking the Reconnect button that has moved to A's window, the screen ware swapped again.

I'm not sure if this is reproducible. It would probably be a very difficult investigation.

Originally created by @itagagaki on GitHub (Mar 3, 2025). Original GitHub issue: https://github.com/1Remote/1Remote/issues/881 Originally assigned to: @VShawn on GitHub. I encountered a very strange behavior and will file the events as far as I can remember. 1. Connect to two RDP hosts A and B 2. Disable RDP functionality on A 3. Initiate a Windows reset on B (not sure if this is relevant) 4. A and B ware swapped. That is, B's screen appears in A's client window and an error screen (with a Reconnect button) appears in B's client window. 5. After clicking the Reconnect button on B's client window, the screens ware swapped again. 6. After clicking the Reconnect button that has moved to A's window, the screen ware swapped again. I'm not sure if this is reproducible. It would probably be a very difficult investigation.

kerem

2026-03-13 12:24:33 +03:00

closed this issue
added the
bug

meta-unknown-error
labels

kerem commented

2026-03-13 12:24:49 +03:00

Author

Owner

@VShawn commented on GitHub (Mar 4, 2025):

sounds mysterious.

When does the window swap between A and B occur? Does it happen immediately after clicking reset in B?

@VShawn commented on GitHub (Mar 4, 2025): sounds mysterious. When does the window swap between A and B occur? Does it happen immediately after clicking reset in B?

kerem commented

2026-03-13 12:24:54 +03:00

Author

Owner

@itagagaki commented on GitHub (Mar 4, 2025):

I found myself in that situation. My memory is fuzzy as to whether it was triggered by an action of B at that time, or whether the disconnection of A was before or after.

@itagagaki commented on GitHub (Mar 4, 2025): I found myself in that situation. My memory is fuzzy as to whether it was triggered by an action of B at that time, or whether the disconnection of A was before or after.

kerem commented

2026-03-13 12:24:59 +03:00

Author

Owner

@itagagaki commented on GitHub (Mar 4, 2025):

Ah, I see what happened.

Client A has primary host1 and alternate host2.
Client B has primary host2.

A connects to host1.
B connects to host2.

host1 is disconnected.
The Reconnect button appears on A.
Clicking the Reconnect button on A causes A to connect to alternate host2.
This disconnects B from host2, and the Reconnect button appears on B.
Clicking the Reconnect button on B causes B to reconnect to host2.
This disconnects A from host2, and the Reconnect button reappears on A.
When the reconnect button on A is clicked, the main host1 remains disconnected, so it connects again to the alternate host2.

The above is repeated. It was just a natural thing that happened. So I close this issue.

However, when I try the above, it still crashes (application becomes unresponsive). This is still be a difficult investigation because the reproducibility is random.

@itagagaki commented on GitHub (Mar 4, 2025): Ah, I see what happened. Client A has primary host1 and alternate host2. Client B has primary host2. A connects to host1. B connects to host2. host1 is disconnected. The Reconnect button appears on A. Clicking the Reconnect button on A causes A to connect to alternate host2. This disconnects B from host2, and the Reconnect button appears on B. Clicking the Reconnect button on B causes B to reconnect to host2. This disconnects A from host2, and the Reconnect button reappears on A. When the reconnect button on A is clicked, the main host1 remains disconnected, so it connects again to the alternate host2. The above is repeated. It was just a natural thing that happened. So I close this issue. However, when I try the above, it still crashes (application becomes unresponsive). This is still be a difficult investigation because the reproducibility is random.

kerem commented

2026-03-13 12:25:04 +03:00

Author

Owner

@VShawn commented on GitHub (Mar 5, 2025):

just let you know I finished #869 last night, a address detecting window will be shown to let user aware that Clicking the Reconnect button on B causes B to reconnect to host2.

@VShawn commented on GitHub (Mar 5, 2025): just let you know I finished #869 last night, a address detecting window will be shown to let user aware that `Clicking the Reconnect button on B causes B to reconnect to host2.`

kerem commented

2026-03-13 12:25:09 +03:00

Author

Owner

@itagagaki commented on GitHub (Mar 5, 2025):

That sounds good.

@itagagaki commented on GitHub (Mar 5, 2025): That sounds good.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/1Remote#3632

No description provided.

Rows
Columns