Bug 187961

I have never seen the first error you mention above. Could you please attach
output from the client when run with -vvv option when the problem happens?
Eventually you could also run the server with -ddd option and attach its output too.

I can occasionally reproduce the second problem however I was never able to
reproduce it when running the client with -vvv options.

I agree that this is really annoying problem but without reproducer it's almost
impossible to fix it.

Also you could try to reproduce it with vanilla openssh compiled yourself and
report it upstream in http://bugzilla.mindrot.org/ if you still can reproduce it.

Created attachment 127379 [details]
% ssh tigger -vvv > /dev/stdout >& ssh-vvv.txt

In this session log (stderr from ssh -vvv, interspersed with some stdout
stuff), I open a ssh session from my x86_64 fc5 machine tigger back to itself.
I then start emacs (emacs-21.4-14), the window opens with just the scratch
buffer, I click once on the window and try to paint the default "This buffer is
for notes..." text.
This causes emacs to fail every time with the BadWindow message found in the
log.
I'm beginning to suspect this is actually a X issue?

Created attachment 127380 [details]
% ssh tigger -vvv > /dev/stdout >& ssh-vvv.txt

In this session log (stderr from ssh -vvv, interspersed with some stdout
stuff), I open a ssh session from my x86_64 fc5 machine tigger back to itself.
I then start emacs (emacs-21.4-14), the window opens with just the scratch
buffer, I click once on the window and try to paint the default "This buffer is
for notes..." text.
This causes emacs to fail every time with the BadWindow message found in the
log.
I'm beginning to suspect this is actually a X issue?

At this time, after the usual fc5 updates, the above error no longer happens!
Wonderful! I think the new xorg-x11 release for x86_64 has fixed this.