Long arch-journey-story short (I hope): built my first 64-bit system back in February and used a 64-bit OS for the first time then. After a couple months, a few peculiar quirks motivated me to try the 32-bit arch of the distro I currently prefer(Debian/testing) instead. The quirk this thread is about was not present on i386, but I'm noticing it again, now that I've bought a new motherboard and installed Lenny/amd64 (as i386 seems a bit sluggish in comparison).
So anyhow, the problem is that sometimes in Konsole or Xterm (and presumably other terminal emulators), if I hit Enter once, the terminal seems to interpret it as many more than one keypress, and in some cases this means it automatically chooses the default response to queries like "Proceed? Y/n/q". So far I've only noticed this using aptitude and apt-get(which I only used to see if applications other than aptitude were affected). I'll edit this post or reply later if/when I notice this behaviour with other programs.
for example (I've added "^C" and 1 line break where I hit CTRL+C, to make things a bit easier on the eyes):
(avidemux was the first dependency-requiring app which I don't have installed that came to mind, and this happening on an 'aptitude full-upgrade' just now is what got me posting)
I looked at the buglist for aptitude and searched through it for the word "key"(as in keypress) but didn't come up with anything. I found a Debian wiki entry for MacBooks refering to "double keypresses" but it was related to debian-installer (and MacBooks). I have a Gigabyte MA790FX-DS5, Athlon X2 4850e, and 4GB DDR2/800, but I'm reasonably sure this has nothing to do with hardware.
So anyhow, the problem is that sometimes in Konsole or Xterm (and presumably other terminal emulators), if I hit Enter once, the terminal seems to interpret it as many more than one keypress, and in some cases this means it automatically chooses the default response to queries like "Proceed? Y/n/q". So far I've only noticed this using aptitude and apt-get(which I only used to see if applications other than aptitude were affected). I'll edit this post or reply later if/when I notice this behaviour with other programs.
for example (I've added "^C" and 1 line break where I hit CTRL+C, to make things a bit easier on the eyes):
Code:
gc@basestar:~$ sudo aptitude install avidemux Reading package lists... Done Building dependency tree... 50% Building dependency tree Reading state information... 0% Reading state information... Done Reading extended state information... 0% Reading extended state information... 32% Reading extended state information Initializing package states... 0% Initializing package states... Done Reading task descriptions... Done The following NEW packages will be installed: avidemux avidemux-common{a} lame{a} liblame0{a} libmjpegtools0{a} libquicktime1{a} libswscale1d{a} libx264-59{a} mjpegtools{a} toolame{a} 0 packages upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 5488kB of archives. After unpacking 14.4MB will be used. Writing extended state information... Done Get:1 http://debian.yorku.ca lenny/main libswscale1d 0.cvs20070307-6 [95.2kB] Get:2 http://debian.yorku.ca lenny/main libquicktime1 2:1.0.2+debian-2 [342kB] 5% [Waiting for headers] [2 libquicktime1 185401/342kB 54%] ^C gc@basestar:~$ sudo apt-get install avidemux Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: avidemux-common lame liblame0 libmjpegtools0 libquicktime1 libswscale1d libx264-59 mjpegtools toolame Suggested packages: sox mpeg2dec a52dec The following NEW packages will be installed: avidemux avidemux-common lame liblame0 libmjpegtools0 libquicktime1 libswscale1d libx264-59 mjpegtools toolame 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 5393kB/5488kB of archives. After this operation, 14.4MB of additional disk space will be used. Do you want to continue [Y/n]? n Abort. gc@basestar:~$ sudo apt-get install avidemux Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: avidemux-common lame liblame0 libmjpegtools0 libquicktime1 libswscale1d libx264-59 mjpegtools toolame Suggested packages: sox mpeg2dec a52dec The following NEW packages will be installed: avidemux avidemux-common lame liblame0 libmjpegtools0 libquicktime1 libswscale1d libx264-59 mjpegtools toolame 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 5393kB/5488kB of archives. After this operation, 14.4MB of additional disk space will be used. Do you want to continue [Y/n]? n Abort. gc@basestar:~$ sudo apt-get install avidemux Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: avidemux-common lame liblame0 libmjpegtools0 libquicktime1 libswscale1d libx264-59 mjpegtools toolame Suggested packages: sox mpeg2dec a52dec The following NEW packages will be installed: avidemux avidemux-common lame liblame0 libmjpegtools0 libquicktime1 libswscale1d libx264-59 mjpegtools toolame 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 5393kB/5488kB of archives. After this operation, 14.4MB of additional disk space will be used. Do you want to continue [Y/n]? n Abort. gc@basestar:~$ sudo apt-get install avidemux Reading package lists... Done Building dependency tree... 50% Building dependency tree Reading state information... 0% Reading state information... Done The following extra packages will be installed: avidemux-common lame liblame0 libmjpegtools0 libquicktime1 libswscale1d libx264-59 mjpegtools toolame Suggested packages: sox mpeg2dec a52dec The following NEW packages will be installed: avidemux avidemux-common lame liblame0 libmjpegtools0 libquicktime1 libswscale1d libx264-59 mjpegtools toolame 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 5393kB/5488kB of archives. After this operation, 14.4MB of additional disk space will be used. Get:1 http://debian.yorku.ca lenny/main libquicktime1 2:1.0.2+debian-2 [342kB] Get:2 http://www.debian-multimedia.org lenny/main avidemux-common 1:2.4.1-0.2 [616kB] Get:3 http://debian.yorku.ca lenny/main toolame 02l-6 [97.5kB] 9% [2 avidemux-common 99005/616kB 16%] ^C
I looked at the buglist for aptitude and searched through it for the word "key"(as in keypress) but didn't come up with anything. I found a Debian wiki entry for MacBooks refering to "double keypresses" but it was related to debian-installer (and MacBooks). I have a Gigabyte MA790FX-DS5, Athlon X2 4850e, and 4GB DDR2/800, but I'm reasonably sure this has nothing to do with hardware.
Comment