Running byobu within byobu (on different hosts) breaks 256 color support

[Andreas Ntaflos]

Using byobu version 5.15/tmux 1.5 on Ubuntu 10.04.4.

It seems that running byobu within an existing byobu session breaks or disables 256 colors in the inner byobu session.

Scenario:

1) Log into a server (using SSH)
2) Start byobu
3) From a byobu window, ssh into another server
4) Start byobu on the server just connected to
5) Observe 256colors.pl showing very little color

I have created two screenshots, showing the problem: https://imgur.com/a/Tlqxv

In the first there is only one byobu session and 256 colors work fine, both on the first host (adm01) and on the second (puppet01). Starting byobu on the second host (puppet01) then breaks 256 color support.

[Dustin Kirkland  (kirkland)]

Howdy, thanks for the report! Can you try to confirm this using tmux alone (without Byobu)? I'd like to ensure that this is a bug that Byobu introduces, rather than a factor of using tmux...

[Andreas Ntaflos (daff)]

Sorry, totally forgot to follow up.

It seems tmux alone, in a single instance (no tmux within tmux) breaks 256 colors as well. NB: I have not configured tmux in any way, just running it like "tmux" from a fresh SSH shell. I also found that the problem of broken 256 color support in nested sessions persists when switching backends to "screen".

So it seems the following is true:

1) Single Byobu instance with tmux backend works with 256 colors
2) Single tmux instance breaks 256 colors (probably a configuration issue)
3) Byobu instance (tmux) within Byobu (tmux) breaks 256 colors
4) Tmux instance within tmux: breaks 256 colors (as before)
5) Single Byobu instance with screen backend works with 256 colors
6) Byobu instance (screen) within Byobu (screen) breaks 256 colors

So I think Byobu is somehow responsible, because it seems to be the common element here.

Can I do anything else to debug this?

[Launchpad Janitor (janitor)]

[Expired for byobu (Ubuntu) because there has been no activity for 60 days.]