Uploaded image for project: 'Guacamole'
  1. Guacamole
  2. GUACAMOLE-196

Backslashes in document title cause printing to fail

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 0.9.10-incubating, 0.9.11-incubating
    • Fix Version/s: 0.9.12-incubating
    • Component/s: guacamole
    • Labels:
      None

      Description

      Guacamole since 0.9.10 to 0.9.11 doesn´t print on Windows RDP (Windows Server 2012r2 to 2016) on many softwares. The best test cenarious is try to print a self-test page on guacamole redirected printer (doesn´t work). In Wordpad for example is ok, but on acrobat read doesn´t print.

      Please help with this. I can´t migrate all my enviroment to new versions because of this.

      Thanks for your efforts. I tested on many linux distro and versions.

        Issue Links

          Activity

          Hide
          snunes SNunes1 added a comment - - edited

          I have the same problem too.... on one or another software the printer doesn't work. In 0.9.9 doesn't have this problem.

          Show
          snunes SNunes1 added a comment - - edited I have the same problem too.... on one or another software the printer doesn't work. In 0.9.9 doesn't have this problem.
          Hide
          mike.jumper Michael Jumper added a comment -

          Thiago dos Santos Nunes and SNunes1, when printing fails with 0.9.10 and 0.9.11, do you see an error in the browser's error console?

          I was recently looking into an issue similar to that described here, and found that certain characters in the title of the document were causing the REST service to return HTTP 400 rather than initiate the download of the printout. I suspect that might be happening here, too.

          Show
          mike.jumper Michael Jumper added a comment - Thiago dos Santos Nunes and SNunes1 , when printing fails with 0.9.10 and 0.9.11, do you see an error in the browser's error console? I was recently looking into an issue similar to that described here, and found that certain characters in the title of the document were causing the REST service to return HTTP 400 rather than initiate the download of the printout. I suspect that might be happening here, too.
          Hide
          TdSN Thiago dos Santos Nunes added a comment -

          How can I help you with this?

          There is any test I can do to help you with this? My Windows Server 2012 r2 is on portuguese language.

          Show
          TdSN Thiago dos Santos Nunes added a comment - How can I help you with this? There is any test I can do to help you with this? My Windows Server 2012 r2 is on portuguese language.
          Hide
          mike.jumper Michael Jumper added a comment -

          Please try printing a document which you know fails under 0.9.10 or 0.9.11, and look at your browser's error console. If you see an HTTP 400 error listed, then this is likely the problem.

          Show
          mike.jumper Michael Jumper added a comment - Please try printing a document which you know fails under 0.9.10 or 0.9.11, and look at your browser's error console. If you see an HTTP 400 error listed, then this is likely the problem.
          Hide
          TdSN Thiago dos Santos Nunes added a comment - - edited

          "I was recently looking into an issue similar to that described here, and found that certain characters in the title of the document were causing the REST service to return HTTP 400 rather than initiate the download of the printout. I suspect that might be happening here, too."

          I agree...

          There are special characters on the title of the files like accentuation in portuguese language.

          Below the error on the printing of self-test page in the debug console:

          app.js:486 GET http://192.168.33.120:8080/guacamole/api/session/tunnels/70d2cbf1-d611-47b4…pdf?token=3758BD8057EE896E44795EA747AF71FD793751B7B79F5BBB5B37E71F00A0C8E8 400 (Bad Request)
          a.downloadStream @ app.js:486
          l.onfile @ app.js:328
          file @ app.js:27
          a.oninstruction @ app.js:33
          b.onmessage @ app.js:120

          Show
          TdSN Thiago dos Santos Nunes added a comment - - edited "I was recently looking into an issue similar to that described here, and found that certain characters in the title of the document were causing the REST service to return HTTP 400 rather than initiate the download of the printout. I suspect that might be happening here, too." I agree... There are special characters on the title of the files like accentuation in portuguese language. Below the error on the printing of self-test page in the debug console: app.js:486 GET http://192.168.33.120:8080/guacamole/api/session/tunnels/70d2cbf1-d611-47b4 …pdf?token=3758BD8057EE896E44795EA747AF71FD793751B7B79F5BBB5B37E71F00A0C8E8 400 (Bad Request) a.downloadStream @ app.js:486 l.onfile @ app.js:328 file @ app.js:27 a.oninstruction @ app.js:33 b.onmessage @ app.js:120
          Hide
          mike.jumper Michael Jumper added a comment -

          This should now be fixed on git master of incubator-guacamole-client. Please try building the latest when you can, and see if that fixes things.

          Show
          mike.jumper Michael Jumper added a comment - This should now be fixed on git master of incubator-guacamole-client. Please try building the latest when you can, and see if that fixes things.
          Hide
          TdSN Thiago dos Santos Nunes added a comment -

          I will try now. Thanks a lot.

          Show
          TdSN Thiago dos Santos Nunes added a comment - I will try now. Thanks a lot.

            People

            • Assignee:
              mike.jumper Michael Jumper
              Reporter:
              TdSN Thiago dos Santos Nunes
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development