On Fri, Oct 21, 2022 at 3:30 PM Dylan Francis <[email protected]>
wrote:

> The logs generated from my most recent connection attempt are below.
> It is now creating the user folder within /etc/guacamole/share after I
> updated the web ui to /etc/guacamole/share/${GUAC_USERNAME}
> There is no guacd user on the machine, if that makes a difference.
> I have included the Device Redirection section below as well, if that is
> beneficial.
>
> Oct 21 19:23:21 n114-251-182 guacd[213659]: Creating new client for
> protocol "rdp"
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[213659]:
> INFO:#011Creating new client for protocol "rdp"
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[213659]:
> INFO:#011Connection ID is "$d3aef13c-823d-4130-a36f-f73deaf10e4f"
> Oct 21 19:23:21 n114-251-182 guacd[213659]: Connection ID is
> "$d3aef13c-823d-4130-a36f-f73deaf10e4f"
> Oct 21 19:23:21 n114-251-182 guacd[1798243]: FreeRDP initialization may
> fail: The current user's home directory ("/usr/sbin") is not writable, but
> FreeRDP generally requires a writable home directory for storage of
> configuration files and certificates.
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[1798243]:
> WARNING:#011FreeRDP initialization may fail: The current user's home
> directory ("/usr/sbin") is not writable, but FreeRDP generally requires a
> writable home directory for storage of configuration files and certificates.
> Oct 21 19:23:21 n114-251-182 guacd[1798243]: Security mode: Negotiate (ANY)
> Oct 21 19:23:21 n114-251-182 guacd[1798243]: Resize method: none
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[1798243]:
> INFO:#011Security mode: Negotiate (ANY)
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[1798243]:
> INFO:#011Resize method: none
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[1798243]: INFO:#011No
> clipboard line-ending normalization specified. Defaulting to preserving the
> format of all line endings.
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[1798243]: INFO:#011User
> "@b14b5698-04ab-4338-9c54-65a92699028d" joined connection
> "$d3aef13c-823d-4130-a36f-f73deaf10e4f" (1 users now present)
> Oct 21 19:23:21 n114-251-182 guacd[1798243]: No clipboard line-ending
> normalization specified. Defaulting to preserving the format of all line
> endings.
> Oct 21 19:23:21 n114-251-182 guacd[1798243]: User
> "@b14b5698-04ab-4338-9c54-65a92699028d" joined connection
> "$d3aef13c-823d-4130-a36f-f73deaf10e4f" (1 users now present)
> Oct 21 19:23:21 n114-251-182 guacd[1798243]: Loading keymap "base"
> Oct 21 19:23:21 n114-251-182 guacd[1798243]: Loading keymap "en-us-qwerty"
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[1798243]:
> INFO:#011Loading keymap "base"
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[1798243]:
> INFO:#011Loading keymap "en-us-qwerty"
> Oct 21 19:23:21 n114-251-182 guacd[1798243]: Connected to RDPDR 1.13 as
> client 0x0003
> Oct 21 19:23:21 n114-251-182 guacd[213659]: guacd[1798243]:
> INFO:#011Connected to RDPDR 1.13 as client 0x0003
> Oct 21 19:23:21 n114-251-182 guacd[213659]: free(): double free detected
> in tcache 2
> Oct 21 19:23:21 n114-251-182 coredump_handler: coredump argv[3] is
> !usr!local!sbin!guacd
> Oct 21 19:23:22 n114-251-182 guacd[213659]: Connection
> "$d3aef13c-823d-4130-a36f-f73deaf10e4f" removed.
> Oct 21 19:23:22 n114-251-182 guacd[213659]: guacd[213659]:
> INFO:#011Connection "$d3aef13c-823d-4130-a36f-f73deaf10e4f" removed.
>
>
Two things stand out to me, here:
* First, you might want to fix the issue with the writable home directory
for the user running guacd. I would recommend just creating a guacd account
with a normal home directory and switching the service over to run under
that account so that FreeRDP can write out the server fingerprints.
* This is likely causing the issues you're seeing:

Oct 21 19:23:21 n114-251-182 guacd[213659]: free(): double free detected in
tcache 2
Oct 21 19:23:21 n114-251-182 coredump_handler: coredump argv[3] is
!usr!local!sbin!guacd

If you could locate this core dump and provide the output, that would help
in tracking it down. It's possible this has already been resolved in the
git version of the code, but if would be good to verify the exact location
of that and make sure that it has actually been resolved.

-Nick

Reply via email to