F3 in bash running under gnome-terminal causes loop

Running strace against the bash process yields:

rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0

repeated over and over again.

thanks for reporting! as this bug lay around stale for some time i dare to ask if it still bothering you?

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Sorry, I didn't get your previous comment from 2008/6/24. But I got this last email. I don't know how to reopen this bug report -- can you do that or let me know how?

Yes, this still happens. It's hard for me to find a terminal window where this doesn't occur. I start my terminal windows by calling /usr/bin/gnome-terminal with a title (-t) and a geometry (--geometry). I managed to get one terminal window into a state where it DID NOT produce this behavior. I ran stty sane in both terminal windows (one window which reproduces this behavior, one which doesn't). Then I ran strace and captured what's going on when I press F3, followed by ctl-c. I've attached the outputs. There are 4 attachments in one tar ball:

good_f3 (strace of F3 in the terminal which DOES NOT produce this behavior)
good_ctl_c (strace of ctl-c in the terminal which DOES NOT produce this behavior)
good_f3_ctl_c (strace of F3 followed by ctl-c in the terminal which DOES NOT produce this behavior)
bad_f3_ctl_c (strace of F3 followed by ctl-c in the terminal which DOES produce this behavior)

Unfortunately, I don't know how I got the "good" terminal in the state where it doesn't produce this behavior.

reopened it for you. but if this bug is not marked as affecting any package (bash, gnome-terminal, ... i am not sure why is/might be the culprit) it is very unlikely that some real developer will have a look at it...

Thanks, Michael. Yes, this definitely affects bash. I didn't know you had to choose a package. It also affects gnome-terminal.

Is this symptom still reproducible in 8.10 or 9.04?

No, it appears to have gone away. I just did some more experimenting and found an easy way to reproduce it in 7.10:

1) boot from CD (to get a fresh installation of 7.10)
2) add System Monitor to panel, in order to be able to see the 100% use of one CPU
3) open a Terminal (Accessories->Terminal)
4) in the Terminal window, type: set -o vi <Enter>
4) hit F3
5) watch the System Monitor to see that one CPU has just been maxed at 100%
6) hit Ctrl-C to return bash to normal behavior
7) notice that the System Monitor shows that usage has dropped back down

I booted from 8.04 and 8.10 and was not able to reproduce it with these same instructions, so it looks like it's gone away. Maybe it's worth reporting upstream to bash or fixing in 7.10?

i am closing this bug, as the bug has been fixed in recent versions and i do not think it is going to be backported.