byobu+tmux 2.0 crashes after startup

Bug #1489765 reported by CarNagE
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
byobu
Incomplete
Critical
Unassigned

Bug Description

I recently download, compiled, and installed tmux 2.0 from https://tmux.github.io/ as I needed a few of its new features. When starting byobu (5.94, for the record, but also happens with 5.74, e.g.) with tmux backend, it crashes a few seconds (varies between 0 and 20) after startup and does not accept any input anymore. I can see the clock in the status bar updating for a while and then it stops.

I already deleted ~/.byobu and ~/.tmux.conf (if that is loaded at all?) which did not change anything. I do use zsh as shell but changing my shell back to bash did not result in any further success... Switching byobu's backend to screen fixes the issue, but then I have to use screen ;) Downgrading tmux to version 1.8 also fixes the issue, but then I cannot use the new features ;)

Comment from the maintainer of byobu on stackoverflow regarding the issue:
"It's likely a permissions issue, perhaps something in /dev/shm, where the distro version of tmux 1.8 sets up those permissions properly in the package maintainer scripts, but your self compiled one does not do so with a simple 'make install'?"

I attached an strace of byobu before the crash. Please let me know if I can provide any other debugging info.

Revision history for this message
CarNagE (tobias-inet00) wrote :
description: updated
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Thanks for moving this over from StackExchange to a bug here in Launchpad.

Thus far, I've been unable to reproduce this.

I've tried both an Ubuntu 15.10 desktop and server, both of which use tmux 2.0.

I'm going to mark this as incomplete for now, but that's just housekeeping, until someone else is able to confirm the problem.

Changed in byobu:
importance: Undecided → High
status: New → Incomplete
importance: High → Critical
Revision history for this message
CarNagE (tobias-inet00) wrote :

It seems this is a tmux issue as the problem also occurs when just using tmux. However, it seems to take much longer to occur, that's why I initially assumed that it was not a tmux problem. I create a bug report there. I guess you can close this bug report.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Thanks. Can you please drop a link to the tmux issue, in case someone else hits it here too?

Cheers!
Dustin

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.