Results 1 to 5 of 5

Thread: Kali Linux 2.1 ARM Raspberry Pi 1 - TightVNC Grey Screen Trouble

  1. #1
    Join Date
    2016-Mar
    Posts
    10

    Post Kali Linux 2.1 ARM Raspberry Pi 1 - TightVNC Grey Screen Trouble

    Hi everyone

    I just need a bit of help with this, im using a Raspberry Pi 1 with the Kali 2.1 ARM image. Everything has installed ok and i can log in via SSH no problems. I have updated Kali using

    Code:
    apt-get update && apt-get upgrade –y
    I then installed tightvncserver. I ran a server and setup password etc. and when i connect i enter the password and i get a grey weave screen with a black cross mouse pointer. I have tried various different configs for .vnc/xstartup file, but nothing seems to work. Here is the most recent log file.

    Code:
    21/03/16 16:23:17 Xvnc version TightVNC-1.3.9
    21/03/16 16:23:17 Copyright (C) 2000-2007 TightVNC Group
    21/03/16 16:23:17 Copyright (C) 1999 AT&T Laboratories Cambridge
    21/03/16 16:23:17 All Rights Reserved.
    21/03/16 16:23:17 See http://www.tightvnc.com/ for information on TightVNC
    21/03/16 16:23:17 Desktop name 'X' (kali:1)
    21/03/16 16:23:17 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
    21/03/16 16:23:17 Listening for VNC connections on TCP port 5901
    /root/.vnc/xstartup: 5: exec: startgnome: not found
    
    21/03/16 16:23:23 Got connection from client 192.168.0.10
    21/03/16 16:23:23 Using protocol version 3.8
    21/03/16 16:23:34 Full-control authentication passed by 192.168.0.10
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 16
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 22
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 21
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 15
    21/03/16 16:23:34 Using zlib encoding for client 192.168.0.10
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding -314
    21/03/16 16:23:34 Enabling full-color cursor updates for client 192.168.0.10
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding -223
    21/03/16 16:23:34 Pixel format for client 192.168.0.10:
    21/03/16 16:23:34   8 bpp, depth 8
    21/03/16 16:23:34   uses a colour map (not true colour).
    21/03/16 16:23:34 Using raw encoding for client 192.168.0.10
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 22
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 21
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 16
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 15
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding -314
    21/03/16 16:23:34 Enabling full-color cursor updates for client 192.168.0.10
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding -223
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 16
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 22
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 21
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding 15
    21/03/16 16:23:34 Using zlib encoding for client 192.168.0.10
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding -314
    21/03/16 16:23:34 Enabling full-color cursor updates for client 192.168.0.10
    21/03/16 16:23:34 rfbProcessClientNormalMessage: ignoring unknown encoding -223
    21/03/16 16:23:39 Client 192.168.0.10 gone
    21/03/16 16:23:39 Statistics:
    21/03/16 16:23:39   key events received 0, pointer events 50
    21/03/16 16:23:39   framebuffer updates 3, rectangles 27, bytes 20428
    21/03/16 16:23:39     cursor shape updates 3, bytes 900
    21/03/16 16:23:39     raw rectangles 1, bytes 16396
    21/03/16 16:23:39     zlib rectangles 23, bytes 3132
    21/03/16 16:23:39   raw bytes equivalent 761880, compression ratio 39.014748
    and here is the current config for the .vnc/xstartup file.

    Code:
    #!/bin/sh
    
    [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
    #xsetroot -solid grey
    exec startgnome
    I am really stuck on this and can really need some help otherwise im stuck before i even begin to fully use Kali.

    Thanks

  2. #2
    Join Date
    2016-Apr
    Posts
    7
    I'm having the same exact problem with the 2.1.2 build of Kali for Raspberry pi. I'm correctly tunnelling VNC data via SSH, but when I connect I only get a grey screen.

    Really could use some help here...

  3. #3
    Join Date
    2016-Mar
    Posts
    10
    Quote Originally Posted by m0lecule View Post
    I'm having the same exact problem with the 2.1.2 build of Kali for Raspberry pi. I'm correctly tunnelling VNC data via SSH, but when I connect I only get a grey screen.

    Really could use some help here...
    Hi m0lecule

    what i had success with was to find the .vnc/xstartup file.. Im not sure if i appended this to what was already there or replaced, but try both ways and i got it working.

    Code:
    !/bin/sh
    xrdb $HOME/.Xresources
    xsetroot -solid black
    /usr/bin/lxsession -s LXDE &
    Hope this helps.

  4. #4
    Join Date
    2016-Apr
    Posts
    7
    Thanks for the reply. Unfortunately that didn't help.
    This is DEFINITELY a simple problem with the xstartup configuration file. For your info: I don't have lxsession in the /usr/bin directory. From what I can gather I am using the default window manager in Kali 2.1.2 for the Raspberry Pi - which is xfce. If I am not mistaken xfce is also the default window manager for Kali 2.0 and up.

    So essentially we all just need correct xstartup settings that will work with the default window manager in Kali...

  5. #5
    Join Date
    2016-Mar
    Posts
    10
    It has been a while since i got this sorted and cant fully remember.. In the end i stopped using the Pi as it wasnt powerful enough for what i wanted..

    I remember when i was all out of ideas i changed the line

    -solid black
    to
    -solid green

    worth a shot.

Similar Threads

  1. Grey sreen TightVNC Raspberry Pi 3
    By mamutu07 in forum ARM Archive
    Replies: 2
    Last Post: 2016-10-10, 05:46
  2. Replies: 1
    Last Post: 2015-11-30, 08:20
  3. TightVNC grey screen / X-cursor
    By RAFd3v in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2014-05-12, 18:22

Posting Permissions

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