Hi, I am using Guacamole 1.0.0 in Debian 9 with Tomcat 8, database authentication with self-sgned SSL certificate.
After following the installation documentation <https://guacamole.apache.org/doc/gug/installing-guacamole.html> I documented my initial 0.9.14 installation steps here <https://wiki.debian.org/Guacamole>. I then recently used this script <https://raw.githubusercontent.com/MysticRyuujin/guac-install/master/guac-upgrade.sh> to update, while working around a small bug <https://github.com/MysticRyuujin/guac-install/issues/77>. VNC, SSH and RDP remote sessions are used daily without problems. I can't seem to get a prompt to save the PDF file generated when printing in RDP sessions. I initially had to symlink all files in /usr/local/lib/freerdp to /usr/lib/x86_64-linux-gnu/freerdp, for example (see this bug report <https://github.com/oznu/docker-guacamole/issues/3>): ln -s /usr/local/lib/freerdp/guacdr-client.so /usr/lib/x86_64-linux-gnu/freerdp/guacdr-client.so After reboot guacdr started normally: Feb 27 14:35:19 guacamole guacd[14998]: guacsnd connected. Feb 27 14:35:19 guacamole guacd[14998]: guacdr connected. When connected, a new printer "Guacamole PDF printer" (as I named it) showed up. When I start printing there is no error, only a message on my local browser notifications "Waiting for guacamole.domain.lan...:" and nothing happens. Ghostscript is installed, in /var/syslog I see: Feb 27 14:44:51 guacamole guacd[23876]: Device 0 (Imprimante Guacamole PDF) connected successfully Feb 27 14:45:07 guacamole guacd[23876]: Print job created Feb 27 14:45:07 guacamole guacd[23876]: Created PDF filter process PID=24158 Feb 27 14:45:07 guacamole guacd[24158]: Running gs And a gs process is running continuously: PID TTY STAT TIME COMMAND 24158 ? S 0:06 gs -q -dNOPAUSE -dBATCH -dSAFER -dPARANOIDSAFER -sDEVICE=pdfwrite -sOutputFile=- -c .setpdfwrite -sstdout=/dev/null -f - But nothing happens... If I close the session then a file dialog to save appears, the resulting file is very small (255 bytes) and of course corrupted but it has PDF headers. I tested this using both Firefox ESR and 65, Chrome and Chromium, from Debian 9 and WIndows 7 Pro desktops with the same results. Any ideas or suggestions on how to troubleshoot further ? Thanks in advance. F. -- Fabián Rodríguez http://fsf.magicfab.ca/
