[
https://issues.apache.org/jira/browse/GUACAMOLE-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028103#comment-18028103
]
Nick Couchman commented on GUACAMOLE-2150:
------------------------------------------
[~sh0tgun]:
{quote}If you allow a personal suggestion: it is not appropriate to downgrade
the priority to “minor” given its overall impact on the use of the solution.
{quote}
I downgraded it because the relative priority of this for the overall project
is lower than things like severe performance issues, processes not exiting or
cleaning up, and display rendering issues. The priority is not intended to say
whether or not this is a "Blocker" or "Major" issue for *your* use of the
project, it's a reflection of the relative importance of correcting or
implementing the various issue as we progress in versions. Issues that are
marked as "Blockers" are ones that we would not consider releasing the next bug
fix release without fixing it. This issue doesn't fall into that category - if
we track down the issue and are able to get the fix into the 1.6.1 bug fix
release, great, but my view is that we would not hold the 1.6.1 bug fix release
for this issue.
Beyond that, we now have 2 reports of this issue (you and David, basically) -
as compared to some of the other issues mentioned above. In my opinion, this
takes it out of the "Major" category, as well - again, not that it isn't
important to your use of the software, or David's, but that, as we prioritize
the issues that we feel are important to dig into and fix in the next bug
release, it appears to impact fewer people and isn't as high a priority as some
of the others where we get several reports or that have impact on the stability
of the software.
Last thing - I'm human, and fallible, and so it may be that I'm wrong about
this and that many other folks will start reporting that this is a problem, or
that other members of Guacamole's PMC will disagree with me on the priority and
correct it. The above is my perspective and opinion, and I'm only one person,
and a person that is frequently wrong :).
> Pasting doesn't respect text formatting
> ---------------------------------------
>
> Key: GUACAMOLE-2150
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-2150
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 1.6.0
> Environment: Docker deployment on Ubuntu server.
> Reporter: Daniel D'Angeli
> Priority: Minor
> Attachments: image-2025-10-03-15-50-49-130.png,
> image-2025-10-03-16-03-47-402.png, image-2025-10-07-15-41-13-067.png,
> immagine (1).png, immagine.png
>
>
> When pasting long text with multiple rows, Guacamole adds an empty line in
> between the rows breaking text formatting. This doesn't happen with
> JumpServer, so it's not browser fault.
> Tried both with Firefox and Chrome, same issue.
> For example, this curl command with multiple rows:
> curl [https://www.google.com|https://www.google.com/] \
> -X GET \
> -H "User-Agent: Mozilla/5.0" \
> -H "Accept: text/html" \
> -L
> Insted of being executed as a single command, is sent to the target as a
> command per row, resulting in the screenshot attached.
> Another example is this docker-compose,yaml file:
> services :
> guacamole:
> image: guacamole/guacamole: 1.6.0
> environment :
> - GUACAMOLE_LDAP_ENCRYPTION_METHOD: starttls
> - GUACAMOLE_LDAP_DISABLE_VERIFY: "true"
> - JAVA_OPTS: "-Djavax. net . ssl . trustStore=/path/to/cacerts -Djavax.
> net. ssl. trustStorePassword=changeit"
>
> This behaviour doesn't allow operators to smoothly work on machines,
> resulting in a turn off of guacamole in our infrastructure and look for other
> solutions.
> Feel free to ask anything if needed.
> Regards,
> Daniel D.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
