[
https://issues.apache.org/jira/browse/GUACAMOLE-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824725#comment-17824725
]
horvathcsabalaszlo commented on GUACAMOLE-1929:
-----------------------------------------------
Managed to install the Git version of guacd on the home server. (Compiled in
place.) Does not work.
This is freakin' strange. Guacd starts, but nothing can connect.
I needed to install libguac-client-rdp0 vnc0... packages of the Bookworm,
because Trixie repos seems to not containing them. But the same install on the
Bookworm works with those libguac-client packages.
Now if i start the guacd, it seems building a connection, but :
root@homeserver:/home/user# GUACD_LOG_LEVEL=debug /usr/local/sbin/guacd -f -b
127.0.0.1 -l 4822 -p /tmp/guacd.pid
guacd[993616]: INFO: Guacamole proxy daemon (guacd) version 1.5.5 started
guacd[993616]: INFO: Listening on host 127.0.0.1, port 4822
guacd[993616]: INFO: Creating new client for protocol "vnc"
guacd[993616]: INFO: Connection ID is "$551e9182-6beb-4584-9073-f9698e28605b"
...and it stops here. Ctrl-c has effect very slowly.
(VNC is only the example, the same happens with RDP too. The remote side
gnome-remote desktop does even not report any connection attempts.)
> Guacd cannot connect to Debian+Gnome-remote-desktop
> ---------------------------------------------------
>
> Key: GUACAMOLE-1929
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1929
> Project: Guacamole
> Issue Type: Bug
> Components: guacd
> Affects Versions: 1.5.4
> Environment: Guacd on Debian Bookworm, connections to Windows and
> Debian Bookworm via RDP is working, but not to Debian Trixie.
> Reporter: horvathcsabalaszlo
> Priority: Minor
> Labels: gnome-remote-desktop, guacd,
>
> Hi,
>
> I have been using Apache Guacamole until now to connect to my home compuers.
> Most of them are running Debian (Bookorm and Trixie), some Windows. The
> Guacamole server is Debian Bookworm.
> So after upgrading my main computer to Trixie, the RDP connection did not
> work. Before VNC was used, which worked well.
> The symptom is that when the Guacamole tries to connect, it cannot
> (disconnects immediately). But only to those, where the OS version is Debian
> Trixie. Connection to Bookworm or Windows is working via RDP.
> The difference between Debian Bookworm and Trixie is the version of
> gnome-remote-desktop , which is 43 on Bookworm, 44 on Trixie, ad the
> libfreerdp2 , which is 2.10 on Bookworm, 2.11 on Trixie.
> I described the issue here, with logs :
> [https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/183]
> The main problem is that the remote machine log says
> ** (gnome-remote-desktop-daemon:3041831): WARNING **: 23:12:32.514: [RDP]
> Client did not advertise support for the Graphics Pipeline, closing connection
> [23:12:32:248]
> [[{{3041831}}|https://github.com/FreeRDP/FreeRDP/commit/30418312521d0391ba30906859012bb2dd9570d2]:3041930]
> [ERROR][com.freerdp.core.transport] - transport_check_fds:
> transport->ReceiveCallback() - -1
> ** Message: 23:12:32.514: Unable to check file descriptor, closing connection
> Don't need to say, i can connect to my main computer with any RDP client,
> from Windows and Linux.
> I have set up a test Guacamole install on a test VM, but it also could not
> connect to my main computer. (1.3.x and 1.5.4 were tested)
> Checked also with xrdp on my main computer, connection also works from
> Remmina/KRDC/Windows RDP, but not from Guacamole.
>
> I have opened cases for Gnome-remote-desktop, and libfreerdp2 developers, and
> they pointed out that graphics pipeline is not a new feature, but guacd is
> not hooking up to it. I suspect that in libfreerdp2 there may be recent
> changes, which are preventing the fallback. Asked libfreerdp2 devs.
>
> Can you please check what can cause such a problem? If any more information
> is needed, let me know :)
> Thanks in advance :)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
