Status line corruption

[Julian Edwards]

The status line on my byobu instance is not displaying correctly and running off the edge of the window, which results in it slowly creeping up the page. (see attached)

I'm not sure how this happens. I am ssh'ed into a remote trusty instance from a trusty instance. The local byobu is fine in the same terminal window (Konsole) but when I ssh to the remote system and run it, it's corrupt.

[Julian Edwards (julian-edwards)]

Oh interesting, I just did this with gnome-terminal and I have the same problem. Maybe this is locale-related?

[Dustin Kirkland  (kirkland)]

Hey bigjools, can you try disabling UTF-8 characters? I suspect there's something in there that's being interpreted as a newline incorrectly.

    Alt-F5 Toggle UTF-8 support, refresh status

[Julian Edwards (julian-edwards)]

Hi Dustin - I'll give it a go next time I see it happen. I have a suspicion
that it's something to do with the sending rather than the receiving end,
since using the same laptop I get problems on some servers and not others.

On Monday 23 March 2015 18:14:31 you wrote:
> Hey bigjools, can you try disabling UTF-8 characters? I suspect there's
> something in there that's being interpreted as a newline incorrectly.
>
> Alt-F5 Toggle UTF-8 support, refresh status
>
>
> ** Changed in: byobu
> Importance: Undecided => Medium
>
> ** Changed in: byobu
> Status: New => Incomplete

[Douglas King (douglask)]

After pressing alt+F5, the issue persists, just without unicode characters on the status line.

This issue is reproducable when using BitVise SSH as the terminal client, images of issue and BitVise terminal settings are here:
http://imgur.com/a/0fRoC

I have installed the core Ubuntu fonts into Windows and am using Ubuntu Mono.

Let me know if there's any other information I can get for you. This issue renders byobu unusable to me.

[Skeith (suyalynx)]

I am using Bitvise SSH Client, byobu was awesome until I just hit with this issue. How can I fix this?

Changing backend to screen fix it but I prefer tmux

[YUKI Hiroshi (piro-or)]

I also saw this problem on WSL (Windows Subsystem for Linux) console:

Case 1: local byobu on WSL console

 * Envilonment: Ubuntu 18.04 on WSL
 * Steps to reproduce:
   1. Start Ubuntu on WSL.
   2. Install byobu.
   3. Start byobu.

Case 2: remote byobu on Ubuntu via WSL console

 * Client: Ubuntu 18.04 on WSL
 * Server: Ubuntu 18.04
 * Steps to reproduce:
   1. Start Ubuntu on WSL.
   2. Log in to the Ubuntu server.
   3. Start byobu on the Ubuntu server.

This problem happens on the default console of WSL, but it doesn't happen on wsltty ( https://github.com/mintty/wsltty/releases ) and GNOME terminal running on the Ubuntu server itself.

[Skeith (suyalynx)]

On my case, it usually happened when a pending reboot is required. After a reboot, the status line is fine again

[SBKch (ssbkch)]

Same problem for me, problem occurs (just like on the screenshot) when reboot_required in status notifications is enabled and system requires restart.
Client: Konsole on Kubuntu 18.04, kernel 4.17.13, encoding: UTF-8
Server: Ubuntu 18.04