Hi Nick,
The logs seem to imply otherwise but I did try it that way as well, yeah.
I raised the core limit and it does seem to be the issue you've linked. It
looks like this is not an issue in 1.5.3? Maybe I can downgrade until 1.5.5
is available.
On Tue, Jan 2, 2024 at 10:46 PM Nick Couchman
On Tue, Jan 2, 2024 at 3:31 PM Carl Manzi wrote:
> I'm trying to set up guacamole for use in small, ephemeral labs, so I'm
> just using user-mapping.xml.
>
> I've got no problems connecting to Linux servers, but I also have Windows
> servers to connect to, and I'd prefer to use SFTP rather than
I'm trying to set up guacamole for use in small, ephemeral labs, so I'm
just using user-mapping.xml.
I've got no problems connecting to Linux servers, but I also have Windows
servers to connect to, and I'd prefer to use SFTP rather than the shared
drive for upload/download of files.
I've
While the issue may correlate with the release of 1.5.4, keep in mind
that the log message in question is coming from FreeRDP regarding memory
that FreeRDP itself manages, and it is reporting what FreeRDP identifies
as a possible bug *in itself*. See:
We just tried rolling back to 1.5.3 and that fixes our issue.
It seems like 1.5.4 contains a lot of changes related to memory management:
https://github.com/apache/guacamole-server/compare/1.5.3...1.5.4#
On 2024/01/02 13:46:06 Vieri wrote:
>
> From the OP it seems that guacamole 1.5.3 did not
>From the OP it seems that guacamole 1.5.3 did not have this issue, but it is
>yet to be confirmed.
-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail:
We have the exact same issue as Vieri is experiencing. We can add a bit more
information.
The error message:
Major bug, unable to allocate a TLS value for currentThread
is thrown by FreeRDP:
