| Summary: | krdc shows no error messages or feedback, making it impossible to troubleshoot any issues | ||
|---|---|---|---|
| Product: | [Applications] krdc | Reporter: | Dima Ryazanov <dima> |
| Component: | RDP | Assignee: | Urs Wolfer <uwolfer> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | chealer, mihai.dontu |
| Priority: | NOR | ||
| Version: | 4.11.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
krdc's xfreerdp strace
python script that can be used as wrapper over newer versions of xfreerdp |
||
|
Description
Dima Ryazanov
2014-03-10 19:25:08 UTC
I have tested some situation like wrong resolvable DNS and not running RDP service. I always get an error message in KRDC (like "Name or service not known." or "Connection attempt to host failed."). Since I do not have MS RDP test servers, I cannot test things like experienced passwords. @Dima Ryazanov: Can you please run xfreerdp from command line with the same host when you experience such a behavior and post the output here? Also, does xfreerdp quit or continue run and just print a message? If you can provide the information requested in comment #1, please add it. To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment. Sorry, you're right about DNS errors or timeouts. Looks like expired password is the only problem. When I connect using "xfreerdp", I get: SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. However, krdc does not display any messages. I've got the same issue: lately something has been changed in xfreerdp that it no longer accepts the command line given by krdc and just dies with: "error: server hostname was not specified with /v:<server>[:port]" which is wrong, because the argument is there. Anyway, until I attached with strace and saw what was going on, all I could see was krdc's blue window. Nothing else. It _should_ say something when xfreerdp (or any other child) exits with a non-zero code. Created attachment 86880 [details]
krdc's xfreerdp strace
This is the strace log for the xfreerdp child. I have changed by hand the command line (password, domain name etc.).
(In reply to comment #5) > I've got the same issue: lately something has been changed in xfreerdp that > it no longer accepts the command line given by krdc and just dies with: @Mihai DONȚU: What version of xfreerdp do you use? xfreerdp reports '1.1.0-beta1', while portage says '1.1.0_beta1_p20130710'. (In reply to comment #8) > xfreerdp reports '1.1.0-beta1', while portage says '1.1.0_beta1_p20130710'. Please use the stable version (1.0). 1.1 has not been tested and there is work in progress for porting KRDC to the new command line interface (see: https://git.reviewboard.kde.org/r/115059/). Mm. There does not seem to be a stable version in portage. I haven't kept an eye on freerdp, but it would seem the oldest version supported by Gentoo is 1.1-alpha and was added to the package repository sometime in July, last year. Now, krdc has worked perfectly fine until about two weeks ago but I can't figure our what has changed. The only patches to freerdp have been some adding support for the latest ffmpeg. I'll keep investigating. On a side note (or rant), I'm not very satisfied with how freerdp works. It has an exotic command line format reminiscent of the 90's and surprise error messages. Probably some other things, but they don't come to mind. It is, however, better at supporting the win2k12+ rdp protocol than rdesktop. I wonder if it would be possible to use some kind of client library and integrate it the tried and true way: via C/C++. :-) (In reply to comment #10) > I wonder if it would be possible to use some kind of client library and > integrate it the tried and true way: via C/C++. :-) Sure, this would be a way cleaner and better way to do it. But it needs quite some manpower to do it. KRDC always displays a blue screen, as explained in ticket 339490. As for the actual source of your problem, I also lost the ability to connect to a server after upgrading from freerdp 1.0.2 to 1.1.0~git20140921.1.440916e, so freerdp may be involved. Please use freerdp 1.0.x; 1.1 is not yet supported since it has not been released. Created attachment 89739 [details]
python script that can be used as wrapper over newer versions of xfreerdp
Gentoo already moved to '1.2.0_beta1_pre20141115' on ~amd64, so I've concocted the attached python script which I use as a wrapper over xfreerdp. Works like a charm. :-)
I think I have uncovered a bug in krdc: I have this connection for which it insists on generating the command option "udio-mode:" instead of "/audio-mode:". Mm. I thought that was supposed to be a some deprecated command, didn't make the connection until later ... Regarding connection issues with FreeRDP 1.1, see ticket 341284. There exist other reports for the two discussed problem in this report: * FreeRDP 1.1 issues: #341284 * Blue screen issues when connection could not be opened: #339490 *** This bug has been marked as a duplicate of bug 339490 *** |