Results 1 to 3 of 3

Thread: 11.4/KDE4.7.1 VNC crash after recent update - a fix here

  1. #1
    Join Date
    Jun 2008
    Location
    Florida, USA
    Posts
    974

    Default 11.4/KDE4.7.1 VNC crash after recent update - a fix here

    I am running 11.4_64/KDE 4.7.1 on a remote desktop and connect via vncviewer from another 11.4 system.
    Was working well. I have it setup following Swerdna's guide here

    After a recent update(Yast-software Management), I was unable to access the VNC server.
    When I logged into the remote via cli and ssh, looking in ~/.vnc/server.log, I could see a string of issues with akondai crashing and ultimately the vnc server shutting down.

    With nothing obvious on the 'net or on the Forum, I looked for an updated package and found xorg-x11-Xvnc-7.6_1.10.4-166.10.x86_64.rpm in the repo http://X11:Org/openSUSE_11.4 searching the Suse Package site.
    It is slightly newer than the version in the standard repos.

    I manually downloaded the rpm, installed with Yast, and VNC now works again.

  2. #2

    Default Re: 11.4/KDE4.7.1 VNC crash after recent update - a fix here (IPv6 hosts entries to blame)

    I had to remove all the ipV6 entries in /etc/hosts... (openSuse11.4 w/ KDE 4)

    Removed these lines from "/etc/hosts"
    # special IPv6 addresses
    ::1 localhost ipv6-localhost ipv6-loopback

    fe00::0 ipv6-localnet

    ff00::0 ipv6-mcastprefix
    ff02::1 ipv6-allnodes
    ff02::2 ipv6-allrouters
    ff02::3 ipv6-allhosts


    I tried upgrading to the latest version of X-vnc, but that did not work... I could not find a log file for the Desktop Sharing (VNC) in KDE, so I can't tell what was happening. Anyone know if/where this service logs it's data? I would think xinetd, but it's not very verbose (just connect log)

  3. #3
    Join Date
    Jun 2008
    Location
    Florida, USA
    Posts
    974

    Default Re: 11.4/KDE4.7.1 VNC crash after recent update - a fix here (IPv6 hosts entries to blame)

    Are you following Swerdna's guide (post #1)?

    That does not use xinet.d service setup.

    The log for the vncserver should be found in /home/username/.vnc/server.log, username = user that started vncserver.

    Is the vncserver process running on the host?

    Look at
    Code:
    ps -A |grep vncserver
    When I could not see it running, realized it had crashed on startup (in server.log)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •