** Description changed: [ Impact ] - * In some versions of Windows Terminal, there's a notorious bug known as - "double encoding of escape sequences." + * In some versions of Windows Terminal, there's a notorious bug known as + "double encoding of escape sequences." - https://github.com/microsoft/terminal/issues/15083 + https://github.com/microsoft/terminal/issues/15083 - This bug causes garbage characters to appear in the input of far2l - when the mouse is moved. + This bug causes garbage characters to appear in the input of far2l + when the mouse is moved. - * The same bug also causes problems with the bracketed paste - functionality. + * The same bug also causes problems with the bracketed paste + functionality. - https://github.com/microsoft/terminal/issues/17656 + https://github.com/microsoft/terminal/issues/17656 - * Furthermore, far2l itself has two issues that exacerbate the situation: - 1) it generates garbage input when receiving unsupported mouse events, and - 2) in win32-input-mode, which is used in Windows Terminal, the zero keycode - should be replaced with the VK_UNASSIGNED constant. Otherwise, Cyrillic - characters (and probably characters of other non-Latin scripts) are ignored - in the data pasted from the clipboard into the terminal. + * Furthermore, far2l itself has two issues that exacerbate the situation: + 1) it generates garbage input when receiving unsupported mouse events, and + 2) in win32-input-mode, which is used in Windows Terminal, the zero keycode + should be replaced with the VK_UNASSIGNED constant. Otherwise, Cyrillic + characters (and probably characters of other non-Latin scripts) are ignored + in the data pasted from the clipboard into the terminal. + + * All listed problems are fixed (or worked around in case of escape sequences + double encoding problem) in master branch of far2l. * Backporting the fix from the master branch will improve Windows Terminal - users UX, both then working in WSL[g] environments or then running far2l - on remote machines via ssh + users UX, both then working in WSL[g] environments or then running far2l + on remote machines via ssh [ Test Plan ] On Windows system: 1. Copy some Cyrillic string to system clipboard ("это строка для проверки", for example). 2. Open Windows Terminal 3. Run far2l inside (in 24.04, in local WSL[g] or by connecting by ssh to remote host) 4. Ask Windows Terminal to do paste by pressing Ctrl+V or Shift+Ins - 5. Try to move mouse over the far2l window + 5. Try to move mouse over the far2l window - Text should be pasted ok and no input garbage should appear + Text should be pasted ok and no input garbage should appear [ Where problems could occur ] * Some input errors in Windows Terminal may occur. However, this way of input processing has been tested in ppa builds from master branch by volunteers and no problems were found. * Also, the fix is Windows Terminal-specific. Even if it breaks something, working in cmd.exe console window still would be possible. [ Other Info ] * wsl_fixes_2410.patch contains fix backported to 24.10 - * ubuntu_wt_fixes.patch contains fix backported to 24.10 + * ubuntu_wt_fixes.patch contains fix backported to 24.04 - * fix_wt_paste.patch is incomplete and should not be used + * fix_wt_paste.patch is incomplete and should not be used ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: 2.6.0~beta+ds-1ubuntu0.2 Architecture: amd64 SourcePackage: far2l
** Tags removed: oracular ** Tags added: noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083233 Title: Clipboard and Mouse Issues in Windows Terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/far2l/+bug/2083233/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
