Bug 26130

Summary: BYOBU+TMUX had redrawing issue
Product: Mageia Reporter: Fabio Pollini <f.open.p>
Component: RPM PackagesAssignee: Joseph Wang <joequant>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: cooker, geiger.david68210
Version: 7   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
URL: https://youtu.be/l0sgX_qFzTY
Whiteboard:
Source RPM: byobu-5.129-1.mga7.src.rpm CVE:
Status comment:
Attachments: In a PTS, set screen-256color
Rewritten with no bashism and no pts check

Description Fabio Pollini 2020-01-24 14:18:07 CET
Description of problem:

Hello everyone,
I noticed in Mageia that xterm-256color is enabled by default during a byobu's tmux session.
This caused redrawing issues during the scroll and cut/paste in the nano editor.
After some test, I discovered that the problem is caused when tmux uses xterm-256color.

On the web I've read various issues caused by xterm-256color under tmux.
The original TMUX author says that's not a his own bug, so it should be a misconfiguration.
More informations here: https://github.com/tmux/tmux/wiki/FAQ

I solved this issue by creating a new /etc/profile.d/byobu.sh file. I attach it in this bugzilla.
IMPORTANT: This file must have 755 permissions (root:root) and a .sh suffix.

The script makes load screen-256color only when a new tmux session has been opened (in pts terminals only).

I suggest you to add this script inside the byobu package. In this way, anytime a user installs byobu the session will be opened with screen-256color.

I tried to open dash, zsh, tcsh and fish (inside a bash session); no shells have shown issues with this script.

You can see a video about the issue (before and after the fix):
https://youtu.be/l0sgX_qFzTY


How reproducible:

Anytime a byobu's tmux session is opened with xterm-256color. No problem with screen-256color.


Steps to Reproduce:
1. urpmi byobu nano
2. byobu
3. nano /etc/mime.types
4. Scroll up and down various times with PgUP and PgDOWN keys.
Sometimes the scroll is correct, some other times there are uncorrect redrawings in terminal's text.
5. Press CTRL+K more times in order to cut about 5-10 lines.
Then press CTRL+U once (or more) in order to paste lines.
Sometimes the paste is correct, some other times there are uncorrect redrawings in terminal's text.
6. (For quitting) Press CTRL+X and type the N letter. Type "exit" for closing the tmux session.


Best regards,
Fabio
Comment 1 Fabio Pollini 2020-01-24 14:20:22 CET
Created attachment 11480 [details]
In a PTS, set screen-256color
Comment 2 Fabio Pollini 2020-01-24 17:05:48 CET
Created attachment 11481 [details]
Rewritten with no bashism and no pts check

I remade the script with no bashisms and with no PTS check (it was not necessary and when you pass from PTS to TTY you can't avoid to use screen-256color).

Attachment 11480 is obsolete: 0 => 1

Comment 3 Lewis Smith 2020-01-24 21:13:45 CET
Thanks for the detailed 'how to reproduce' instructions, which I did not try because the video is comprehensive (if extremely fast)!
Thanks also for /etc/profile.d/byobu.sh (c2)
> This file must have 755 permissions (root:root) and a .sh suffix 
Assigning this to Joseph, because this bug is exactly about an opposite change to byobu:
> Revision 1362766 - Directory Listing
> Modified Sun Feb 3 04:45:17 2019 UTC (11 months, 3 weeks ago) by joequant
> change default to xterm-256color from screen-256color
CC'ing DavidG as having committed most recent versions.

P.S.
> various issues caused by xterm-256color under tmux
> More informations here: https://github.com/tmux/tmux/wiki/FAQ
which begs the question whether 'tmux' is the package to fiddle. solbu is the maintainer for that, so CC'ing him too.

CC: (none) => cooker, geiger.david68210
Assignee: bugsquad => joequant

Comment 4 Aurelien Oudelet 2021-07-06 13:15:43 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 5 Marja Van Waes 2021-09-07 14:10:21 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Resolution: (none) => OLD
Status: NEW => RESOLVED