Results 1 to 11 of 11

Thread: Can no longer run tightvncviewer in most current Kali Light armhf image for rpi2/3

  1. #1

    Can no longer run tightvncviewer in most current Kali Light armhf image for rpi2/3

    About a month ago, i loaded an SD card up with the kali-linux-light-2016.2-armhf.img image. I used a tutorial for installing tightvncserver. ( http://www.catonrug.net/2014/05/how-to- ... ry-pi.html )

    I had absolutely no issues whatsoever. This image still works perfectly fine. I made a backup image of this using Win32DiskImager.

    Last week i bought some more SD cards and tried to image my backup image to them. Unfortunately, the cards are not identical and have too many sectors on them to flash to my new cards, even though they are all 16GB. Either way, this is not the issue i am posting about. i know i can get around that at a later point, but it is not a worry to me rigth now. My issue is this:

    I started from scratch using 2 images (one on each card)- kali-linux-light-2016.2-armhf.img and kali-2.1.2-rpi2.img (Kali Full image)

    In both, i am having the same issue. Steps i've done are below:

    with both images, ive imaged the SD card, modified cmdline.txt to assign static IP to pi. SSH into device, and follow tutorial from http://www.catonrug.net/2014/05/how-to- ... ry-pi.html.

    After installing tightvncserver, i try to run tightvncserver, but am returned with "command not found".

    After some googling i decided to run "vncviewer" and i am returned with :

    Code:
    Cleaning stale pidfile '/root/.vnc/kali:1.pid'!
    
    New 'kali:1 (root)' desktop at :1 on machine kali
    
    Starting applications specified in /etc/X11/Xvnc-session
    Log file is /root/.vnc/kali:1.log
    
    Use xtigervncviewer -SecurityTypes VncAuth -passwd /root/.vnc/passwd :1 to connect to the VNC server.

    now, when i try to connect through my tightvncviewer on my win7x64 system, i am greeted with
    "Error in TightVNC Ciewer: No connection could be made because the target machine actively refused it."

    I had seen that error previously about a month ago when i was building the first (working) image, but fixed it quickly by adding :1 to the end of the IP of my kaliPi.

    This is not working now.

    Im not certain that these issues are connected, but i have tinkered with the use of :5901, ::5901, ;1, ::1, and ive also launched vncserver with other session IDs like :2, :5, :9, etc, and still cannot connect. I am at the point of being frustrated enough that i am turning to the forums for help.

    I'd like to get back to using tightvncserver instead of vncserver or tigervncserver. Not sure why there is all of a asudden an issue running tightvncserver.

    Please help!!! Thanks!

  2. #2
    Anybody please help us !!
    I'm also facing same problem

  3. #3
    Quote Originally Posted by yogendrasinghx View Post
    Anybody please help us !!
    I'm also facing same problem
    Was yours also working at some point then facing the issue just as of last few weeks?

  4. #4
    Yeahhh broo it's frustrating now !! still no luck for me ..

  5. #5
    Join Date
    2017-Jan
    Posts
    2
    Hi i have the same issue.

    On the log file it says "ttyname failed: inappropriate ioctl for device"

    Any help please?

  6. #6
    Join Date
    2017-Jan
    Posts
    2
    Hi just to add to the issue. this is the full log output.

    =================== tail -15 /root/.vnc/kali:1.log ===================

    Xvnc TigerVNC 1.7.0 - built Jan 5 2017 22:35:23
    Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt)
    See http://www.tigervnc.org for information on TigerVNC.
    Underlying X server release 11900000, The X.Org Foundation


    Fri Jan 27 23:15:34 2017
    vncext: VNC extension running!
    vncext: Listening for VNC connections on local interface(s), port 5901
    vncext: created VNC server for screen 0
    mesg: ttyname failed: Inappropriate ioctl for device
    XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
    after 173 requests (173 known processed) with 0 events remaining.

    Killing Xtigervnc process ID 897... which seems to be deadlocked. Using SIGKILL!

    ================================================== ====================

    Starting applications specified in /etc/X11/Xvnc-session has failed.

  7. #7
    Join Date
    2015-Aug
    Posts
    16
    I haven't tried this on my pi yet but my last updated broke the ability to use vncviewer from my windows box.

    Running a vnc over an ssh session with the output sent to Xming works fine

    i.e.

    From putty:

    vncserver:1 --localhost true [other options]
    vncviewer 127.0.0.1:1


    I haven't looked into why, but the -SecurityTypes flag on startup is definitely new.
    (I suspect the viewer is outdated and old security was depreciated but I haven't confirmed.)

  8. #8
    Join Date
    2017-Jan
    Posts
    2
    I got the same issue , I was running correctly the vnc a week agobut I had to reinstall for other issue , after that I always got the following issue

    Sun Jan 29 18:29:27 2017
    vncext: VNC extension running!
    vncext: Listening for VNC connections on local interface(s), port 5901
    vncext: created VNC server for screen 0
    mesg: ttyname failed: Inappropriate ioctl for device

    The xstartup file is never created , I tried in 2 different raspberrys without luck .

    any help is appreciated.

  9. #9
    Join Date
    2017-Jan
    Posts
    2
    Tried other options without luck , still getting

    mesg: ttyname failed: Inappropriate ioctl for device
    XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"

  10. #10
    Join Date
    2017-Apr
    Posts
    1

    Solved: Can not run tightvncserver on amdhf image of raspberry pi 2

    Quote Originally Posted by Javier View Post
    Hi just to add to the issue. this is the full log output.

    =================== tail -15 /root/.vnc/kali:1.log ===================

    Xvnc TigerVNC 1.7.0 - built Jan 5 2017 22:35:23
    Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt)
    See http://www.tigervnc.org for information on TigerVNC.
    Underlying X server release 11900000, The X.Org Foundation


    Fri Jan 27 23:15:34 2017
    vncext: VNC extension running!
    vncext: Listening for VNC connections on local interface(s), port 5901
    vncext: created VNC server for screen 0
    mesg: ttyname failed: Inappropriate ioctl for device
    XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
    after 173 requests (173 known processed) with 0 events remaining.

    Killing Xtigervnc process ID 897... which seems to be deadlocked. Using SIGKILL!

    ================================================== ====================

    Starting applications specified in /etc/X11/Xvnc-session has failed.

    I found that in my /etc/X11/Xvnc-session, the last line of the file was a vncserver -kill command.
    I commented that out and my vncserver now works.
    I suspect the exec command is returning after the server initializes and not blocking was desired by the script's author.

  11. #11
    Join Date
    2015-Nov
    Location
    Australia
    Posts
    445

    Lightbulb

    #10 solution seems to be unrelated to the problems posted by the other users.

    The issues in the earlier posts appear to be caused by a recent change in the default settings of TigerVNC, which accepts vnc connections from localhost only.
    The solution is to either:

    - tunnel your vnc connection through ssh - This is the recommended solution
    - Add the following to /etc/vnc.conf
    Code:
     $localhost = "no";
    More infos can be found here:

    https://whitedome.com.au/re4son/topic/vnc/

Similar Threads

  1. No symlinks in current kali-linux-1.1.0a-armhf.img.xz
    By Dave Driesen in forum ARM Archive
    Replies: 6
    Last Post: 2015-08-18, 21:18
  2. Kali 2.0 RPI2 image issues
    By tazdevil in forum ARM Archive
    Replies: 0
    Last Post: 2015-08-11, 22:43
  3. Replies: 1
    Last Post: 2014-08-19, 13:35
  4. Kali ARMHF image on Fat32 sdcard.
    By kaju666 in forum ARM Archive
    Replies: 0
    Last Post: 2013-12-19, 11:04

Tags for this Thread

Posting Permissions

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