> > > > Make sure you read the FC3 release notes on ssh [try: ssh -Y] before > > assuming its a bug. > > And make sure you have the most up2date openssh RPMs. The > -X/-Y issue is > addressed by yesterday's update. > Turns out the issue was related to -Y, turning on -Y or setting it in .ssh/config fixed the problem. The problem was not however obvious from the release notes. The application could request the atom number for a given resource. When it tried to read the resource, it would work if the atom number was below a certain value. The value happened to always correspond to resource XFree86_VT (atom number varied with each X restart). Resources with atom numbers greater than or equal to XFree86_VT would get an invalid atom error. This would kill applications such as ddd and any others that used atoms beyond that magic value. Doing a direct displayback (after -nolisten was turned off) worked fine. This is why I suspected an ssh issue. Thanks for the pointer in the right direction. Robert E. Styma Principal Engineer (DMTS) Lucent Technologies, Phoenix Email: stymar@xxxxxxxxxx / styma@xxxxxxxxxx Phone: 623-582-7323 Company: http://www.lucent.com Personal: http://www.swlink.net/~styma
