Nukear's post actually will result in a non-functional Lumina desktop session...
Try this instead:
To install the package + X11 (can use other xorg packages instead, like "xorg-minimal" if you like)
pkg install lumina xorg
To start a Lumina desktop session from the CLI:
start-lumina-desktop
Alternatively, you can put "exec start-lumina-desktop" at the end of your ~/.xinitrc, and then you can run startx
instead. (Typically used if you need to customize your X startup settings)
As far as other services which Lumina can use if enabled in /etc/rc.conf:
zfs : Lumina is agnostic about this. You will need it for access to ZFS filesystems naturally, but Lumina does not require it in any way.
hald : **DO NOT USE**. This is the device detection system from Linux (and is old/vulnerable). Lumina has never needed this, and never will.
moused : Probably a good idea. This is the mouse control daemon for FreeBSD, and while Lumina does not explicitly care how the mice are presented to the X11 server, moused seems to do the best job in my experience.
mixer : (NOTE: not "mixed" as mentioned in the posts above). If this is turned on, then Lumina can use the "mixer" utility to let the user change audio volume graphically. Not needed per-se, but is nice to have.
dbus:
This one is a bit more complicated due to a Qt bug, but Lumina itself neither needs or uses dbus.
1) Enable the service in /etc/rc.conf. This will turn on a root-permissioned DBUS server (generally for talking to consolekit or policykit - neither of which Lumina uses). I generally do not recommend/use this.
2) Enable the service for the user's desktop session only (user-permissions). Just wrap the desktop init call as follows: dbus-launch --exit-with-session start-lumina-desktop
3) No DBUS service. After installing the Lumina package, just run (as root) dbus-uuidgen --ensure
. That will simply save a unique ID string into /var/db/dbus/machine-id. Once that file is there, then Qt will no longer crash on startup if there is no dbus session active on the system, and you can use Lumina normally without any dbus pollution on the system. This may cause issues with other apps that try to forcibly use dbus, but that is another topic for another time...
NOTE: The start-lumina-desktop routine for Lumina has gone through a number of changes in the last couple versions, and will automatically try to detect one of the three dbus service options listed above, and automatically start #2 (local dbus session) if no dbus session is currently active (root or user), and the "machine-id" file is not found on the system (just to ensure the Qt crash gets avoided).