Results 1 to 7 of 7

Thread: Problem with vncserver running Kali 2019.2 arm32 bit.

  1. #1
    Join Date
    2019-Jul
    Posts
    3

    Problem with vncserver running Kali 2019.2 arm32 bit.

    I dont know if i post this in the right subforum, if not can you move it to the right place


    Hi, I need some help. Im trying to get the VNC connection to work, but for some reason I cant figure out what to go from here, what have i forgot? Nothing modded or changed from ISO file except a password for vncserver from first run.

    I need 2 things, really, first one is to actually got it started, secondly how to add it to update-rc.d.

    Im using vncserver thats preinstalled from ISO
    Kali 2019.2 ARM 32bit Using Paspberry Pi with HDMI

    Mad76e@kali:~# vncserver
    Couldn't start Xtightvnc; trying default font path.
    Please set correct fontPath in the vncserver script.
    Couldn't start Xtightvnc process.
    02/07/19 17:38:10 Xvnc version TightVNC-1.3.9
    02/07/19 17:38:10 Copyright (C) 2000-2007 TightVNC Group
    02/07/19 17:38:10 Copyright (C) 1999 AT&T Laboratories Cambridge
    02/07/19 17:38:10 All Rights Reserved.
    02/07/19 17:38:10 See http://www.tightvnc.com/ for information on TightVNC
    02/07/19 17:38:10 Desktop name 'X' (kali:1)
    02/07/19 17:38:10 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
    02/07/19 17:38:10 Listening for VNC connections on TCP port 5901

    Fatal server error:
    could not open default font 'fixed'
    02/07/19 17:38:11 Xvnc version TightVNC-1.3.9
    02/07/19 17:38:11 Copyright (C) 2000-2007 TightVNC Group
    02/07/19 17:38:11 Copyright (C) 1999 AT&T Laboratories Cambridge
    02/07/19 17:38:11 All Rights Reserved.
    02/07/19 17:38:11 See http://www.tightvnc.com/ for information on TightVNC
    02/07/19 17:38:11 Desktop name 'X' (kali:1)
    02/07/19 17:38:11 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
    02/07/19 17:38:11 Listening for VNC connections on TCP port 5901
    Font directory '/usr/share/fonts/X11/Speedo/' not found - ignoring

    Fatal server error:
    could not open default font 'fixed'
    Mad76e@kali:~#
    And when I tried from the client (realvnc client on win10) the connection was refused
    Last edited by Smnfz; 1 Week Ago at 11:40.

  2. #2
    Join Date
    2019-Jul
    Posts
    3
    Same issue with the kali nethunter . How to remove this font error Font directory '/usr/share/fonts/X11/Speedo/' not found - ignoring

  3. #3
    Join Date
    2015-Nov
    Location
    Australia
    Posts
    234

    Lightbulb Fix for vnc error: "could not open default font 'fixed'"

    This will fix it:

    Code:
    dpkg-reconfigure xfonts-base
    ----------------------------------------
    https://re4son-kernel.com
    - - - - - - - - - - - - - - - - - - - - - -
    Check out "Sticky Fingers Kali-Pi":
    https://re4son.com/kali-pi

    Now with mana-toolkit and more goodies!

  4. #4
    Join Date
    2019-Jul
    Posts
    3
    Thanks it got fixed the error

  5. #5
    Join Date
    2019-Jul
    Posts
    3
    It did, I have a session, and i can connect to it, however i do have more problems


    So, it seems that i suffer from the same issue as many other. The grey empty window with a cursor. However my session dont crashes Is there a way around this?


    "vncserver" in terminal gave me a grey session when running the client
    "vncserver -geometry 1024x768" did also give me a grey session
    Modifying "xstartup" in /root/.vnc/ did give me a terminal window (removed # on x-terminal line, just to check that it works)

    content in xstartup

    #!/bin/sh

    xrdb $HOME/.Xresources
    xsetroot -solid grey
    # x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
    # x-window-manager &
    # Fix to make GNOME work
    export XKL_XMODMAP_DISABLE=1
    /etc/X11/Xsession
    content in logfile Kali1.log
    04/07/19 14:23:46 Xvnc version TightVNC-1.3.9
    04/07/19 14:23:46 Copyright (C) 2000-2007 TightVNC Group
    04/07/19 14:23:46 Copyright (C) 1999 AT&T Laboratories Cambridge
    04/07/19 14:23:46 All Rights Reserved.
    04/07/19 14:23:46 See http://www.tightvnc.com/ for information on TightVNC
    04/07/19 14:23:46 Desktop name 'X' (kali:1)
    04/07/19 14:23:46 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
    04/07/19 14:23:46 Listening for VNC connections on TCP port 5901
    xrdb: No such file or directory
    xrdb: can't open file '/root/.Xresources'

    04/07/19 14:23:59 Got connection from client 192.168.1.159
    04/07/19 14:23:59 Using protocol version 3.8
    04/07/19 14:24:03 Full-control authentication passed by 192.168.1.159
    04/07/19 14:24:03 rfbProcessClientNormalMessage: ignoring unknown encoding 24
    04/07/19 14:24:03 rfbProcessClientNormalMessage: ignoring unknown encoding 15
    04/07/19 14:24:03 Using hextile encoding for client 192.168.1.159
    04/07/19 14:24:03 rfbProcessClientNormalMessage: ignoring unknown encoding 16
    04/07/19 14:24:03 rfbProcessClientNormalMessage: ignoring unknown encoding 22
    04/07/19 14:24:03 rfbProcessClientNormalMessage: ignoring unknown encoding 21
    04/07/19 14:24:03 rfbProcessClientNormalMessage: ignoring unknown encoding -314
    04/07/19 14:24:03 Enabling full-color cursor updates for client 192.168.1.159
    04/07/19 14:24:03 rfbProcessClientNormalMessage: ignoring unknown encoding -223
    04/07/19 14:24:03 Pixel format for client 192.168.1.159:
    04/07/19 14:24:03 32 bpp, depth 24, little endian
    04/07/19 14:24:03 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
    04/07/19 14:24:03 no translation needed
    04/07/19 14:24:11 Client 192.168.1.159 gone
    04/07/19 14:24:11 Statistics:
    04/07/19 14:24:11 key events received 0, pointer events 59
    04/07/19 14:24:11 framebuffer updates 1, rectangles 2, bytes 4156
    04/07/19 14:24:11 cursor shape updates 1, bytes 1068
    04/07/19 14:24:11 hextile rectangles 1, bytes 3088
    04/07/19 14:24:11 raw bytes equivalent 3145740, compression ratio 1018.698187
    pic from client

    https://i.imgur.com/PiFURZr.png

  6. #6
    Join Date
    2015-Nov
    Location
    Australia
    Posts
    234
    Try this xstartup:

    https://github.com/Re4son/RPi-Tweaks...rvice/xstartup

    That should do the trick
    ----------------------------------------
    https://re4son-kernel.com
    - - - - - - - - - - - - - - - - - - - - - -
    Check out "Sticky Fingers Kali-Pi":
    https://re4son.com/kali-pi

    Now with mana-toolkit and more goodies!

  7. #7
    Join Date
    2019-Jul
    Posts
    3
    Thanks, that worked perfectly!

Similar Threads

  1. Reaver/Bully problem. Kali problem? backports problems?
    By kaputjan in forum General Archive
    Replies: 2
    Last Post: 2017-04-28, 17:48

Posting Permissions

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