| Summary: | unable to connect using xfreerdp (X224_TPDU_CONNECTION_CONFIRM error) | ||
|---|---|---|---|
| Product: | [Plasma] KRdp | Reporter: | Guido <guido.iodice> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | ahiemstra, akselmo, helaslo, john.kizer, michiel, nate |
| Priority: | NOR | ||
| Version: | 6.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Server-side log from KRDC attempting to connect to KRDP on Fedora 40
Server-side logs for KRDP with an initially successful connection attempt from the Remmina Flatpak, then the connection freezing (client screen frozen, no input accepted) after a few minutes |
||
|
Description
Guido
2024-06-20 17:51:20 UTC
I'm also seeing the same thing, trying to connect from one Fedora 40 machine to another Fedora 40 installation, both on Plasma 6.1. The System Settings option didn't appear until I manually installed krdp, so I'm not sure if there might be some other package that needs installed still? Seems xfreerdp as a client does not work. Can you try another client, such as Remmina installed from Flatpak, just to see if it's client or server specific thing? If what I'm observing is with KRDC (mentioned by the original reporter as well) and Remmina as clients, should I create a new bug report since this one has been edited to be specific to xfreerdp? (In reply to Akseli Lahtinen from comment #2) > Seems xfreerdp as a client does not work. Can you try another client, such > as Remmina installed from Flatpak, just to see if it's client or server > specific thing? Krdp uses freerdp2, krdc also uses freerdp2, and xfreerdp is part of freerdp2. Remind uses freerdp3 So your request sounds a bit strange for me. But I can try in next few days. I tried remmina, negotiation error From the terminal: [20:33:37:220] [69816:000110fc] [ERROR][com.freerdp.core] - [tpdu_read_connection_confirm]: Error: expected X224_TPDU_CONNECTION_CONFIRM [20:33:37:220] [69816:000110fc] [ERROR][com.freerdp.core.nego] - [nego_connect]: Protocol Security Negotiation Failure [20:33:37:220] [69816:000110fc] [ERROR][com.freerdp.core] - [rdp_client_connect]: ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C] [20:33:37:220] [69816:000110fc] [ERROR][com.freerdp.core.connection] - [rdp_client_connect]: Error: protocol security negotiation or connection failure 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! Sorry if this is incorrect, I'm trying to set this to "Confirmed" so it's not auto-closed, since at least two folks have reported it? (In reply to John Kizer from comment #7) > Sorry if this is incorrect, I'm trying to set this to "Confirmed" so it's > not auto-closed, since at least two folks have reported it? Also I see other users report the same problem on Reddit Ah sorry I had forgotten to turn this back to reported. We will look more into this when we can. What distribution does this happen on? Also, does something change if you add `/sec:nla` to the xfreerdp command line options? (In reply to Arjen Hiemstra from comment #10) > What distribution does this happen on? > > Also, does something change if you add `/sec:nla` to the xfreerdp command > line options? I use Manjaro unstable branch (equivalent to Arch) With that option nothing change. So this is going to need more logging output, because it seems to fail in the middle of security negotiation which works fine for me and others. The server side logs should be in the journal, for the client use `WLOG_LEVEL=debug xfreerdp` . Created attachment 171592 [details]
Server-side log from KRDC attempting to connect to KRDP on Fedora 40
Hope this is helpful, this is the server-side log from my attempt to use KRDC on a Fedora 40 device to connect to KRDP on another Fedora 40 device - mine appears to be a graphics issue though, and both are Nvidia devices using the RPMFusion-provided Nvidia drivers (555 series), so this may be a different issue? Should I log separately?
Created attachment 171594 [details]
Server-side logs for KRDP with an initially successful connection attempt from the Remmina Flatpak, then the connection freezing (client screen frozen, no input accepted) after a few minutes
|