Cannot get to connect headless RPI4B through VNC

Ask questions about Arch Linux ARM. Please search before making a new topic.

Cannot get to connect headless RPI4B through VNC

Postby greynote » Mon Oct 07, 2024 4:47 pm

Hello.
I am trying to connect to a headless RPI through VNC without success.
I have installed X11VNC and xf86-vide-dummy following this guide

[url]https://wiki.archlinux.org/title/Xorg#Monitor_settings[/url]

/etc/X11/xorg.conf.d/10-headless.conf
---
Section "Monitor"
Identifier "dummy_monitor"
HorizSync 28.0-80.0
VertRefresh 48.0-75.0
Modeline "1920x1080" 172.80 1920 2040 2248 2576 1080 1081 1084 1118
EndSection

Section "Device"
Identifier "dummy_card"
VideoRam 256000
Driver "dummy"
EndSection

Section "Screen"
Identifier "dummy_screen"
Device "dummy_card"
Monitor "dummy_monitor"
SubSection "Display"
EndSubSection
EndSection
---

But when I run x11vnc -create I get this:

[alarm@alarmpi ~]$ sudo x11vnc -create
###############################################################
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@ @#
#@ ** WARNING ** WARNING ** WARNING ** WARNING ** @#
#@ @#
#@ YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!! @#
#@ @#
#@ This means anyone with network access to this computer @#
#@ may be able to view and control your desktop. @#
#@ @#
#@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
#@ @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@ @#
#@ You can create an x11vnc password file by running: @#
#@ @#
#@ x11vnc -storepasswd password /path/to/passfile @#
#@ or x11vnc -storepasswd /path/to/passfile @#
#@ or x11vnc -storepasswd @#
#@ @#
#@ (the last one will use ~/.vnc/passwd) @#
#@ @#
#@ and then starting x11vnc via: @#
#@ @#
#@ x11vnc -rfbauth /path/to/passfile @#
#@ @#
#@ an existing ~/.vnc/passwd file from another VNC @#
#@ application will work fine too. @#
#@ @#
#@ You can also use the -passwdfile or -passwd options. @#
#@ (note -passwd is unsafe if local users are not trusted) @#
#@ @#
#@ Make sure any -rfbauth and -passwdfile password files @#
#@ cannot be read by untrusted users. @#
#@ @#
#@ Use x11vnc -usepw to automatically use your @#
#@ ~/.vnc/passwd or ~/.vnc/passwdfile password files. @#
#@ (and prompt you to create ~/.vnc/passwd if neither @#
#@ file exists.) Under -usepw, x11vnc will exit if it @#
#@ cannot find a password to use. @#
#@ @#
#@ @#
#@ Even with a password, the subsequent VNC traffic is @#
#@ sent in the clear. Consider tunnelling via ssh(1): @#
#@ @#
#@ make_clickable_callback(MAGIC_URL_FULL, ' ', 'http://www.karlrunge.com/x11vnc/#tunnelling', '', ' class="postlink"') @#
#@ @#
#@ Or using the x11vnc SSL options: -ssl and -stunnel @#
#@ @#
#@ Please Read the documention for more info about @#
#@ passwords, security, and encryption. @#
#@ @#
#@ make_clickable_callback(MAGIC_URL_FULL, ' ', 'http://www.karlrunge.com/x11vnc/faq.html#faq-passwd', '', ' class="postlink"') @#
#@ @#
#@ To disable this warning use the -nopw option, or put @#
#@ 'nopw' on a line in your ~/.x11vncrc file. @#
#@ @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
###############################################################
07/10/2024 16:36:35 x11vnc version: 0.9.16 lastmod: 2019-01-05 pid: 3079
07/10/2024 16:36:35
07/10/2024 16:36:35 wait_for_client: WAIT:cmd=FINDCREATEDISPLAY-Xvfb
07/10/2024 16:36:35
07/10/2024 16:36:35 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560
07/10/2024 16:36:35
07/10/2024 16:36:35 Unable to establish connection with systemd socket
07/10/2024 16:36:35 Autoprobing TCP port
07/10/2024 16:36:35 Autoprobing selected TCP port 5900
07/10/2024 16:36:35 Autoprobing TCP6 port
07/10/2024 16:36:35 Autoprobing selected TCP6 port 5900
07/10/2024 16:36:35 listen6: bind: Address already in use
07/10/2024 16:36:35 Not listening on IPv6 interface.
07/10/2024 16:36:35

The VNC desktop is: alarmpi:0
PORT=5900
07/10/2024 16:36:37 Got connection from client 192.168.201.102
07/10/2024 16:36:37 0 other clients
07/10/2024 16:36:37 Normal socket connection
07/10/2024 16:36:37 incr accepted_client=1 for 192.168.201.102:49764 sock=5
07/10/2024 16:36:37 wait_for_client: got client
07/10/2024 16:36:37 Client Protocol Version 3.8
07/10/2024 16:36:37 Protocol version sent 3.8, using 3.8
07/10/2024 16:36:37 client progressed=1 in 10/1 0.008828 s
07/10/2024 16:36:37 client_set_net: 192.168.201.102 0.0052
07/10/2024 16:36:37 wait_for_client: running: env X11VNC_SKIP_DISPLAY='' /bin/sh /tmp/x11vnc-find_display.OtQyaD
egrep: warning: egrep is obsolescent; using grep -E
07/10/2024 16:36:37 wait_for_client: find display cmd failed.
07/10/2024 16:36:37 wait_for_client: FINDCREATEDISPLAY cmd: /bin/sh /tmp/x11vnc-find_display.OtQyaD Xvfb
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
trying N=20 ...
egrep: warning: egrep is obsolescent; using grep -E
grep: warning: stray \ before +
/tmp/x11vnc-find_display.OtQyaD: line 788: hostname: command not found
redir_daemon=
/tmp/x11vnc-find_display.OtQyaD: line 462: hostname: command not found
/usr/bin/xinit /usr/bin/xterm -- /usr/bin/Xvfb :20 -screen 0 1280x1024x24 -cc 4 -nolisten tcp -auth /tmp/.xas314914560.M5XTwA

/usr/bin/nohup: appending output to 'nohup.out'
(EE)
(EE) Backtrace:
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
07/10/2024 16:36:43 wait_for_client: read failed: /bin/sh /tmp/x11vnc-find_display.OtQyaD Xvfb
07/10/2024 16:36:43 fgets: No such file or directory
--------------------------------

Any idea to fix it?
Thank you very much :-)
greynote
 
Posts: 1
Joined: Mon Oct 07, 2024 4:09 pm

Return to User Questions

Who is online

Users browsing this forum: No registered users and 27 guests