TERM=bterm not recognised by ncurses in /target, breaking some applications

Bug #35400 reported by Sebastien Estienne
40
This bug affects 2 people
Affects Status Importance Assigned to Milestone
debian-installer-utils (Debian)
Fix Released
Unknown
debian-installer-utils (Ubuntu)
Fix Released
Medium
Colin Watson

Bug Description

as the rescue shell use TERM=bterm, emacs doesn't want to start
using something like vt100 fixed the issue

Revision history for this message
CMoreno (cmoreno0309) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Revision history for this message
Chris Weiss (cweiss) wrote :

I can help with this..

procedure:
- boot a server, alternate, or jeos cd in rescue/repair mode.
- choose to execute in the /dev/xxxx environment (your install that you want to repair)

expected to happen:
- use editors, aptitude, less, etc, in order to fix the system

what actually happened:
- vim, less, nano, aptitude, and other utilities that depend on a terminal either fail complaining that bterm cannot be opened, or say their functionality is limited and are generally unusable.

Revision history for this message
Colin Watson (cjwatson) wrote :

CMoreno: that might be fine if the reporter hadn't provided enough information. As it happens, though, he did.

(The fact that TERM=bterm breaks some applications in the rescue shell is a well-known issue. I'm working on some approaches to other bugs that might have the side effect of fixing this one too. In the meantime, bug triagers should not touch this bug.)

Changed in rescue:
status: New → Triaged
Revision history for this message
Colin Watson (cjwatson) wrote :

We're going to fix this by a change in debian-installer-utils, accompanied by a new cdebconf plugin. Reassigning.

Changed in debian-installer-utils:
assignee: nobody → kamion
Colin Watson (cjwatson)
Changed in debian-installer-utils:
importance: Low → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package debian-installer-utils - 1.65ubuntu2

---------------
debian-installer-utils (1.65ubuntu2) jaunty; urgency=low

  * start-shell: Use cdebconf-newt-terminal if available (closes: #412168,
    LP: #35400).

 -- Colin Watson <email address hidden> Mon, 16 Feb 2009 14:00:25 +0000

Changed in debian-installer-utils:
status: Triaged → Fix Released
Changed in debian-installer-utils:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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