Other startx: [cmd]exec cmd[/cmd] versus [cmd]ck-launch-session ...[/cmd]

I am a newbie with freebsd and the main contributor of fvwm-crystal. I just installed the last freebsd version and fvwm3 along with fvwm-crystal from its github fvwm-crystal:freebsd work in progress branch. In ~/.xinitrc, I put exec /usr/local/bin/fvwm-crystal and it works.

But I saw on the forum that other startx users use something like ck-launch-session dbus-launch --exit-with-session startlxde.

What is the best or recommended way to do it on freebsd?
 
Neither fvwm nor fvwm-crystal require dbus, which imply I don't need it. fvwm-crystal is completely independent from the system, it just use what it find. As example with its Quit menu for system shutdown or hibernation, but it is to the sysadmin to get them to work as wanted.

Even for the Qt and Gtk themes, it is let to the user to configure them with qt5ct, qt6ct or lxappearence, and it will not mess with these settings. It was so when I begun to use it, and I like it that way.
 
there are some applications that use dbus

i think obs studio uses dbus together with the xdg portal to select a screen to record
also i think mpv may use dbus from memory
As fvwm-crystal don't require dbus, it is fine for me to not use it. As it also depend on the applications an user will use, I will check its documentation and add words about this into it. The final choice will be to the user or sysadmin.

You mention obs studio. Fvwm-crystal have a mixer control that support alsamixer among other. It is made to use it with ALSA, not OSS. We will see what I can do with it, and what will be left on the todo list when the first freebsd compatible release will be out in the world.
 
Back
Top