Hello
i have a problem on CentOS 4 with starting remote x application on
remote CentOS 3 od Solaris 9 boxes.
The problem is: When I run it from CentOS 3 it's OK form CentOS 4 I
cannot find a bad word in logs ...
My local machine
stoping firewall
[root at klima-pc ~]# service iptables stop
[root at klima-pc ~]# iptables-save
[root at klima-pc ~]#
SELinux is OFF
I am connecting by ssh with Xforwarding enabled to
- Centos 3 box
[09:32 root at tux:root]# gvim --sync
The program 'gvim' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
(Details: serial 287 error_code 5 request_code 20 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
[09:33 root at tux:root]#
-Solaris 9 box
root at sun bin# gvim --sync
Gdk-ERROR **: BadAtom (invalid Atom parameter)
serial 364 error_code 5 request_code 20 minor_code 0
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
serial 365 error_code 10 request_code 102 minor_code 0
root at sun bin#
Hello
i have a problem on CentOS 4 with starting remote x application on
remote CentOS 3 od Solaris 9 boxes.
The problem is: When I run it from CentOS 3 it's OK form CentOS 4 I
cannot find a bad word in logs ...
My local machine
stoping firewall
[root at klima-pc ~]# service iptables stop
[root at klima-pc ~]# iptables-save
[root at klima-pc ~]#
SELinux is OFF
I am connecting by ssh with Xforwarding enabled to
- Centos 3 box
[09:32 root at tux:root]# gvim --sync
The program 'gvim' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
(Details: serial 287 error_code 5 request_code 20 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
[09:33 root at tux:root]#
-Solaris 9 box
root at sun bin# gvim --sync
Gdk-ERROR **: BadAtom (invalid Atom parameter)
serial 364 error_code 5 request_code 20 minor_code 0
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
serial 365 error_code 10 request_code 102 minor_code 0
root at sun bin#
On Tue, 2005-05-03 at 11:05 +0200, Petr Kl?ma wrote:> Hello > > i have a problem on CentOS 4 with starting remote x application on > remote CentOS 3 od Solaris 9 boxes. > > The problem is: When I run it from CentOS 3 it's OK form CentOS 4 I > cannot find a bad word in logs ... > > > My local machine > > stoping firewall > [root at klima-pc ~]# service iptables stop > [root at klima-pc ~]# iptables-save > [root at klima-pc ~]# > > SELinux is OFF > > > I am connecting by ssh with Xforwarding enabled to > - Centos 3 box > > [09:32 root at tux:root]# gvim --sync > The program 'gvim' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadAtom (invalid Atom parameter)'. > (Details: serial 287 error_code 5 request_code 20 minor_code 0) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() > function.) > [09:33 root at tux:root]# > > > -Solaris 9 box > root at sun bin# gvim --sync > Gdk-ERROR **: BadAtom (invalid Atom parameter) > serial 364 error_code 5 request_code 20 minor_code 0 > Gdk-ERROR **: BadAccess (attempt to access private resource denied) > serial 365 error_code 10 request_code 102 minor_code 0 > root at sun bin#It is a feature ... really, it is (according to RH) :). Here is a quote from the RH mailing list: --------------------- I think by default X11Forwading is now disabled in SSH. You can either use 'ssh -X' or change it in your /etc/ssh/ssh_config. I have the following in mine: ForwardX11 yes ForwardX11Trusted yes -------------------- That should make it work the way you expect. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20050503/10da4318/attachment-0005.sig>
> It is a feature ... really, it is (according to RH) :). Here is a quote > from the RH mailing list: > > --------------------- > I think by default X11Forwading is now disabled in SSH. You can either > use 'ssh -X' or change it in your /etc/ssh/ssh_config. I have the > following in mine: > > ForwardX11 yes > ForwardX11Trusted yes > -------------------- > > That should make it work the way you expect. > >YES YES YES by default ForwardX11 yes ForwardAgent yes ForwardX11Trusted no so you have to change to ForwardX11Trusted yes and voila it works Thank you Petr Kl?ma JIHOMILK a.s. Rudolfovsk? 246/83 370 50 ?esk? Bud?jovice Czech Rpublic phone: +420 389 136 209 e-mail: petr.klima at jihomilk.cz
On Tuesday 03 May 2005 06:28, Johnny Hughes wrote:> On Tue, 2005-05-03 at 11:05 +0200, Petr Kl?ma wrote: > > i have a problem on CentOS 4 with starting remote x application on > > remote CentOS 3 od Solaris 9 boxes.> > The problem is: When I run it from CentOS 3 it's OK form CentOS 4 I > > cannot find a bad word in logs ... > --------------------- > I think by default X11Forwading is now disabled in SSH. You can either > use 'ssh -X' or change it in your /etc/ssh/ssh_config. I have the > following in mine:> ForwardX11 yes > ForwardX11Trusted yes > --------------------> That should make it work the way you expect.Or use ssh -Y. Recent Cygwin is the same; in fact, any recent SSH; it's not Red Hat's fault, it's upstream. -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu
"JH" == Johnny Hughes <mailing-lists at hughesjr.com>
JH> It is a feature ... really, it is (according to RH) :).
JH> Here is a quote from the RH mailing list:
RHML> I think by default X11Forwading is now disabled in
RHML> SSH. You can either use 'ssh -X' or change it in your
RHML> /etc/ssh/ssh_config. I have the following in mine:
RHML> ForwardX11 yes
RHML> ForwardX11Trusted yes
JH> That should make it work the way you expect.
Cool, cool, cool. This problem burned me a week or so ago. I
figured out the ForwardX11 change, but I was too busy with the end
of the semester to look into it any more than that, so never had a
clue about ForwardX11Trusted.
Luckily, the problem didn't seem to affect my Mac, so I've been
using that as my main system. Until the start of this week, when
I started having the same problems with X on my Mac after
upgrading to Tiger, which was a pretty big clue, but I still
wasn't sure exactly where the problem was.
Johnny probably should have stressed that you need to add the
ForwardX11 and ForwardX11Trusted keys on your client machine (the
machine your X server is running on). Knowing about the -Y flag
is also a Good Thing.
Thanks!
Claire
--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Claire Connelly cmc at math.hmc.edu
Systems Administrator (909) 621-8754
Department of Mathematics Harvey Mudd College
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20050504/979bf996/attachment-0004.sig>