~/.screenrc is sourced twice with profile NONE

Bug #382642 reported by Anders Kaseorg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
byobu (Ubuntu)
Fix Released
Low
Dustin Kirkland 

Bug Description

Binary package hint: byobu

byobu uses the configuration file /usr/share/byobu/profiles/byoburc, which sources ~/.byobu/profile and ~/.screenrc. Selecting the NONE profile makes ~/.byobu/profile a symlink to /usr/share/byobu/profiles/NONE, which also sources ~/.screenrc.

The NONE profile should just be empty instead of sourcing ~/.screenrc again.

Related branches

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

Thanks for the report, fix committed. Will be in the next upload.

:-Dustin

Changed in byobu (Ubuntu):
assignee: nobody → Dustin Kirkland (kirkland)
importance: Undecided → Low
milestone: none → karmic-alpha-2
status: New → Fix Committed
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Committed revision 497.

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

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

---------------
byobu (2.9-0ubuntu1) karmic; urgency=low

  * screen-launcher: slightly cleaner bash exit (still could use some
    improvement)
  * select-screen-profile: update to say "byobu" rather than screen,
    LP: #382643
  * bin/wifi-quality, bin/network-up, bin/network-down: must use /sbin
    in iwconfig and ifconfig paths
  * bin/cpu-count: performance improvement, use getconf
  * bin/cpu-freq: performance improvement, simplify pipes
  * bin/disk-*: use the POSIX output format
  * bin/ec2-cost: performance improvement, cache ifconfig output
  * bin/logo: use a case-statement instead of nasty if/then/else stack
  * profiles/NONE: don't source ~/.screenrc, causes a nasty recursion,
    LP: #382642

 -- Dustin Kirkland <email address hidden> Mon, 08 Jun 2009 17:46:24 -0500

Changed in byobu (Ubuntu):
status: Fix Committed → Fix Released
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.