enabling and starting the server with systemctl, I have been connecting to it with Remmina on a Linux Mint machine via an SSH-Tunnel. Connects fine, however my client does only show me the wallpaper or the kodi-gui, but seems not to recieve the panel (polybar), X-windows or the popup-menu.
Btw, hi there and thanks for providing the awesome arch distribution and this forum. I’m new here and a linux-beginner.
How did you saved your sysctl settings & how you did it, might help in here as well.
systemctl enable x0vncserver
systemctl start x0vncserver
systemctl status x0vncserver
and voila the service is up and running, survives a reboot of the machine as well. However, as described here the server is invoced by the shell command ’ /usr/bin/x0vncserver -display :0 -rfbport 5900 -passwordfile /home/foo/.vnc/passwd &’ and there is a reference to the passwordfile but not to the config file or the xstartup-script.
edit: so, yes, you might have helped me looking into the right direction…
someone else might help you better on this topic(vpn issues)
Maybe, although there is no vpn issue involved so far.
According to the wiki the x-startup script that you are using should be considered like a ~/.xinitrc
You can see what is in your xinitrc and pick out just what you want, but given your existing script is using an xinitrc I’ll assume I can too. I would suggest trying something like this for your vnc startup script.
vncconfig -iconic &
xterm -geometry 80x24+10+10 -ls -title “$VNCDESKTOP Desktop” &
# shouldn't need to exec it, ~/.xinitrc already exec(s) the main process
I’m really not sure why the wiki is saying to unset the dbus environment variables, so we’re just gonna run with it and assume they are being re-set by the vnc.
Lemme know if this helps
EDIT: I see you’re using the default /etc/X11/xinit/xinitrc
This script doesn’t really have much going on, see for yourself
It starts a few programs and runs twm, I don’t have a lot of experience with twm but I don’t believe it has true X support. It’s basically one of the smallest (and in my opinion worst) window managers of all time, so my above solution should work for you
Hi natemaia, thanks for your input. Indeed I haven’t cat into the xinitrc so far. And my archlabs-machine doesn’t even have twm installed, so I assume whichever script is invoced, it is supposed to use openbox instead of twm (as mentioned in my first post).
The ~/.xinitrc on my archlabs-machine seems to be the standard archlabs-script and while nano into it I have found
# this file is executed when calling startx
# To run a different WM, set session="WM" below, or run:
# startx ~/.xinitrc WM
# [..more code..]
# Do NOT put commands below the exec lines
case $session in
i3|i3wm) exec i3 ;;
bsp|bspwm) exec bspwm ;;
xfce|xfce4) exec startxfce4 ;;
openbox) exec openbox-session ;;
awesome) exec awesome ;;
*) exec "$1" # Unknown, try running it
which looks not only good but even very neat to me. There is the same copy of an ~/.xinitrc script in /root/ as well. I am mentioning that, because I assume (!!! don’t know) that in the context of a foobar.service file ~ is located at /root/. So far my archlabs-machine has no /root/.vnc/ and both config and xstartup are only located at /home/foo/.vnc/ until now.
So once again, thanks for your input.
I believe giving an install of twm a try isn’t necessary. Before I set up a different xstartup script as you suggested, I think I have got to get the location of config and xstartup right.
The source command isn’t part of the POSIX specification and so shouldn’t be used with a /bin/sh shebang (although it will work in ArchLabs because /bin/sh is symlinked to bash); the portable version is:
Works as a service as well, but I don’t know why. There is neither a xstartup file nor a .vnc folder in
/root/ /etc/ /etc/systemd/ /etc/systemd/system/
and foo isn’t the only useraccount on this machine, so I wonder how x0vncserver knows that /home/foo/.vnc/xstartup is the correct startup script to use. Additionally, who knows why the x0vncserver is a kind of slow - compared to a Remmina (Mint) <-> x11vnc (Bunsenlabs) vnc-session and despite of an GBit/s-LAN uplink?
The script containing that line started with #!/bin/sh: this indicates that the script should be parsed by /bin/sh and it also means that the script should be compatible with the Portable Operating System Interface (POSIX), which is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems.
The idea is that a #!/bin/sh script should be able to run in any Unix-like operating system (and even in Windows under CygWin) and so all such scripts must conform to the POSIX man page:
Although #!/bin/sh scripts will run under bash, the reverse may not be true: bash scripts can have features and syntax not found in the POSIX specification which will cause #!/bin/sh scripts to fail unless /bin/sh is symlinked to bash.
These features are called “bashisms” and the source command is an example of such a beast, as declared by the checkbashisms tool (available in the AUR):
empty@hegel:~ $ checkbashisms test
possible bashism in test line 9 (should be '.', not 'source'):
^ As you can see, the suggested POSIX-compliant alternative to source is . (“dot”), which does the exact same thing.
This is all rather irrelevant in ArchLabs though because /bin/sh is symlinked to bash but if you changed this to gain a performance advantage then any #!/bin/sh scripts that contained bashisms would subsequently fail.