Description of problem:
x11 forwarding via ssh is broken. Some apps like xterm work, but
most don't (including system-config-*)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login to a FC3 box
2. ssh to some remote box (FC1,2,3 or RH9)
3. start (e.g.) system-config-date
Some X11 error (BadWindow with sysstem-config-*, BadAtom with gvim)
window popping up
From a remote administration point of view this is probably the WORST thing you
This is a dup of Bug 141056
Sorry, that should have been bug 134425
As per the FC3 release notes, you must invoke "ssh -Y" in order
to get full X11 forwarding. Please refer to the FC3 release
notes, and the openssh documentation for details.
This is not a bug.
First of all: I did read the relase notes! However, "Some applications may not function properly"
is a joke! The only app which I could find that works is xterm!? But xterm over ssh is as useless
as a fridge at the northpole! So what sense does it makes to change ssh x11 forwarding if
it breaks pretty much everything you want to use it for? If the intention was full customer
dissatisfaction, then you succeeded.
This is a change made by the upstream "openssh" project. I'm not
sure why they made this change, but they did. I also agree it is
a very annoying and inconvenient change, but we ship it as upstream
supplies it currently.
I encourage users who are inconvenienced and upset about this issue
to please discuss it on the fedora mailing lists. I'm no authority
on openssh, or wether we would change the upstream default, however
if any sort of user concensus can be reached on the lists, perhaps
it may weigh in on such a decision.
Thanks for your feedback!
*** This bug has been marked as a duplicate of 137685 ***