You misunderstood me or I misunderstood you. But first, it's important to know that each time you login, a new .Xauthority is created, that's why an old one didn't work.
Second, I thought you couldn't get a GUI going in root after logging is a user (who the GUI did work for). If I'm correct about that, then login as a user and verify that the user's GUI works. If that user has a working GUI, then you're almost there. Copy the .Xauthority from the logged in user's home directory (the date and time stamp should coincide with the login time) to the home directory of root--most likely /root or /--look for the hidden bash login and history files if you're not sure. Hope that helps! On Wed, Oct 28, 2009 at 1:16 PM, pete b. <[email protected]> wrote: > I tried copying the remote .Xauthority to the local and then the following > command: > > \ssh -X -p8080 -vvv p...@remotehost 'evince' 2>/tmp/ssh.log > > The result was the same as I list in the Oct 13 posting. > > > On Wed, Oct 14, 2009 at 6:50 PM, Blues Renegade > <[email protected]>wrote: > >> After you login remotely, are you changing user and then trying to run >> X11? I've had that same problem before where it worked for the client I >> logged in as, but as soon as I su-ed to any other user (usually su - to >> root), then the su login got display errors (screen not found, etc.). >> >> As someone else suggested, the problem was with .Xauthenticity (not where >> I can look up the exact name at the moment, but it's a hidden file in the >> login user's home directory). >> >> I copied that .Xauthen (whatever the exact name is...) to the login user's >> home directory and then when I su-ed to that account the GUI apps worked as >> expected. >> >> ** NOTE ** The .Xauthenticity (name?) file is created on each remote >> login. Therefore, each time you login you'll have to replace the .Xauth file >> in the home dir of account you're su-ing into with .Xauth file from the home >> dir of the remote user's current login (or make a one-line cp script to do >> it for you). >> >> John >> >> >> >> On Tue, Oct 13, 2009 at 10:39 AM, pete b. <[email protected]> wrote: >> >>> Based on your suggestions I tried both: >>> \ssh -X -vvv p...@remotehost -p8080 'evince' 2>/tmp/ssh.log >>> >>> and >>> >>> \ssh -X -p8080 -vvv p...@remotehost 'evince' 2>/tmp/ssh.log >>> >>> Each of these did not display the evince GUI and returned the following: >>> grep -i -e x11 -e port /tmp/ssh.log >>> Hmm, for some reason port 8080 is not recognized. >>> >>> ------------------------------------------------------------------------------------------- >>> >>> debug1: Connecting to remotehost [remotehost] port 8080. >>> debug3: put_host_port: [remotehost]:8080 >>> debug3: put_host_port: [remotehost]:8080 >>> debug2: x11_get_proto: /usr/bin/xauth list remotehost:0.0 2>/dev/null >>> Warning: No xauth data; using fake authentication data for X11 >>> forwarding. >>> >>> debug1: Requesting X11 forwarding with authentication spoofing. >>> debug2: channel 0: request x11-req confirm 0 >>> debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384 >>> debug1: client_request_x11: request from 127.0.0.1 41008 >>> debug2: connect remotehost port 6000: No route to host >>> connect remotehost port 6000: No route to host >>> debug1: failure x11 >>> >>> >>> ------------------------------------------------------------------------------------------- >>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup -~----------~----~----~----~------~----~------~--~---
