mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #217] RDP connection does not save different port #2109
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#2109
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nikos1988 on GitHub (Mar 14, 2022).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/217
Originally assigned to: @VShawn on GitHub.
Describe the bug
RDP connection does not save different port
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Save RDP connection port correctly.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Encrypted PRemoteM.db. Not sure if this has to do with the problem
@VShawn commented on GitHub (Mar 14, 2022):
Sorry, I can't reproduce it on Win10. I closed it and reopened, the port still shows
123IMO OS version would not bring this kind of bug.
@nikos1988 commented on GitHub (Mar 14, 2022):
Did you completely (via Trayicon) close PRemoteM and is your DB encrypted? I also checked the JsonConfigString with DBBrowser for SQLite and the port value does change. Maybe it does not load the port value correctly with encrypted DB?
@VShawn commented on GitHub (Mar 14, 2022):
Yes
No
I‘ll try again with encryption.
@VShawn commented on GitHub (Mar 14, 2022):
oh yes you're right, it reproduce with encryption.