Bug#432280: bash-like command interface locks up typing long lines?

2007-07-12 Thread Robert Millan
On Mon, Jul 09, 2007 at 04:01:19PM +1000, Trent Buck wrote:
 On Mon, Jul 09, 2007 at 03:28:42PM +1000, Trent Buck wrote:
  I could enter linux, initrd and boot commands and succeeded in booting
  (yay for tab completion!).  However I noticed that typing a line
  longer wider than the screen, e.g.
  
  linux (hd0,1)/vmlinuz-2.6.21-2-amd64 root=/dev/mapper/Etch-root ro 
  video=radeonfb:1600x1200
  
  caused the system to stop updating the screen.  I couldn't see
  anything I typed appearing, so I tried blindly finishing the command
  and pressing Enter.  Nothing appeared to happen so after a couple of
  seconds [...]
 
 I rebooted again, and I cannot reproduce this behaviour.  When typing
 long lines, this time they continued onto the next line as in an xterm
 running bash.

I'm afraid we can't really debug it unless someone finds an accurate way to
reproduce it.  Perhaps you did something in the first try that you didn't in
the second one?  Can you get it to happen again?

Btw, you might find it easier to use the CD image in grub-rescue-pc for that
(assuming the bug is not dependant on your hardware).

-- 
Robert Millan

My spam trap is [EMAIL PROTECTED]  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#432280: bash-like command interface locks up typing long lines?

2007-07-09 Thread Trent Buck
On Mon, Jul 09, 2007 at 03:28:42PM +1000, Trent Buck wrote:
 I could enter linux, initrd and boot commands and succeeded in booting
 (yay for tab completion!).  However I noticed that typing a line
 longer wider than the screen, e.g.
 
 linux (hd0,1)/vmlinuz-2.6.21-2-amd64 root=/dev/mapper/Etch-root ro 
 video=radeonfb:1600x1200
 
 caused the system to stop updating the screen.  I couldn't see
 anything I typed appearing, so I tried blindly finishing the command
 and pressing Enter.  Nothing appeared to happen so after a couple of
 seconds [...]

I rebooted again, and I cannot reproduce this behaviour.  When typing
long lines, this time they continued onto the next line as in an xterm
running bash.
-- 
Trent Buck


signature.asc
Description: Digital signature


Bug#432280: bash-like command interface locks up typing long lines?

2007-07-08 Thread Trent Buck
Package: grub-pc
Version: 1.95+20070626-1
Severity: normal

After copying /usr/share/grub/unifont.pff to my /boot partition, I
re-ran update-grub and rebooted.  The gfxterm terminal didn't appear
to start (still 640x480 with white text), and there were no entries in
the menu chooser thingy.  I pressed c to enter the bash-like command
mode.

I could enter linux, initrd and boot commands and succeeded in booting
(yay for tab completion!).  However I noticed that typing a line
longer wider than the screen, e.g.

linux (hd0,1)/vmlinuz-2.6.21-2-amd64 root=/dev/mapper/Etch-root ro 
video=radeonfb:1600x1200

caused the system to stop updating the screen.  I couldn't see
anything I typed appearing, so I tried blindly finishing the command
and pressing Enter.  Nothing appeared to happen so after a couple of
seconds so I rebooted the system and dropped the video= argument,
which made the line length short enough to fit, allowing me to boot.

-- Package-specific info:

*** BEGIN /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw 0 0
/dev/mapper/Etch-root / xfs rw 0 0
/dev/mapper/Etch-root /dev/.static/dev xfs rw 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid 0 0
usbfs /proc/bus/usb usbfs rw,nosuid,nodev,noexec 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec 0 0
fusectl /sys/fs/fuse/connections fusectl rw 0 0
/dev/hda1 /boot ext3 rw,data=ordered 0 0
fs:/alt/home /home nfs 
rw,vers=3,rsize=32768,wsize=32768,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=fs
 0 0
fs:/alt /alt nfs 
rw,vers=3,rsize=32768,wsize=32768,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=fs
 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/hda
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automaticaly generated by /usr/sbin/update-grub using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(Etch-root)
font (hd0,1)/grub/unifont.pff
set gfxmode=1600x1200
insmod gfxterm
insmod vbe
terminal gfxterm
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_hurd ###
### END /etc/grub.d/10_hurd ###

### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, linux 2.6.21-2-amd64 {
linux   (hd0,1)/vmlinuz-2.6.21-2-amd64 root=/dev/mapper/Etch-root ro 
initrd  (hd0,1)/initrd.img-2.6.21-2-amd64
}
menuentry Debian GNU/Linux, linux 2.6.21-2-amd64 (single-user mode) {
linux   (hd0,1)/vmlinuz-2.6.21-2-amd64 root=/dev/mapper/Etch-root ro 
single 
initrd  (hd0,1)/initrd.img-2.6.21-2-amd64
}
menuentry Debian GNU/Linux, linux 2.6.21-1-amd64 {
linux   (hd0,1)/vmlinuz-2.6.21-1-amd64 root=/dev/mapper/Etch-root ro 
initrd  (hd0,1)/initrd.img-2.6.21-1-amd64
}
menuentry Debian GNU/Linux, linux 2.6.21-1-amd64 (single-user mode) {
linux   (hd0,1)/vmlinuz-2.6.21-1-amd64 root=/dev/mapper/Etch-root ro 
single 
initrd  (hd0,1)/initrd.img-2.6.21-1-amd64
}
### END /etc/grub.d/10_linux ###
*** END /boot/grub/grub.cfg

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.21-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages grub-pc depends on:
ii  libc6 2.5-11 GNU C Library: Shared libraries
ii  liblzo2-2 2.02-3 data compression library

grub-pc recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]