Bug#412168: debian-installer: Rescue mode: terminal 'bterm' doesn't play nice with some apps in rescue shell
reassign 412168 di-utils thanks On Sat, Feb 24, 2007 at 07:44:20AM +0100, Alain Kalker wrote: > After booting into rescue mode and starting a shell in my root > partition from the menu, the grub shell and some other > tools messed up my screen, probably because the terminal type 'bterm' > wasn't fully supported. > 'man' (using 'more' as pager, I think) complained about some terminal > functions probably not working correctly, while the grub shell overwrote > much of its own output, making it mostly unusable. We should be able to fix this now that cdebconf-newt-terminal exists and does most of the work necessary to provide the chroot with a working terminfo file for bterm. I'm reassigning this over to di-utils, which needs to make use of that new plugin in order to fix this bug. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#412168: debian-installer: Rescue mode: terminal 'bterm' doesn't play nice with some apps in rescue shell
Processing commands for [EMAIL PROTECTED]: > reassign 412168 rescue Bug#412168: debian-installer: Rescue mode: terminal 'bterm' doesn't play nice with some apps in rescue shell Bug reassigned from package `debian-installer' to `rescue'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412168: debian-installer: Rescue mode: terminal 'bterm' doesn't play nice with some apps in rescue shell
Package: debian-installer
Severity: normal
(From memory, please forgive minor errors in naming etc.)
After booting into rescue mode and starting a shell in my root
partition from the menu, the grub shell and some other
tools messed up my screen, probably because the terminal type 'bterm'
wasn't fully supported.
'man' (using 'more' as pager, I think) complained about some terminal
functions probably not working correctly, while the grub shell overwrote
much of its own output, making it mostly unusable.
I tried changing terminal emulation to
TERM={ansi,linux,vt52,vt100,vt102,vt200} with mixed but unsatisfactory
results. Does this have something to do with the console
(framebuffer) driver used during installation?
On a normal boot, my system has VCs without framebuffer, TERM=linux.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
