Bug 277272 - url misinterpreted
Summary: url misinterpreted
Status: RESOLVED WORKSFORME
Alias: None
Product: krdc
Classification: Applications
Component: RDP (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-07 08:57 UTC by Dj YB
Modified: 2023-02-04 04:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dj YB 2011-07-07 08:57:48 UTC
Version:           unspecified (using KDE 4.6.3) 
OS:                Linux

trying the following in bash:
krdc --fullscreen "rdp://domain.name\username@ip_address"

fail.
the \ sign between the domain and the user name is interpreted as %5C

Thanks.

Reproducible: Didn't try

Steps to Reproduce:
in a shell type:
krdc --fullscreen "rdp://domain.name\username@ip_address"

Actual Results:  
nothing, the \ sign is misinterpreted as %5C

Expected Results:  
connection

OS: Linux (i686) release 2.6.38.8-32.fc15.i686.PAE
Compiler: gcc
Comment 1 Urs Wolfer 2012-01-04 20:37:58 UTC
It looks like KUrl encodes the URL here. Does it not work this way? What is entered on the remote machine login? %5c only?

In debug output it looks like KRDC does the right thing:
krdc(3061)/krdc (RDP backend) RdpView::start: Is LDAP login: true "domain.name\username"
Comment 2 Dj YB 2012-01-04 21:21:38 UTC
the %5c is not the problem apparently.
because using the krdc gui convert the \ also to %5c and there is no problem there.
the problem is probably with the cli itself, don't know what it is you just have to try and connect from both cli and gui and check if it is working for you. I fail to connect using the cli.

Thanks,
YB.
Comment 3 Andrew Crouthamel 2018-11-06 15:11:24 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-18 03:26:24 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-20 07:49:58 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2023-01-04 05:25:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Dj YB 2023-01-05 11:42:40 UTC
(In reply to Justin Zobel from comment #5)
> Thank you for reporting this issue in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the issue with a recent software version?
> 
> If you can reproduce the issue, please change the status to "REPORTED" when
> replying. Thank you!

Hello, Justin

I am not using Linux anymore, so I have no way to test the bug.

Best regards,
YB
Comment 8 Bug Janitor Service 2023-01-20 05:07:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2023-02-04 04:58:54 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!