This problem again for me. Seems to happen with every version! I have the same problem as my last thread. Basically it was solved by removing an IPv6 line from the hosts file or adjusting the vnc configuration to use an IP and not host name. Both of these are not working for me on 11.3. I’m not seeing any errors in log/messages. It just sits there with an X cursor that moves around then times out after around a minute or so. I don’t know if there are any other logs that will help.
To clarify, starting a vncserver from a terminal will work, but the ‘Remote administration’ vnc with the login screen will produce a fully black screen with an X cursor that updates with my mouse position.
Same issue here on two different boxes. I thought it was screen resolution to start, but my last box was setup with 800x600 resolution, which would have resolved that problem. In addition, I didn’t even install Desktop Effects (just for testing). Same issue.
I thought it was just me from doing something else. I just reinstalled 11.3 today and again same problem. I spent a couple hours just going around looking for possible solutions, reinstalling, verifying firewall, hosts file, setting a hard IP instead of localhost, verifying policies etc. No luck. That and the fact that Firefox java doesnt work out of the box kinda got to me.
I too had the same problem with the black screen and X cursor for the Remote Administration VNC Server. It was cured exactly the same way as per my post for Suse 11.2 here:
No much info is given, worst is that it seems to be no error, but I only see the black window with the X.
I installed 11.3 today, clear install from a 11.1 version working without problems.
I´m looking into gdm now, but any help will be appreciated.
I had the same in my logs. I do remember now that I stumbled accross that log. Mine would always time out at 126 seconds or something around there (maybe 129 like yours)
No that did not help. Like I said earlier I commented out the ipv6 line, and even replaced localhost with the loopback ip (in the xinet.d vnc conf). Thanks for the suggestion though.
Not wishing to waste your time but just to clarify:
you entered ‘ipv4-localhost’ on the back end of the ‘127.0.0.1 localhost’ line to make it an alias and
you changed the VNC line, in the xinedtd list of tasks, to read ‘-query ipv4-localhost’ and you clicked the finish button, to make sure it updates, and
you either opened the port in the firewall or allowed VNC services through or you set your NIC interface to ‘Internal’?
If you did all that I am out if ideas. It must be something else.
Well, i tried with 16 and 24 bits and is the same, I copy the output from the client:
**24 bits**
MBP-2:~ jbuchmann$ vncviewer 10.200.0.200:5901
Connected to RFB server, using protocol version 3.7
Enabling TightVNC protocol extensions
No authentication needed
Desktop name "nobody's x11 desktop (srv02:1)"
VNC server default format:
32 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using default colormap which is TrueColor. Pixel format:
32 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
**16 bits**
MBP-2:~ jbuchmann$ vncviewer 10.200.0.200:5901
Connected to RFB server, using protocol version 3.7
Enabling TightVNC protocol extensions
No authentication needed
Desktop name "nobody's x11 desktop (srv02:1)"
VNC server default format:
16 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0
Using default colormap which is TrueColor. Pixel format:
32 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
As you can see it shows no error, but i only get the black box.
Seems to be some problem with gdm, as im not using KDE.
Next cunning idea: Have you tried doing something rather perverse - displaying a VNC remote desktop on the same machine as the VNC server? The idea being that, if it is a network problem or the server is preventing the display of the logon screen / desktop to a remote client, this would work whilst the normal method would not:
So, whilst logged on locally to your Suse 11.3 VNC server:
