https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225559

            Bug ID: 225559
           Summary: net/krdc: "xfreerdp" parameter "/network:[...]" not
                    supported anymore in FreeRDP 2.0.0r1?
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
          Assignee: [email protected]
             Flags: maintainer-feedback?([email protected])

After upgrading all packages, it seems that "krdc" is no longer able to spawn
RDP sessions. Activating all debug flags using "kdebugdialog" reveals that
"krdc" executes "xfreerdp" with following options:
-------------------------------------------------------------------------------
-decorations /w:1255 /h:879 /kbd:0x00000407 /u:SECRETUSER
/parent-window:4194338 /bpp:16 /audio-mode:2 /drive:media,/media /network:lan
/cert-ignore +clipboard /port:3389 /v:SECRETSERVER
-------------------------------------------------------------------------------


Executing "xfreerdp" manually with above mentioned options line does not spawn
a RDP session as well and show "xfreerdp" usage output instead. Removing an
option one by one reveals that "xfreerdp" does not like the "/network"
parameter anymore - at least with that options combination.

Patching "krdc" to exclude that:
-------------------------------------------------------------------------------
--- rdpview.cpp.bak     2018-01-30 13:08:36.375470000 +0100
+++ rdpview.cpp 2018-01-30 12:53:57.551629000 +0100
@@ -310,7 +310,7 @@
             break;
         }

-        arguments << "/network:" + performance;
+        // arguments << "/network:" + performance; // nbe: broken in FreeRDP
2.0.0r1

         if (m_hostPreferences->console()) {
             arguments << "/admin";
-------------------------------------------------------------------------------


makes it working again...

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to