byobu (screen) goes nuts when running nested byobu (tmux)

Bug #911500 reported by Andres Rodriguez on 2012-01-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone
byobu (Ubuntu)

Bug Description

Running byobu (tmux default) under a byobu screen session causes byobu to go completely nuts making almost impossible to recover the console.

Changed in byobu (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Changed in byobu (Ubuntu):
status: Confirmed → In Progress
Dustin Kirkland  (kirkland) wrote :

Hmm, okay, I did reproduce this once, but I'm not able to reproduce it now. Here's what I've tried...

 1) backend == tmux, running byobu inside of byobu:
kirkland@x220:~$ byobu
sessions should be nested with care. unset $TMUX to force.

 2) backend == tmux, running byobu-tmux inside of byobu:
kirkland@x220:~$ byobu-tmux
sessions should be nested with care. unset $TMUX to force.

 3) backend == tmux, running byobu-screen inside of byobu
(launches a new byobu-screen session)

 4) backend == screen, running byobu inside of byobu:
kirkland@x220:~$ byobu
Attaching from inside of screen?

 5) backend == screen, running byobu-tmux inside of byobu:
(launches a new byobu-tmux session)

 6) backend == screen, running byobu-screen inside of byobu:
kirkland@x220:~$ byobu-screen
Attaching from inside of screen?

Changed in byobu (Ubuntu):
status: In Progress → Incomplete
Dustin Kirkland  (kirkland) wrote :

Andres, can you still reproduce this? I know that I saw it once, but I'm not seeing it any more...

Andres Rodriguez (andreserl) wrote :

Hi Dustin,

Yes I was able to reproduce this bug today again:

1. Turned on precise machine.
2. Run byobu
3. Run byobu-tmux inside byobu and things went crazy.
4. killed the byobu processes
5. Run byobu
6. Run byobu-tmux inside byobu, and this was showed:
sessions should be nested with care. unset $TMUX to force.
7. i did TMUX='' inside byobu.
8. Run byobu-tmux, and bug showed again.

Hope this helps.


Changed in byobu (Ubuntu):
status: Incomplete → Fix Committed
Dustin Kirkland  (kirkland) wrote :

Okay, committed a fix.

Committed revision 1879.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package byobu - 5.6-0ubuntu1

byobu (5.6-0ubuntu1) precise; urgency=low

  [ Dustin Kirkland ]
  * usr/lib/byobu/ip_address:
    - user@host and ipaddress need some separation, as they're hard to
      differentiate when next to one another
  * usr/bin/byobu-ctrl-a: LP: #922951
    - if the user has already chosen an escape sequence, don't run the
      interactive byobu-ctrl-a program
  * usr/share/byobu/keybindings/f-keys.tmux,
    - empty default window names
    - easy to change with F8
    - need to save characters in default tmux launch to get it to fit
      in 80x24 terminals
  * experimental/byobu-classroom, usr/bin/byobu-config, usr/bin/byobu-
    ctrl-a, usr/bin/byobu-janitor, usr/bin/byobu-launcher-uninstall,
    usr/bin/byobu-quiet, usr/bin/byobu-silent, usr/bin/byobu-status,
    usr/lib/byobu/cpu_temp, usr/lib/byobu/custom,
    usr/lib/byobu/ec2_cost, usr/lib/byobu/include/constants,
    usr/lib/byobu/logo, usr/lib/byobu/menu, usr/lib/byobu/network,
    usr/share/byobu/keybindings/f-keys: LP: #920661
    - byobu should not set environment variable 'SED'
    - use BYOBU_SED instead
  * usr/bin/byobu, usr/bin/byobu-janitor, usr/lib/byobu/disk_io,
    - use BYOBU_READLINK instead of READLINK
  * usr/bin/byobu-select-session: LP: #911500
    - detect and avoid some circular byobu-inside-byobu infinite loops
  * usr/bin/byobu, usr/bin/byobu-ctrl-a, usr/bin/byobu-reconnect-
    sockets, usr/lib/byobu/color, usr/lib/byobu/date,
    usr/lib/byobu/include/shutil, usr/lib/byobu/time:
    - make check for BYOBU_BACKEND explitly tmux|screen

  [ Ryan Thompson ]
  * usr/bin/byobu-select-session: LP: #919391
    - read only integers
  * usr/bin/byobu-select-session: LP: #908944
    - use attach_session function
 -- Dustin Kirkland <email address hidden> Wed, 18 Jan 2012 19:57:15 -0600

Changed in byobu (Ubuntu):
status: Fix Committed → Fix Released
James Gifford (jamesgifford) wrote :

I encountered this on 12.10 today.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers