-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Print functionality is not working after passing print configuration. #14
Comments
Just making sure I understand the workflow. You are printing from inside an RDP window session to a "Guacamole Printer" and then getting the error. Can you confirm. We don't do much printing so we've never tested before. After you confirm we can take a look and see if anything jumps out as an easy fix. |
yes @mattskipton the workflow is same as you mentioned . |
|
@mangeshtanpure123 we can take a look, could you provide the docker config your using so we can re-create. The config your using would help a lot also. |
@mattskipton I'm using same setup as mentioned in readme.
this is the config map that i am passing with guacd , "enable-printing":"true" after adding this config i can see the gucamole printer in rdp session. |
After taking RDP access i was trying to print document .Guacamole printer is visible after selecting the printer getting error while printing.
didn't find any error's in client , found error in server (gaucd) which works fine with (https://github.com/apache/guacamole-client) client .
guacd[3754]: INFO: Connected to RDPDR 1.13 as client 0x0002
guacd[3754]: INFO: RDPDR user logged on
guacd[3754]: INFO: Print job created
guacd[3754]: INFO: Created PDF filter process PID=3779
guacd[3779]: INFO: Running gs
guacd[3754]: INFO: User explicitly aborted print stream.
GPL Ghostscript 9.27: Unrecoverable error, exit code 1
GPL Ghostscript 9.27: ERROR: ioerror (-12) on closing pdfwrite device.
guacd[3754]: INFO: Accepted format: 16-bit PCM with 2 channels at 44100 Hz
Not sure if problem is with go client or vue.js code
The text was updated successfully, but these errors were encountered: