Hackberry Pi

The Hackberry Pi is a handheld Linux terminal similar to the Clockworkpi uConsole. Its key feature is it uses left over keyboard stock from the old Blackberry phones of yesteryear.

 

Both devices are available from Tindie;

Hackberry Pi Zero

Hackberry Pi 5

You can read my comparison to the uConsole here, and here are 10 things to do after you get your Hackberry Pi 5.

The Hackberry Pi currently comes in two flavors, one based on the Raspberry Pi Zero 2 W (RPi 0) and one based on the Raspberry Pi 5 (RPi 5). Both devices have a 4" 720x720 screen, both have a battery life of 2-3 hours depending on what you are doing with it and both cost roughly the same, before you purchase the Rasperry Pi you need to power it.

The RPi 0 version is a rather limited device, primarily because the RPi 0 is a limited device. It has 512 MB of RAM and runs at 1 Ghz. You can run a desktop environment (DE) on it, but you will not be happy with the performance of some application like Firefox, Chrome or well anything more complicated then a text editor or calculator. The RPi 0 was not designed to be a desktop computer, it was designed to be a hopped up micro controller, so it does not do well in this area. However, if you are a command line junkie, this limitation will not bother you in the slightest.

There are plenty of reasonably good replacements for GUI applications that run in text mode. Alpine and W3m for email and web browsing, cmus and mpv for playing music and videos, and wordgrinder, sc and tpp replace LibreOffice (mostly? I guess). While you will find these applications limited compared to their GUI counter parts and the learning curve a bit annoying, once you get use to them, they are usable and have a certain minimalist appeal to them.

The biggest problem I had with the RPi 0 version is the wireless does not work well. This is because the front cover is made of aluminum and blocks the signal. It seems some people have better luck than others, I tried two different RPi 0's in mine and both could connect to my router, but neither could actually communicate with it in any meaningful manner. I had several USB wifi dongles laying around and I just plugged one of those in to solve the problem.

Edit: I did eventually get the on board WiFi working. I wish I could tell you how I did it, but I cannot, it just started working one day.

The RPi 5 version is a much more usable device, depending on what RPi 5 you buy. If you get the 4 GB version, you will want to stick with a light DE and stay away from Gnome or KDE. If you get an 8 GB or 16 GB RPI 5, you can pretty much do anything you want with it. I bought the 8 GB version and it has handled everything I have thrown at it so far.

The big, I do mean big, advantage the RPi 5 version has over the RPi 0 version and the uConsole for that matter, is the PCIE connector on the board. The designer of this device left room to mount a M.2 hat on the RPi 5 that provides access to the PCIE connector. It just so happens Waveshare makes such a hat. This hat not only provides an M.2 slot, it also provides active cooling to the RPi 5, something it really needs. You can mount just about any 2242 / 2230 M.2 card into it, like a fancy A.I. accelerator, but we all know the primary use case is mounting an NVME SSD card to it. SSD storage is faster and more reliable than an SD card. This by itself, makes this the stand out product among hand held terminals.

I only really had one issue with this device, when I first put it together I couldn't get video to save my life. As an assembly tip for those who have not purchased one yet, if you assemble it and don't get video after waiting 5-10 minutes, chances are good you didn't line up the GPIO contacts properly. Remove the cover to the RPi 5 and remove the standoff screws. If you did not remove the piece of plastic that came inside the case, take it out now and throw it away. Now place the Raspberry RPi 5 back in and put the bottom left stand off screw in first, it is the one closest to the GPIO pogo pins, tighten it down and then back it off 1 or 2 turns. Then put in the right stand off screw, tighten it down and then back it off 1 or 2 turns. The Raspberry Pi 5 should have just a little bit of wiggle, move it around until you feel the pogo pins snap into place, you should feel it click. Then tighten both screws down and put in the top two screws and tighten them down. Put the cover back on and try to boot it up again, you should get video.

Both of these devices share the same keyboard and I do need to talk about it. The keyboards take some getting use to, not just because they are hideously small, but because the keyboard is a challenge to use. It takes time to figure things out and learn all key combinations needed to do even basic typing. I can see how this keyboard was considered innovative back in the early 2000's, but there is a good reason why they were replaced, they are awkward to use. Part of the issue was, I am Gen X and did not grow up thumb typing like the younger generations did. I have adapted to it, though it has been a struggle.

Overall, if you are considering the purchase of one of these devices, I would go with the RPi 5 version, as a real functioning tool, it is the better choice. The RPi 0 version is really not much more than a command line junky toy. The RPi 0 version does not do anything the RPi 5 doesn't do better and its not that much cheaper. It's only advantage is it is smaller and lighter, and it will actually fit in your pocket.

Eulogy for my Brother

We have known my Brother was dying for about 6 months now. He had ALS and although he had just been officially diagnosed, he had the symptoms for quit some time. His decline over the last 6 months has been very rapid.

Before my Brother died, I kind of assumed it would not affect me much, I mean we were not close in any meaningful way. We had not talked much in decades and even when we did, our conversations tended to be shallow and I hate to say it, but uninteresting. Neither of us made any effort to change that, even in the last months of his life.

However, I find that is not the case at all. Even though we not been close since we were teenagers, there was a time when we were. We grew up together, we did things together, we had adventures together and we even had many of the same friends. When I say that, I of course mean, he and his friends let me hang around them sometimes.

You know he was the one who taught me to play chess. I remember the first time I beat him, how happy I was. Incidentally, that was also the last game we ever played, LOL, yes, I think that is funny.

My Brother taught me to drive, actually both of my Brothers were tasked with teaching me to drive. My Mother had taught them to drive and her revenge for that was they had to teach me. However, my older Bother was out of the house by then and so the majority of the teaching was done by the middle son. I cannot say whether or not he was a good teacher or not, but I did manage to learn to drive and eventually get my license with out killing anyone, so I am sure he considered that a win.

I also remember a conversation we once had about the turn of century, he said we would live to see the 21st century and that I would only be 38 years old. Of course being in the 4th grade at the time, that seemed an impossible amount of time in the future. Of course I started to imagine flying cars and jet packs, I am still disappointed about that by the way.

When I discovered my inner dialog, I thought everyone could hear it as well, it was my Brother who explained to me that that was not the case, I was probably 4 at the time.

I think I will miss him.

My Brother died today

 I am at that point in my life where people start dying around me. My Father died 15 years ago, but that was a small bump, I never really had a relationship with him, so it did not matter much to me. I know my Mother does not have many if any years left and of course I have lost grandparents and such as well, but it is weird and eye opening when someone you grew up with and is only a couple of years older dies.

NixOS

Last month I talked about GUIX and how much I disliked it. This month a took swing at NixOS, which is the Linux distro GUIX is based on. NixOS is a much more polished distribution of Linux than GUIX ever was or probably will be. NixOS brings a decent graphical installer to help you get through the basic install and once you are in, you then have access to the packaging and configuration system.

The packaging and configuration system is really where GUIX was supposed to shine, but I never got to the point where it was useful to me. NixOS on the other hand, did the tedious stuff for me, which is what an installer should be doing.

Everything about packaging and configuration is kept in the /etc/configuration.nix file which can be edited easily to add or remove functions or programs. Then once you have the file setup the way you like it, you can then take this file to a fresh install of NixOS and use it to reproduce your setup. The first thing you will probably want to do is break out the packages you want installed into a separate packages.nix file to keep you configuration file from becoming unwieldy. If you have more than 3 or 4 users, you probably want to break that out into a different file as well. This will help keep your configuration.nix file short and manageable.

Honestly, this is how GUIX should have been done. Since GUIX is a newer spin on NixOS, there is no reason why it should not have been better. I still prefer Debian, I certainly am not switching to NixOS. Because of the way it handles packages and maintains backup of old configurations, it eats hard drive space, which is fine if you have a couple of terabytes of storage, but not so good if you are using an old laptop with 512 GB or less of storage. On top of that, the good things about NixOS can be done with any other distribution by simply writing a shell script and running it after an install. So this does not really bring much to the table.

GUIX Package Manager

 For those who don't know, GUIX is a package manager for Linux. It is supposed to work across all (or most) Linux distributions and provides some level sand boxing between applications. There is also a distribution based entirely on this software. It is supposed to be an alternative to Flatpak and Snap, both of which have their own problems.

Yesterday I spent the day messing around with it. I installed the distro on my test machine, I also tried it on an clean install of Debian. I have used a lot of package managers over the years, Apt, Yum, Pacman, Portage, and yes, Flatpak and Snap, I have used most all of them at one point or another. Guix is without a doubt the worst package manager I have ever used. I have no idea who thought this package manager implementation was a good idea, but I hope they did not quit their day job to develop this garbage.

First the things I liked; Nothing, I didn't like anything about Guix. It does nothing Flatpak or Snap doesn't do, it brings no new ideas or technology to the table, it is just a terrible implementation of a good idea.

Things I didn't like. Fuck where do I start. The Guix distribution took half a day to install a basic system and I do mean basic, no web browser, no email client, nothing more complex than a text editor. Debian takes 30 minutes for a full install, bells, whistle and all. On top of that once I had it install, it was taking up close to 20 GB of storage, what the hell Guix? A full install of Debian comes in well under 5 GB.

Once I had the basic install, I started installing programs, that was a bloody mistake. Every program took half an hour to install and a boat load of other packages would install with it, often simply reinstalling packages that were already on the system. To make things worse, commonly used programs like Firefox and Thunderbird were not available. I either had to compile from source or use Guix equivalents, Icecat and Icedove. Which apparently are freer and more open sourcey than Firefox and Thunderbird, but lack just about every feature implemented in those two programs in the last 5 years.

After nearly 8 hours of screwing about with the distro and still not having a system I could use as a daily driver, I gave it up. I installed a basic install of Debian and whittled it down to the same state the basic install of Guix gave me, as I said earlier, this took me less than 30 minutes to accomplish. I then installed the Guix package manager on this poor machine. Guix immediately brought all its worst features to Debian. It took over an hour to pull down its repository information and then promptly installed a bunch of packages that already existed on the system, which took an hour. Then I tried to install Icecat, and it repeated the same bullshit it did on its own distro and after half an hour when it was finished, I could not actually run Icecat. It was not on the menu and I could not run it from the command line. At this point, I was done with Guix.

No one should be using Guix. I would recommend Gentoo Linux before I would recommend Guix as a distribution. Debian + Flatpak will give you everything Guix gives you, but you will have more storage left, you will spend far less time managing it and you will not hate your computer and yourself everyday. If you want a challenge, install Arch Linux, install Gentoo, heck to Linux from Scratch, but please for the love of god, do not use Guix, don't encourage them.

Minimalist Linux III

If all that was too much work for you, go to my github where you will find all my config files and a nice little install script to do the heavy lifting for you.

 https://github.com/cjstoddard/My-Openbox

This will make your desktop look and function like mine. However if you actually read the blog posts, making minor changes should not be a problem.

You will still need a basic install of Debian 12.

Tiling windows managers still suck.

Minimalist Linux II

Now that we have a functional desktop, it is time to pretty it up a bit and add a bit of functionality. Nobody normal like a stock boring desktop, so I am going to show you some customization tricks.

The first thing most people do is set wall paper. Find an image you like and download it into your home directory and rename it to something simple, I named mine angel.jpg.

mv background.jpg angel.jpg

Next we want to make it available system wide, for later.

sudo mkdir /usr/share/backgrounds
sudo cp angel.jpg /usr/share/backgrounds/
sudo chown root:root /usr/share/backgrounds/angel.jpg

Now place the picture wherever you want it to go. Normally there is a Pictures folder, you can just put it there.

mkdir Pictures
mv angel.jpg Pictures/

Now run these commands;

feh --bg-scale Pictures/angel.jpg
nano ~/.config/openbox/autostart

Add this line to the autostart file;

(sleep 1; ~/.fehbg) &

Now if you exit out of Openbox and go back in, you should have a nice background. Our next step is to change the Openbox theme, the default is Clearlooks. Which is fine, but for whatever reason lots of people like darker themes. Edit the configuration file;

nano ~/.config/openbox/rc.xml

Look for the <theme> section, and replace <name>Clearlooks</name> with <name>Artwiz-boxed</name>. Restart Openbox and you should see a change in how the windows decorations look. If this is not to your taste, there are many themes available in /usr/share/themes. You will have to google the themes to see how they each look.

The biggest issue with this setup so far is when you boot to the system it drops to the command line and you have to run startx to get to you desktop. There is also no way to lock the screen if you need to. We will need a display manager for this, lightdm is the one I like.

sudo apt install lightdm
sudo systemctl enable lightdm

When you reboot the system, you should come to a graphical login screen. We could leave it there, but that would be boring. To change the background open the configuration file;

sudo nano /etc/lightdm/lightdm-gtk-greeter.conf

At the bottom, add the following line;

background=/usr/share/backgrounds/angel.jpg

This will set the background of the login screen. Any picture you want to use, will have to be placed in the /usr/share/backgrounds/, otherwise it will not work properly.

Next we want to add the ability to lock the screen when needed. Run;

nano ~/.config/openbox/rc.xml

search for </keyboard> and add these lines just above that line;

<!-- Keybindings for [l]ock screen -->
  <keybind key="W-l">
    <action name="Execute">
      <command>i3lock -c 000000</command>
    </action>
  </keybind>

Once you restart Openbox, the screen can now be locked by pressing the Winows key + l.

For the final piece of customization, we are going to use a program called conky to add a dynamic element to your desktop. The first thing we need is a default config file.

cp /etc/conky/conky.conf .conkyrc
nano .conkyrc

The first thing I like to do is make conky transparent. I mean why have wallpaper if you are just going to block it out. Right under conky.config = { add this line;

own_window_transparent = true,

Next look for this section;

${color grey}Networking:
Up:$color ${upspeed} ${color grey} - Down:$color ${downspeed}

and change it to look like this;

$hr
${color grey}Networking:
IP Address:$color ${addr enp3s0}
Up:$color ${upspeed enp3s0} ${color grey} - Down:$color ${downspeed enp3s0}

My network device is enp3s0, you will need to run the command "ip addr" to find your network device and replace accordingly. Now go to the bottom of the file and just above the ]], place these lines;

$hr
${exec cat .keys.txt}
$hr

Now save and exit the file. The last lines I had you place are there because I like to have an onscreen reminder of all those dumb keybindings we setup that I can never remember, so run this command;

nano .keys.txt

and put the following text into it, then save and exit.

-------------------------------------
Keybindings
-------------------------------------
ROX-filer     windows-f(ile manager)
Rofi          windows-m(enu)
Firefox-ESR   windows-w(eb)
Tilix         windows-t(erminal)
Thunderbird   windows-e(mail)
Audacious     windows-a(udio)
VLC           windows-v(ideo)

Print Screen  windows-prtscn
Lock Screen   windows-l

Switch Desktops;
  ctrl-alt-right
  ctrl-alt-left
-------------------------------------

Finally, edit the autostart file

nano ~/.config/openbox/autostart

and add this line, then save and exit the file.

(sleep 5 && conky -c .conkyrc) &

Finally, reboot the system and if all went well, things should look much better. With a display manager and conky running, the amount of memory consumed crawled up above 512 MB, but probably not by much. I consider it to be a worth while trade off for the added functionality and general look of the desktop.

As a final note, I know some of you are going to scream that I should have used a tiling WM like Suckless or i3. I do not like tiling WM's, I prefer stacking WM's. Tiling WM's make me work the way the developers think I should be working, fuck that is all I am going to say about it.

Minimalist Linux

Honestly, I am not a fan of the minimalist Linux movement. Today's machines are more than capable of handling what we throw at them and RAM is cheap. There is no reason not to use Gnome or KDE and even if you prefer a more legacy look, MATE and Cinnamon work just as well. The problem with minimalist desktops is you sacrifice ease of use and functionality. I don't care what anyone says ctrl-t is not easier than clicking on a button.

Having said that, there is some use for such a setup, for instance if you have a low end machine with limited RAM and no upgrade paths. In this case a GUI that eats less than 512 MB of RAM is nice. I have a Lenovo ideapad-1 with a Celeron G4020 and 4 GB of RAM, I like it because it is light and easy to carry around a busy airport. Gnome or KDE would bring this system to its knees and even MATE is a bit much for it.

In a case like this, I would forgo a Desktop Environment (DE) altogether and just use a Windows Manager (WM), in this case Openbox. A WM provides the basics, windows and decorations nothing more, a DE goes a step further and add the bells and whistles that make things easier to use and flashier.

The first step is to install Debian 12, when you get to the part where it asks what Desktop you want, uncheck everything except the bottom two options. Once that is done, reboot and log in as root, update the system and add the user you created to the sudo group. Then reboot again and log in under you user account.

Next comes installing what you need

sudo apt install xorg xbacklight xbindkeys xvkbd xinit xinput xserver-xorg-input-all xterm openbox obconf dunst dbus-x11 feh hsetroot i3lock libnotify-bin libxcb-xinerama0 lxappearance lximage-qt menu picom rofi scrot tint2 volumeicon-alsa xfce4-power-manager alsa-utils fonts-dejavu fonts-firacode fonts-font-awesome fonts-liberation2 fonts-ubuntu fonts-jetbrains-mono gtk2-engines-murrine gtk2-engines-pixbuf network-manager network-manager-gnome papirus-icon-theme pavucontrol pipewire-audio qt5-style-plugins rox-filer conky

Here we are installing our applications, I am avoiding heavy duty applications like LibreOffice and GIMP in favor of applications like Abiword and Inkscape, which eat less memory. Adjust to taste.

sudo apt install firefox-esr audacious thunderbird vlc emacs abiword gnumeric atril pluma mate-calc tilix inkscape

These next commands setup our WM in a basic configuration

mkdir -p ~/.config/openbox
cp /etc/xdg/openbox/* ~/.config/openbox/
systemctl --user --now enable wireplumber.service

Then we are going to setup the utilities needed for the basic functioning of the desktop. Type the following;

nano ~/.config/openbox/autostart

And add these lines;

hsetroot -solid "#000000"
xfce4-power-manager &
dunst -config ~/.config/dunst/dunstrc &
tint2 &
(sleep 5; volumeicon) &
nm-applet &

The hsetroot command sets the background color, #000000 is hexadecimal for black, for a nice blue, use #2e86c1, if you want to choose your own color, this site will help, https://htmlcolorcodes.com/ . You can set a picture as your background using a program call feh, but I am not covering that here.

Next we need to edit the .xinitrc file so when xorg starts, it knows what WM we are using. Type this command;

nano .xinitrc

and add these lines;

#!/bin/bash
exec openbox-session

Now, type startx and Openbox will start. You will see a blank screen, with a bar at the bottom. Right click on the background and choose terminal off the menu. In the terminal type in;

rofi-theme-selector

Rofi is the tool we will use to find and run programs. In its default state a window pops up in the middle of your screen, I prefer a bar at the top. Off the menu of choices, choose the demnu theme, to set the theme. Then we will want to configure rofi, so it shows icons with the programs. Type in the terminal;

nano .config/rofi/config.rasi

and add these lines to the file;

configuration{
display-drun: "Applications:";
display-window: "Windows:";
font: "JetBrainsMono Nerd Font Medium 10";
modi: ["drun", "window", "run"];
icon-theme: "Papirus";
show-icons: true;
}

@theme "/usr/share/rofi/themes/dmenu.rasi"

The final step is to setup our hotkeys for running the applications we use the most. Type in the following command;

nano ~/.config/openbox/rc.xml

search for </keyboard> and add these lines just above that line;

 <!-- Launch rox-filer when windows-f is pressed -->
  <keybind key="W-f">
    <action name="Execute"><command>rox-filer</command></action>
  </keybind>
<!-- Launch rofi when windows-m is pressed -->
  <keybind key="W-m">
    <action name="Execute"><command>rofi -show drun</command></action>
  </keybind>
<!-- Launch firefox when windows-w is pressed -->
  <keybind key="W-w">
    <action name="Execute"><command>firefox-esr</command></action>
  </keybind>
<!-- Launch tilix when windows-t is pressed -->
  <keybind key="W-t">
    <action name="Execute"><command>tilix</command></action>
  </keybind>
<!-- Launch thunderbird when windows-e is pressed -->
  <keybind key="W-e">
    <action name="Execute"><command>thunderbird</command></action>
  </keybind>
<!-- Launch audacious when windows-a is pressed -->
  <keybind key="W-a">
    <action name="Execute"><command>audacious</command></action>
  </keybind>
<!-- Launch vlc when windows-v is pressed -->
  <keybind key="W-v">
    <action name="Execute"><command>vlc</command></action>
  </keybind>
<!-- Launch scrot for screen caps when windows-print is pressed -->
  <keybind key="W-Print">
    <action name="Execute"><command>scrot 'screenshot-%Y-%m-%dT%H%M%S.png'</command></action>
  </keybind>

With this configuration, your keybindings will be as follows.

ROX-filer         windows-f(ile manager)
Rofi                 windows-m(enu)
Firefox-ESR    windows-w(eb)
Tilix                windows-t(erminal)
Thunderbird   windows-e(mail)
Audacious      windows-a(udio)
vlc                  windows-v(ideo)

Switch Desktops;
  ctrl-alt-right
  ctrl-alt-left

Print Screen  windows-prtscn

All that is left to do is right click on the background and choose Exit, this will drop you back to the command line, reboot the system and log back in. Then type startx to get back to your desktop. To run a program you do not have a hotkey for, simply press the Windows Key + m, at the top rofi will appear, simply start typing the name of the program and when it appears, highlight it and press enter.

Keep in mind, this is a very basic and plain setup. As I said earlier, you can set a background picture and you can add some interesting bling using conky. I may go into these things later. But for now, enjoy your minimalist desktop that consumes less than 512 MB of memory.

Building a Firefox Kiosk

 In my home lab I have been experimenting with various types of virtual machines. Mostly this has been complete operating systems. However one of the things Broker servers can do for you is give access to single applications, without the need for complete operating systems. Broker software like VMWare Horizon is expensive, but honestly, something like Remmina, which is a multi protocol desktop connection client, serves the same purpose.

In this example, I am setting up Firefox as a app, when the VM is launched Firefox is all the user has access to. If you wanted to, you could install this setup on a PC and just use it as a kiosk, no virtualization is really needed.

The first step is installing Debian 12, you can use Ubuntu server as well. We want a minimal install, no extra software outside of ssh server, not even a desktop environment. The resource requirements are very low; 1 core, 2 GB of RAM and 8 GB of storage will be more than enough. Once you are done, log in as root and install the needed software

apt update && apt upgrade

apt install sudo firefox-esr xorg openbox lightdm tigervnc-standalone-server tigervnc-common

Once that is done you will need to add the kiosk user, which is the account which the system will automatically log into when anyone accesses the virtual machine.

useradd kiosk

Next, enter the kiosk user account;

su - kiosk

Now we are going to make 2 confiuration files, one for VNC so the account can be accessed remotely and one for Openbox, which is the window manager we will use.

mkdir .vnc

nano .vnc/config

Enter the following text into the file, then press ctrl-x, save the file and exit.

session=openbox
geometry=1200x720
localhost
alwaysshared

Then move on to Openbox;

mkdir -p .config/openbox

nano .config/openbox/autostart

Enter the following text into the file, then press ctrl-x, save the file and exit.

env DISPLAY=:1 firefox-esr -kiosk 'http://url' &

If you want to setup a different application, this is the place to do it. Firefox can be replaced with Chrome or LibreCalc, just make sure the appropriate software is installed. Go a head and exit the kiosk user account by typing exit and you will be back in the root account.

We now want to give over display :1 to the kiosk user so when when someone logs in via RDP, Firefox will display on the VNC connection instead of the local display.

nano /etc/tigervnc/vncserver.users

Enter the following text into the file, then press ctrl-x, save the file and exit.

 :1=kiosk

The next step is to make it so the system booting directly into the kiosk user account and starts the VNC server.

 nano /etc/lightdm/lightdm.conf

Go to the bottom of the files and add these lines, then press ctrl-x, save the file and exit;

[SeatDefaults]
autologin-user=kisok
user-session=openbox

[VNCServer]
enabled=true
command=/usr/bin/Xvnc -rfbauth /etc/vncpasswd
port=5901
width=1200
height=720
depth=32

Finally, we want to setup the VNC password, that will be required when the user initiates a VNC connection.

vncpasswd /etc/vncpasswd

Now, reboot the system. On the local display, you will get a blank screen, if you right click on the background, you should get a menu. When you access it with VNC, Firefox should automatically start up in kiosk mode.

Installing VNC Server software into Debian 12

 Something that should be easy to do in Linux is getting VNC server software up and running without too much problem, except its not. All the instructions I found used TightVNC or TigerVNC and for whatever reason required the installation of XFCE to make work. XFCE is not bad really, but it is not the desktop environment that I normally used.

This got me to wondering whatever happened to vino, which was a VNC package I used years ago but no longer seemed to be in favor. I looked around and although it is still available it is no longer being maintained. Further, because of a bug, the last person who worked on it, removed the configuration dialog, which forced the user to configure it with a command line tool. Ultimately though, it is still pretty easy to install and get running without all the extra hoops needed for TightVNC or TigerVNC.

sudo apt install vino

gsettings set org.gnome.Vino prompt-enabled false

Then run this command to make sure the prompt is disabled.

gsettings list-recursively org.gnome.Vino

Finally, add this to your startup programs and reboot the system;

/usr/lib/vino/vino-server --display=:0 &

That is pretty much it. You should now be able to access the desktop with Remmia or similar using port 5900.