VNC Issues

[Vincent Labreche]

Matthew S-H wrote:

> [snip]
>
>> I had the same issue with rebooting my server and discovered in the 
>> setting it is possible to automatically log a user after some idle 
>> time in the session manager. Using this, my vnc server is always on :)
>
> [/snip]
> I don't quite understand what you mean.  Can you please explain?
>
> [snip]
>
>> As for the slowdown, i kinda noticed it too, but it wasn't too 
>> unbearable so i didn't pay attentio to it
>
> [/snip]
> For me the slowdown has been tremendous.  Better than nothing, but not 
> by far.  And I don't seem to know why it is.  Any clues?
>
>
> Anyway, thanks again guys for all of your generous help :).
>
> ~Matt
>
> On Apr 20, 2005, at 12:41 PM, Vincent wrote:
>
>> Matthew S-H wrote:
>>
>>> I have recently been using VNC quite often to access my desktop when 
>>> away.
>>> Recently, I have run into some problems though:
>>>
>>> 1. Speed. Note that this is a NEW issue. Up until a day or two ago, 
>>> I was able to run VNC at a tolerable speed. Now, however, it seems 
>>> to be lagging tremendously. It takes practically forever just to see 
>>> the mouse move. And NO settings were changed on the client. It 
>>> should be noted that I upgraded to Hoary right after the final 
>>> release and that this problem started occurring some time within the 
>>> last week (I have been on a /vacation/ from VNC for the past week). 
>>> This bothers me, however, because I commonly use the computer over VNC.
>>>
>>> 2. Startup. This is a problem I can more easily describe. The VNC 
>>> server doesn't start until I log in. I often-times must reboot my 
>>> computer remotely. After a reboot, I am unable to access the 
>>> computer (graphically--I can still use SSH) until I can physically 
>>> sit in front of the computer and login to GNOME. Is there any way to 
>>> get around this? My ideas (although I don't know how to do them) are 
>>> the following:
>>> a) Modify some startup file to start the VNC server immediately so 
>>> that I can use it to login.
>>> b) Use the command line (via SSH) to either:
>>> b1) Login to GNOME
>>> b2) Start the VNC server
>>>
>>> Note that my temporary solution to this problem has been to set up 
>>> my computer to automatically log me in after 2 minutes. Although 
>>> this works, it is not desirable. i would rather not allow 
>>> unrestricted login to someone without a password, and I would rather 
>>> not wait 2 minutes (which is less of a problem).
>>>
>>>
>>> Anyway, thank you very much for your help. Any and all responses 
>>> will be greatly appreciated.
>>>
>>> ~Matt
>>
>>
>> I had the same issue with rebooting my server and discovered in the 
>> setting it is possible to automatically log a user after some idle 
>> time in the session manager. Using this, my vnc server is always on :)
>>
>> As for the slowdown, i kinda noticed it too, but it wasn't too 
>> unbearable so i didn't pay attentio to it
>>
>> -------------------------------------------
>> Vincent
>>
>> -- 
>> ubuntu-users mailing list
>> ubuntu-users at lists.ubuntu.com
>> http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
>
>
I system/Administration/LoginScreenSetup you can enable "Timed login"
Just click on "Log a user automaticaly after a number of seconds.

I put 30, that way i still can log different users if i acces directly 
the server, but if i do everything remotely, vnc server is always on :)

------------------------------------
Vincent