| Summary: | Login via rdp:// URL into Windows 8 when username=email address does not work from bookmark or history | ||
|---|---|---|---|
| Product: | [Applications] krdc | Reporter: | Stefan Radermacher <kde> |
| Component: | RDP | Assignee: | Urs Wolfer <uwolfer> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | acelan, ctrlaltca |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Stefan Radermacher
2014-08-29 09:02:48 UTC
Please see this note in the KRDC manual: "You need to enter an URL in percent encoded syntax, i.e. @ as %40, for e.g. username%40ad.domain.example" I have tried that, but it still doesn't work. Windows says "The user name or password is incorrect" and then displays only the part of the user name before the "%40" in the login entry box. Does it only not work when connecting from a bookmark? I.e. does it work when you enter the url directly? The same problem occurs when entering the url directly. This problem is still occuring in the krdc version from the KDE Applications 14.12.1 bundle. I found it parse the username correctly(I didn't create an email account name to test), Could you use "kdebugdialog" to turn on "5012 krdc (RDP backend)" debug message, and then paste the result here? Thanks. krdc(15479)/krdc (RDP backend) RdpView::start: Use FreeRDP 1.1+ compatible arguments krdc(15479)/krdc (RDP backend) RdpView::start: Starting xfreerdp with arguments: "-decorations /w:800 /h:600 /kbd:0x00000409 /u:acelan@acelan.idv.tw /parent-window:153092212 /bpp:24 /audio-mode: 0 /sound:sys:alsa /drive:media,/media /network:lan /rfx /cert-ignore +clipboard /port:3389 /v:192.168.2.118" krdc(15479)/krdc (RDP backend) RdpView::receivedStandardError: "loading channel rdpdr loading channel rdpsnd loading channel cliprdr connected to 192.168.2.118:3389 Thank you for reporting this bug 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 "CONFIRMED" when replying. Thank you! (In reply to Justin Zobel from comment #7) > Thank you for reporting this bug 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 "CONFIRMED" when > replying. Thank you! This bug seems to have been fixed in the meantime. I can no longer reproduce the problem. 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! Closing stale bug already confirmed fixed by user |