The best Server

[Rashkae]

NoOp wrote:
> On 07/09/2008 04:33 PM, Rashkae wrote:
>> Oh, I see what you did here... Sorry for my earlier responses.  I've
>> somehow failed at reading comprehension. (just don't call me Karl, k?)
>>
>> You do not need to, nor should you, run startx on the remote computer.
>> For any X application to work, including gedit, you need to have
>> "Xserver" running on the computer that will display the application.
>> This is confusing, as it flips terminology around.  Xserver needs to run
>> on the "Client" computer, not the Server computer.. got it?  The
>> application that runs on the application server, like gedit, is called a
>> client application..... (don't look at me, this terminology was invented
>> by egg heads in the 70's.)
>>
>>
> 
> The startx was from the ssh -X session. So I've rebooted the server, now
> login using 'ssh -X username at serverIP:
> 
> clientmachineusername at clientmachine:~$ ssh -X serverusername at serverIP
> clientmachineusername at clientmachine's password:
> Linux userver 2.6.24-19-server #1 SMP Wed Jun 18 15:18:00 UTC 2008 i686
> 
> The programs included with the Ubuntu system are free software;
> the exact distribution terms for each program are described in the
> individual files in /usr/share/doc/*/copyright.
> 
> Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
> applicable law.
> 
> To access official Ubuntu documentation, please visit:
> http://help.ubuntu.com/
> Last login: Wed Jul  9 16:14:47 2008 from 192.168.4.100
> ggserver2 at userver:~$
> 
> ggserver2 at userver:~$ sudo gedit
> [sudo] password for ggserver2:
> The program 'gedit' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAccess (attempt to access private resource denied)'.
>   (Details: serial 188 error_code 10 request_code 145 minor_code 5)
>   (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.)
> 
> Now the odd part is that if I issue the 'sudo gedit' command again it
> works. Ditto for 'gksu gedit' etc. So you are right that I don't have to
> do 'startx'. Odd that it didn't take on the first attempt - maybe it's a
> timing issue?
> 

Just for kicks, try turning off the "Desktop Effects" on the client
before you ssh into the server and try this again that way.