[
https://issues.apache.org/jira/browse/GUACAMOLE-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879529#comment-17879529
]
Lukas Raska commented on GUACAMOLE-1256:
----------------------------------------
[~mjumper] From some brief testing it seems the "vi" related scolling issue is
not reproducible there and also dumping a lot of text doesn't have any
particular issues. However it overall feels more "laggy" (less fluent than
without it and also compared to RDP session), but I guess that's what you've
already mentioned in the PR as "performance regressions in the terminal
emulator".
> Lines of file gets broken when navigating back and forth using a text editor
> ----------------------------------------------------------------------------
>
> Key: GUACAMOLE-1256
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1256
> Project: Guacamole
> Issue Type: Bug
> Components: Terminal
> Affects Versions: 1.2.0
> Environment: Distributor ID:Ubuntu
> Description:Ubuntu 18.04.2 LTS
> Release:18.04
> Codename:bionic
> Linux dev-kubernetes-01 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Hugaleno Bezerra
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: Screenshot from 2023-10-10 13-39-18.png, Screenshot from
> 2023-10-10 13-41-00.png, bug_scrollingback_onfile.gif,
> image-2024-06-06-18-13-06-244.png
>
>
> Protocol: SSH
> When editing a file using a text editor like vim and navigating back and
> forth in the file some lines get "broken".
> The file being used in the gif below is a default file from ubuntu
> installation "vim /etc/ltrace.conf"
> The problem happens in some servers of our local network, while in anothers
> with same SO it doens't. We tried find a step to step to reproduce the
> problem with 100% accurate but unfortunately we couldn't.
> We decide to share that to see if someone else is having the same problem and
> could help to find the reason.
> If you need any more information to help reproduce de problem pls let me know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
