This bug was fixed in the package byobu - 2.46-0ubuntu1
---------------
byobu (2.46-0ubuntu1) lucid; urgency=low
* byobu-janitor: seed the default color choices more effciently, also
fixes some strange crashes on first run; default the colors to white
on black
* byobu-config, doc/help.txt: insert version number in byobu help menu,
LP: #502119
* bin/network: match interface a bit better for bridges, LP: #498722
* bin/logo, bin/release: when looking at /etc/issue, grab the first
line that starts with a real letter rather than control character,
LP: #432751
* byobu: deprecate code that prevented nested byobu sessions; this is
is actually quite useful, although you should choose different
escape sequences for each nested host, LP: #403988
* bin/battery, bin/custom, bin/fan_speed, bin/temp, bin/temp_f: don't
use ls programatically in for-loops, LP: #452405
* bin/cpu_temp, bin/temp_f, bin/temp_c, byobu-config, byobu.1,
profiles/common, rpm/byobu.spec, statusrc: merge temp_f and temp_c
into a single cpu_temp script
* profiles/common: adjust the formatting-only, and run-only-at-startup
status scripts to run every 9,999,999 seconds (~115 days), minor
performance improvement once a day, easier to identify such jobs;
adjust cpu_count and mem_available to run more frequently, as
cpu-hotplug and memory-ballooning are becoming more feasible,
particularly in VMs
-- Dustin Kirkland <[email protected]> Thu, 07 Jan 2010 21:53:14 -0600
** Changed in: byobu (Ubuntu)
Status: Fix Committed => Fix Released
--
Network status break when using bridging
https://bugs.launchpad.net/bugs/498722
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
