Hi,

sadly - the same problem on Debian 13 as docker host.

Dec 15 13:35:25 kernel: guacd[3479749]: segfault at 7f5b069d6bf8 ip 00007f535d9cd4c8 sp 00007f53069d32e8 error 4 in *ld-musl-x86_64.so.1*[574c8,7f535d98a000+4c000] likely on CPU 7 (core 7, socket 0)
Dec 15 13:35:25 kernel: Code: e3 18 ...  0a b8 16

After "some" Connections, didn't really count them...

At some point - no new connections can be started.

CPU/RAM (25%) are fine.

After i closed some of the (rdp) connections (all on different servers) the system can connect to the "outstanding" servers.

Is it a problem to use a new Alpine image?

https://github.com/abesnier/docker-guacamole/blob/master/Dockerfile.alpine.base

also works with a newer.

Tobias

Am 15.12.2025 um 13:31 schrieb Nick Couchman:
On Mon, Dec 15, 2025 at 6:23 AM Tobias Feller | OPC<[email protected]> wrote:
Hi Subba,

i think it is still there. In my opinion it is a combination of

docker image (outdated) alpine
and maybe only in combination with the docker host (debian 12)

I have now a new host (debian 13) in the HA-setup with the current official 
guacamole docker running, didn't test yet.

But because it is not integrated in the Loadbalancer i can do a test now 
without interrupt the clients.

I will report back today my test-results.

Tobias

Am 15.12.2025 um 11:15 schrieb Subbareddy Alamuru:

Hi,

I am trying to reproduce this bug where after 60 RDP connections, guacamole 
fails to establish new RDP connections which was first observed in 1.5.5.

However I could not see this issue in the 1.6.0 guacamole version. Anyone out 
there still facing this issue? I just wanted to know for sure if I can upgrade 
my production guacamole version to the 1.6.0 version where ALT+TAB in full 
screen is working.

It definitely still occurs under some circumstances - as Tobias
mentioned, it is a bit dependent upon the environment in which guacd
is running. I have never produced the issue in my environment under
either 1.5.5 or 1.6.0, but I run guacd built native on RHEL/Rocky.
However several other folks have produced it in a variety of different
environments, including the Docker image.

https://issues.apache.org/jira/browse/GUACAMOLE-1998

There is a potential fix for it, but it is quite extensive and still
under review.

https://github.com/apache/guacamole-server/pull/614

-NIck

---------------------------------------------------------------------
To unsubscribe, e-mail:[email protected]
For additional commands, e-mail:[email protected]

Reply via email to