Package Details: guacamole-server 0.9.14-2

Git Clone URL: (read-only)
Package Base: guacamole-server
Description: Guacamole proxy daemon
Upstream URL:
Keywords: guacamole
Licenses: GPL3
Replaces: guacd, libguac, libguac-client-rdp, libguac-client-ssh, libguac-client-vnc
Submitter: ShyPixie
Maintainer: figue (figuepluto, jfigueras)
Last Packager: figuepluto
Votes: 21
Popularity: 0.702422
First Submitted: 2013-09-17 15:21
Last Updated: 2018-05-24 22:21

Dependencies (18)

Required by (0)

Sources (3)

Latest Comments

1 2 3 4 5 6 Next › Last »

Marcel_K commented on 2018-08-28 22:47

@figue: Correct, but you should be able to compile against tagged releases < 2 on GitHub.

I installed freerdp 1.2.0_beta1+android9 by rebuilding it from source using the PKGBUILD and the patch from that version in SVN. After this, I managed to build this package by adding -Wno-error=stringop-truncation to CPPFLAGS. Of course, this is bad practice, but I managed to connect to an RDP server.

figue commented on 2018-07-11 13:36

AFAIK rdp is broken due to unsupported freerdp versioning...

I've just compiled and in my case RDP is disabled during configure phase:

checking for freerdp_new in -lfreerdp-core... no
checking for freerdp_new in -lfreerdp... no
configure: WARNING:
   Unable to find libfreerdp-core / libfreerdp
   RDP will be disabled.

schickel commented on 2018-07-11 10:11

I'm getting an error installing guacamole-server:

make[3]: Entering directory '/tmp/yaourt-tmp-mk/aur-guacamole-server/src/guacamole-server-0.9.14/src/protocols/rdp'
  CC       guac_svc/guacsvc_client_la-svc_service.lo
guac_svc/svc_service.c: In function 'VirtualChannelEntry':
guac_svc/svc_service.c:56:5: error: 'strncpy' output may be truncated copying 7 bytes from a string of length 7 [-Werror=stringop-truncation]
     strncpy(svc_plugin->, svc->name,
cc1: all warnings being treated as errors
make[3]:  [Makefile:1489: guac_svc/guacsvc_client_la-svc_service.lo] Error 1
make[3]: Leaving directory '/tmp/yaourt-tmp-mk/aur-guacamole-server/src/guacamole-server-0.9.14/src/protocols/rdp'
make[2]:  [Makefile:832: all] Error 2
make[2]: Leaving directory '/tmp/yaourt-tmp-mk/aur-guacamole-server/src/guacamole-server-0.9.14/src/protocols/rdp'
make[1]:  [Makefile:503: all-recursive] Error 1
make[1]: Leaving directory '/tmp/yaourt-tmp-mk/aur-guacamole-server/src/guacamole-server-0.9.14'
make:  [Makefile:427: all] Error 2
==> ERROR: A failure occurred in build().
==> ERROR: Makepkg was unable to build guacamole-server.
==> Restart building guacamole-server ? [y/N]
==> -----------------------------------------

I followed the recomendations from "robocop commented on 2017-10-17 15:50" to get rdp work. Rebuilding guacamole-server failed.

figue commented on 2018-05-24 22:25

@fryfrog fixed. Thanks for the report!

fryfrog commented on 2018-05-24 21:11

Building for a fresh install on latest Arch seems to have a problem:

make[2]: Entering directory '/tmp/trizen-fryfrog/guacamole-server/src/guacamole-server-0.9.14/src/guacenc'
  CC       guacenc-guacenc.o
guacenc.c: In function 'main':
guacenc.c:79:5: error: 'avcodec_register_all' is deprecated [-Werror=deprecated-declarations]
In file included from guacenc.c:27:
/usr/include/libavcodec/avcodec.h:4086:6: note: declared here
 void avcodec_register_all(void);
cc1: all warnings being treated as errors

figue commented on 2018-03-16 10:36

@kcwitt libtelnet and uuid are packages in AUR. makepkg can only install if the packages are in a repository.

You can use yaourt or pacaur to get and build AUR packages automatically though.

kcwitt commented on 2018-03-16 02:12

nice work @robocop (especially the tip about installing ffmpeg2.8).

the only other thing that confused me was that the libtelnet and uuid packages need to be built (using the same process as building this package), prior to building this package (ie. this is not something the makepkg system works out for us automatically).

I haven't tested much other than to display a machine running in virtualbox yet (so can't confirm sound, etc.). But thrilled to have gotten this far.

figue commented on 2017-10-17 21:28

@robocop thanks again. In my case, I can't revert to older versions because of security concerns in my company. Anyway it's really great that you could workaround the RDP issue.

I read some time ago in guacamole mail list that they would wait until FreeRDP 2.0 stable were released to patch guacamole code, because of the constant changes in FreeRDP synthax.

If you are really interested, write in guacamole mail list to keep the focus :)

robocop commented on 2017-10-17 15:50

I managed to connect via RDP on fully updated arch headless installation (except freerdp of course, which is: 1.2.0_beta1+android9-1 from: 9-Nov-2014 16:50 [])

# standard situation is when you are building guacamole-server, you will see that rdp protocol support cannot be detected
# guacamole at this time requires older version of freerdp (i dont know how old exactly, i have succesfuly tried this one, so i moved on)
pacman -U
# i chose default options regarding dependencies
pacman -Qi freerdp | grep Version
# output: Version : 1.2.0_beta1+android9-1
# at this point, when you build guacamole-server package, you will see that rdp is supported as guacamole can find all freerdp files
# but when you try connect to rdp connection via guacamole-client, you can see in journal logs that "rdp support is not installed"
# then i noticed that freerdp is broken as you can see with following command
xfreerdp /version
# output: xfreerdp: error while loading shared libraries: cannot open shared object file: No such file or directory
# maybe this error prevented guacamole from using freerdp, so i installed missing package (pacman -Ss libavcodec)
pacman -S ffmpeg2.8
xfreerdp /version
# output: This is FreeRDP version 1.2.0-beta1 (git n/a)
# error with freerdp is gone
# next step is: ....rebuild and install guacamole from aur....
systemctl daemon-reload
systemctl restart guacd
systemctl restart tomcat7
# after these steps i was able to connect via rdp

Tip: when you see in journal logs: guacd Error connecting to RDP server
Check you connection in user-mapping.xml, i had to use all parameters: hostname,port,username,domain,password,ignore-cert=true,security=any
When i set last possible parameter <param name="security">any</param>, error was gone and connection was succesful

@figue: looks great

figue commented on 2017-10-15 19:14

@robocop what do you think?