Shift-F2 no longer working in Byobu in Ubuntu 14.10 (utopic) with tmux 1.9

Bug #1350810 reported by Dustin Kirkland 
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Tmux
New
Undecided
Unassigned
byobu (Ubuntu)
Fix Released
Critical
Dustin Kirkland 
Utopic
Fix Released
Critical
Dustin Kirkland 
tmux (Ubuntu)
Fix Released
High
Unassigned
Utopic
Fix Released
High
Unassigned

Bug Description

There seems to be a regression with the release of tmux 1.9, which we are experiencing in Debian and Ubuntu 14.10 (utopic) systems which have merged the new tmux release.

Shift-F1 - Shift-F8 are no longer being handled properly by Tmux. A tilda, ~, is simply printed to the terminal, rather than the keypress being handled properly as defined in my ~/.tmuxrc with a bindkey -n S-F2 command, for example.

Commit 193b6bcf36dda3754c99beb0dcc3dfdfceebdb09 looks suspect.

Changed in tmux (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Changed in byobu (Ubuntu):
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Dustin Kirkland  (kirkland)
Revision history for this message
Michał Sawicz (saviq) wrote :

Can't link the upstream bug, but here it is: https://sourceforge.net/p/tmux/tickets/144/

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

FWIW, I have pushed a test build of tmux_1.9-5ubuntu1~ppa1_source.changes to ppa:kirkland/ppa, that simply reverts upstream commit 193b6bcf36dda3754c99beb0dcc3dfdfceebdb09.

Please give that a shot on a Utopic/tmux-1.9 system, and report back here if that gets your Shift-F* hotkeys working again. I'll talk to upstream about that, if you can confirm it solves the issue.

Revision history for this message
Michał Sawicz (saviq) wrote :

Hey, sorry for the delay. Unfortunately no, reverting this commit doesn't help (as suggested in the upstream bug).

Revision history for this message
Michał Sawicz (saviq) wrote :

I built a HEAD package (ppa:saviq) as mentioned in the upstream bug, and indeed that helps.

Revision history for this message
Kick In (kick-d) wrote :

Hi,

I have an utopic server with byobu using tmux, and for me all is ok via ssh.
Maybe there is a particular case which make it not working?

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package tmux - 1.9-6ubuntu1

---------------
tmux (1.9-6ubuntu1) utopic; urgency=medium

  * Cherry-pick fix from upstream Git:
    + upstream-2056a9ef9e.diff: fix Shift-Fkeys, LP: #1350810
 -- Dustin Kirkland <email address hidden> Tue, 09 Sep 2014 07:55:48 -0500

Changed in tmux (Ubuntu Utopic):
status: Confirmed → Fix Released
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

This was fixed in tmux. It affected byobu, but it's now fixed with the tmux upload.

Changed in byobu (Ubuntu Utopic):
status: Triaged → Fix Released
Revision history for this message
Rob Parker (rfdparker) wrote :

It may be a different/unrelated issue, but I'm experiencing something similar since rebuilding my laptop with Ubuntu 16.04, having previously been using 14.04.

From gnome-terminal I run byobu (from the Ubuntu 16.04 repos) locally and also, in another gnome-terminal window, I SSH to a Debian 8 server running byobu (from the Debian 8 repos).

Since upgrading my laptop to 16.04 local byobu is still fine, but I'm seeing an issue when using gnome-terminal to SSH to byobu on Debian 8. It is where Shift+F2 simply causes a tilde (~) to be printed, rather than a new horizontal split being created. In-fact Shift+F1 through to Shift+F8 all cause a tilde to be printed.

Do you know whether this issue is related to Ubuntu 16.04's gnome-terminal, Debian 8's byobu, or something else? Notably, the issue did not occur when using gnome-terminal on Ubuntu 14.04 to connect to byobu on the same Debian 8 server. If it's a known issue, is there's a workaround?

Revision history for this message
TenLeftFingers (tenleftfingers) wrote :

I was about to report the same issue here Rob, until I ran byobu --version on the different machines. Turns out the machine I was ssh'd into has:

byobu version 5.87
tmux 1.9

Ubuntu 16.04 has
byobu version 5.106
tmux 2.1

So it looks like the other (Raspbian) machine has the issue. Simple test is, does it work *before* you ssh into Debian? In my case the answer is, yes. So this bug is not an Ubuntu one.

Revision history for this message
Rob Parker (rfdparker) wrote :

Hi TenLeftFingers,

I'm glad to hear I'm not the only one seeing this issue.

However as to whether the issue lies, I would counter that gnome-terminal on Ubuntu 14.04 could connect to the same Debian 8 server and not suffer the issue, whereas the issue does occur when connecting with gnome-terminal on Ubuntu 16.04. The versions of byobu and tmux on the Debian 8 server had not changed between connecting from Ubuntu 14.04 and connecting from Ubuntu 16.04

Yes it's true that byobu on Ubuntu 16.04 itself doesn't suffer the issue, but it appears something within Ubuntu has changed between 14.04 and 16.04 which causes the difference in behaviour when connecting to the same Debian 8 server.

Whether whatever has changed in Ubuntu should be considered a bug, or an expected change, is probably another question - I'd perhaps argue it is a bug, but we'll have to see. Either way, we need to find out what has changed.

Revision history for this message
Rui Apostolo (ruiapostolo) wrote :

I can confirm this bug, running LTS 16.04.1, byobu 5.106 and screen 4.03.01. F-keys not working and byobu-config results in a segfault.

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.