guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Bereknyei <>
Subject Re:
Date Mon, 22 Aug 2016 22:16:51 GMT
Yes, there's a lot of NixOS wierdness when it comes to linking and
libraries. Most of the time that is taken care of by the default packaging.

strace shows many libraries not being found. But I can't even see it
looking for the (it does exist! it get's built).
I just added an LD_LIBRARY_PATH and it seems to work. But the Nix patchelf
should take care of that. I'll investigate. I'll let you know then Nix can
build both. I'll also try to have a NixOS service to "just make it all


On Mon, Aug 22, 2016 at 6:08 PM, Mike Jumper <>

> On Mon, Aug 22, 2016 at 2:39 PM, Thomas Bereknyei <>
> wrote:
>> Hi,
>> I'm trying to package guacamole for NixOS. I ran into the following
>> issue; Tomcat is serving the client and serves the login page. Guacd is
>> running (compiled with ssh support) and I get the following errors. I can
>> see that the client can at least interact with the server, but the server
>> doesn't like the protocol, even though it was part of the compilation.
>> guacd[1080]: INFO:      Protocol "ssh" selected
>> guacd[1080]: WARNING:   Support for selected protocol is not installed
> Is there anything unique about the way NixOS handles dlopen() (or the
> system linker path)?
> When a particular protocol is about to be used, guacd dynamically loads
> the "" library. This is done via a call to
> dlopen(), which will search the system linker path for the library having
> that name.
> If SSH support was built, but guacd fails to find it at runtime, that must
> mean either:
> 1) The library could not be found in the system
> linker path by dlopen().
> or 2) did not get linked properly during the build,
> and the linker thus cannot load it despite having otherwise found it
> successfully (unlikely)
> - Mike

View raw message