Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 Description of problem: the help browser (yelp) popup when I type "gre" fast on the terminal. Can't explain why? and its really anonying! somehow it seems that the string "gre" is connected to the F1 button? I have this problem on every gnome app. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.open up a gnome-terminal 2.type "gre" fast. 3. Actual Results: help browser pops up Expected Results: nothing Additional info:
There is just no way. ;-) Do you have a laptop where the function keys are alternates on the main keys for example? Maybe you somehow changed the keybinding for help in gnome-terminal->Edit->Keybindings so it isn't F1 anymore?
Yeah, I have a laptop.. compaq evo n600c and now I have disabled the F1 button for the help browser. and now when I type "gre" it adds "p" and I get a beep through the speaker?! It´s really strange! Im going mad! Observe!, Its in every gnome app. not just the gnome-terminal.. but not in anything else.. maybe something with "stty" or something? I ran redhat 7.3 before without problem.. I got this prob. when upgrading to RH8. [wmdljo@xxxxx wmdljo]$ grep grepp grpep grep grpep grpep grep [wmdljo@xxxxx wmdljo]$ stty -a speed 38400 baud; rows 24; columns 80; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke
I´ve fixed it! If I enabled the "Bounce keys" and set the value to 10 msec this strange problem stopped buggin me. I Dont really know what it does, but now it works?! I guess its just a workaround.. Or I have some strange keyboard error..?!
It's quite possible you had just turned on some of the accessibility features. Those do cause some funky keyboard behavior if you aren't expecting it.