[arch-general] X11 forwarding: X Error: BadAccess (attempt to access private resource denied) 10
Guys,
I'm trying to use x11 forwarding and from my arch laptop and I can't run X apps from my arch server. I know this has to do with the MIT-MAGIC-COOKIE-1 or something similar, but I can't remember what we did to fix this last time. What's the trick to get it going?? ICEauthority? pam entry?
can you post the exact terminal commands that you are using?
On Tue, Jul 20, 2010 at 11:48 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
Guys,
I'm trying to use x11 forwarding and from my arch laptop and I can'trun X apps from my arch server. I know this has to do with the MIT-MAGIC-COOKIE-1 or something similar, but I can't remember what we did to fix this last time. What's the trick to get it going?? ICEauthority? pam entry?
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 07/21/2010 12:08 AM, Jeffrey Lynn Parke Jr. wrote:
can you post the exact terminal commands that you are using?
Sure, sorry:
From my laptop, I use:
ssh -X nirvana.3111skyline.com
to ssh into my arch server (nirvana). In that same terminal, I then want to start X apps on supersff by using for example
/opt/kde/bin/kate &
to have kate from the server appear on my laptop. Works fine. Also for config purposes, I su on nirvana to start kate to manage the apache configs, etc. Instead of starting the X app and having it show up on my laptop, all I get is:
04:19 alchemy:~> snv Last login: Wed Jul 21 00:30:35 2010 from zephyr.3111skyline.com 04:23 nirvana:~> /opt/kde/bin/kate & [1] 2309 04:24 nirvana:~> X Error: BadAccess (attempt to access private resource denied) 10 Major opcode: 18 Minor opcode: 0 Resource id: 0x6e
[1]+ Segmentation fault /opt/kde/bin/kate
Strangely enough, I can use gedit on this box so it appears to be a kde3 issue (environment?) Here is the output I get on running gedit:
04:24 nirvana:~> /usr/bin/gedit & [1] 2321 You have mail in /var/mail/david 04:24 nirvana:~> Xlib: extension "RANDR" missing on display "localhost:10.0". ** Message: pygobject_register_sinkfunc is deprecated (GtkWindow) ** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible) ** Message: pygobject_register_sinkfunc is deprecated (GtkObject)
[1]+ Done /usr/bin/gedit
Lastly, I have another arch box named supersff. When I attempt either kate or gedit there, I get a can't open display error
04:27 alchemy:~> sff Last login: Fri Jul 16 20:28:39 2010 from zephyr.3111skyline.com 04:30 supersff:~> /opt/kde/bin/kate & [1] 1410 04:30 supersff:~> kate: cannot connect to X server
[1]+ Exit 1 /opt/kde/bin/kate 04:31 supersff:~> gedit & [1] 1411 04:32 supersff:~> (gedit:1411): Gtk-WARNING **: cannot open display:
[1]+ Exit 1 gedit
I can't recall if I have to set display somewhere or just what we did to get this working.
Thanks.
On 07/21/2010 10:38 AM, David C. Rankin wrote:
On 07/21/2010 12:08 AM, Jeffrey Lynn Parke Jr. wrote:
can you post the exact terminal commands that you are using?
Sure, sorry:
From my laptop, I use:ssh -X nirvana.3111skyline.com
to ssh into my arch server (nirvana). In that same terminal, I then want to start X apps on supersff by using for example
The only thing I can remember is to try:
ssh -XY nirvana.3111skyline.com
I usually use it with -XY because just -X or -Y (which should imply -X I guess) don't seem to work very well sometimes.
On 07/21/2010 05:55 AM, Mauro Santos wrote:
The only thing I can remember is to try:
ssh -XY nirvana.3111skyline.com
I usually use it with -XY because just -X or -Y (which should imply -X I guess) don't seem to work very well sometimes.
Thanks Mauro,
For some reason, I recall copying some magic-cookie or maybe ICEAuthority from one box to the other. I wish I could find my notes. I'll google a bit more. If you think of anything else, let me know :)
On 07/21/2010 03:49 PM, David C. Rankin wrote:
On 07/21/2010 05:55 AM, Mauro Santos wrote:
The only thing I can remember is to try:
ssh -XY nirvana.3111skyline.com
I usually use it with -XY because just -X or -Y (which should imply -X I guess) don't seem to work very well sometimes.
Thanks Mauro,
For some reason, I recall copying some magic-cookie or maybeICEAuthority from one box to the other. I wish I could find my notes. I'll google a bit more. If you think of anything else, let me know :)
Try doing:
xhost + local: or xhost +
but I doubt that will solve the problem. The only thing that usually is needed is for the remote machine to have a ~/.Xauthority file, which is created when you run X or use ssh -X. No other ideas here.
Your other option is to run a vnc server, although for local networks x forwarding works great, a vnc server allows one to keep gui apps running and sometimes that is really handy.
On 21-07-10 18:59, Mauro Santos wrote:
On 07/21/2010 03:49 PM, David C. Rankin wrote:
[...]
For some reason, I recall copying some magic-cookie or maybeICEAuthority from one box to the other. I wish I could find my notes. I'll google a bit more. If you think of anything else, let me know :)
Try doing:
xhost + local: or xhost +
but I doubt that will solve the problem. The only thing that usually is needed is for the remote machine to have a ~/.Xauthority file, which is created when you run X or use ssh -X. No other ideas here.
Well, ssh creates the ~/.Xauthority file, you could try setting the XAUTHORITY variable after su-ing to root. So: XAUTHORITY=~USER/.Xauthority export XAUTHORITY
and then start your X apps.
mvg, Guus
On 07/22/2010 01:37 PM, Guus Snijders wrote:
On 21-07-10 18:59, Mauro Santos wrote:
On 07/21/2010 03:49 PM, David C. Rankin wrote:
[...]
For some reason, I recall copying some magic-cookie or maybe ICEAuthority from one box to the other. I wish I could find my notes. I'll google a bit more. If you think of anything else, let me know :)
Try doing:
xhost + local: or xhost +
but I doubt that will solve the problem. The only thing that usually is needed is for the remote machine to have a ~/.Xauthority file, which is created when you run X or use ssh -X. No other ideas here.
Well, ssh creates the ~/.Xauthority file, you could try setting the XAUTHORITY variable after su-ing to root. So: XAUTHORITY=~USER/.Xauthority export XAUTHORITY
and then start your X apps.
mvg, Guus
Guys,
Here may be something that will help. On my suse box, I can use x11 forwarding without any problem at all. When the connection is slow, I see a small xterm flash with the title 'xdg su' just before the X application starts. Maybe that will jog a memory or two.
Since I have both OS's to compare -- which files are involved in handling the authentication for x forwarding? I'll do a side-by-side comparison and report back if I can figure out which files to compare -- thanks.
Try doing:
xhost + local: or xhost +
Please don't do that!
Well, ssh creates the ~/.Xauthority file, you could try setting the XAUTHORITY variable after su-ing to root. So: XAUTHORITY=~USER/.Xauthority export XAUTHORITY
that's not needed either.
Here may be something that will help. On my suse box, I can use x11 forwarding without any problem at all. When the connection is slow, I see a small xterm flash with the title 'xdg su' just before the X application starts. Maybe that will jog a memory or two.
Since I have both OS's to compare -- which files are involved in handling the authentication for x forwarding? I'll do a side-by-side comparison and report back if I can figure out which files to compare -- thanks.
Check that X11Forwarding is set to yes on the ssh *server*
also check "man sshd" there's a discussion if you have a ~/.ssh/rc or /etc/ssh/sshrc executable file
participants (5)
-
Damjan Georgievski
-
David C. Rankin
-
Guus Snijders
-
Jeffrey Lynn Parke Jr.
-
Mauro Santos