build tmux with utf8proc to allow utf8 in status line

Bug #1665618 reported by Kevin Brubeck Unhammer on 2017-02-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glibc (Ubuntu)
tmux (Debian)
Fix Released
tmux (Ubuntu)

Bug Description

This version of tmux seems to be built without utf8proc, which leads to strange utf8 bugs in the status line. See e.g. the attached image on what happens if the program name has a multibyte char in it (by using `printf '\033k💻NAME\033\\' `).

Could we have tmux built with --enable-utf8proc? It would give a runtime dep on libutf8proc2 and build-dep on libutf8proc-dev.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: tmux 2.2-3
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Feb 17 12:42:33 2017
InstallationDate: Installed on 2011-12-13 (1892 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: tmux
UpgradeStatus: Upgraded to yakkety on 2017-02-07 (9 days ago)

(As an explanation to the image: the status line "wraps around" a character here. Depending on the program running, it's easy to get two or three "stale" status lines on top of each other.)

Joshua Powers (powersj) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu

This bug is present in Debian as well and Ubuntu currently does not make any
changes to the Debian package. Therefore, this bug would be best fixed
directly in Debian, and then Ubuntu will pick up the fix automatically.

Would you mind filing a bug with Debian please?

tags: added: bitesize needs-upstream-report
Changed in tmux (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Changed in tmux (Debian):
status: Unknown → New
Changed in tmux (Debian):
status: New → Fix Released
ChristianEhrhardt (paelzer) wrote :

The Debian bug lead to a discussion around the right solution and terminal configs.
Eventually it led to conclude with:

Yes, glibc was updated to Unicode 9.0.0 a few days ago so version 2.26
will, indirectly, fix this:;a=commit;h=0b38d66a4e2e0d7cb9f40da5bc6e795e20cf3088

That said, adding a glibc task here

Adam Conrad (adconrad) wrote :

glibc in zesty has Unicode 9.0 support, so closing the glibc task.

Changed in glibc (Ubuntu):
status: New → Fix Released
Joshua Powers (powersj) wrote :

Marking the tmux bug as invalid as this was fixed via glibc support.

Changed in tmux (Ubuntu):
status: Triaged → Invalid
Joshua Powers (powersj) wrote :

(hit post too soon)

Also it would be good to confirm that this is indeed working on Zesty as you expect it at this point. You can report back if there still appears to be an issue. Thanks!

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

Other bug subscribers

Remote bug watches

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