Hi, first I want to thanks to the developer. I'm new to Obarun but not to Arch Linux. Arch is my first minimal linux, but when Arch switch to systemd I moved to Void Linux, now I'm trying Obarun.
So I have installed Obarun and installed necessary packages for gui with fluxbox. I run it with startx.
But I have this warning when i quit x:
66-all: fatal: unable to find: /home/fysnin/.66/system/state: No such file or directory
What could possibly wrong and how to troubleshoot this?
Thanks
I solved this by creating a user tree
Welcome

Some analysis with many unknowns.
Starting your X/wm session with startx (or xinit) your ~/.xinitrc is read.
If you had success in running "without" a user tree the problem you see at the end is not because you didn't have a user tree but that the command in .xinitrc (I think) that brought up the tree and services and brought it down on logout, doesn't find a tree.

If you simply created a tree that means that a boot-user tree and corresponding module for that user exists and the tree is enabled, otherwise the user tree wouldn't run.

What/how did you install the system and what does % 66-intree -g and % sudo 66-intree -g show?

Since I don't know what you have done I am suspecting you followed the instructions for creating a boot-user module and it created .xinitrc and .xsession in which the default user command to start user trees exists. Since you didn't have any it produced such an error.

Are you using/needing consolekit consoletracker dbus, etc.??
fungal_net wroteWelcome

Some analysis with many unknowns.
Starting your X/wm session with startx (or xinit) your ~/.xinitrc is read.
If you had success in running "without" a user tree the problem you see at the end is not because you didn't have a user tree but that the command in .xinitrc (I think) that brought up the tree and services and brought it down on logout, doesn't find a tree.

If you simply created a tree that means that a boot-user tree and corresponding module for that user exists and the tree is enabled, otherwise the user tree wouldn't run.

What/how did you install the system and what does % 66-intree -g and % sudo 66-intree -g show?

Since I don't know what you have done I am suspecting you followed the instructions for creating a boot-user module and it created .xinitrc and .xsession in which the default user command to start user trees exists. Since you didn't have any it produced such an error.

Are you using/needing consolekit consoletracker dbus, etc.??
I install obarun following the wiki.
% 66-intree -g

Name         : base
Initialized  : no
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : fysnin
Symlinks     : svc->source db->source
Contents     : /
               └─None

% sudo 66-intree -g

Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(195,Enabled,classic) tty-earlier@ tty12
               ├─(up,Enabled,oneshot) system-hostname
               ├─(up,Enabled,oneshot) mount-run
               ├─(up,Enabled,oneshot) populate-run
               ├─(up,Enabled,oneshot) mount-tmp
               ├─(up,Enabled,oneshot) populate-tmp
               ├─(up,Enabled,oneshot) mount-proc
               ├─(up,Enabled,oneshot) mount-sys
               ├─(up,Enabled,oneshot) populate-sys
               ├─(up,Enabled,oneshot) mount-dev
               ├─(up,Enabled,oneshot) mount-pts
               ├─(up,Enabled,oneshot) mount-shm
               ├─(up,Enabled,oneshot) populate-dev
               ├─(up,Enabled,oneshot) mount-cgroups
               ├─(up,Enabled,bundle) 00
               ├─(up,Enabled,bundle) all-Mount
               ├─(up,Enabled,oneshot) system-hwclock
               ├─(up,Enabled,oneshot) modules-kernel
               ├─(up,Enabled,oneshot) system-random
               ├─(up,Enabled,oneshot) modules-system
               ├─(up,Enabled,oneshot) system-sysctl
               ├─(239,Enabled,longrun) udevd-log
               ├─(404,Enabled,longrun) udevd
               ├─(up,Enabled,oneshot) udevadm
               ├─(up,Enabled,oneshot) system-fontnkey
               ├─(up,Enabled,oneshot) system-fsck
               ├─(up,Enabled,oneshot) mount-fstab
               ├─(up,Enabled,bundle) all-System
               ├─(up,Enabled,oneshot) mount-rw
               ├─(up,Enabled,oneshot) mount-swap
               ├─(up,Enabled,oneshot) mount-netfs
               ├─(up,Enabled,oneshot) local-loop
               ├─(up,Enabled,oneshot) local-sethostname
               ├─(up,Enabled,oneshot) local-time
               ├─(up,Enabled,oneshot) local-authfiles
               ├─(up,Enabled,oneshot) local-tmpfiles
               ├─(up,Enabled,oneshot) local-dmesg
               ├─(up,Enabled,bundle) all-Local
               ├─(up,Enabled,oneshot) all-Runtime
               ├─(up,Enabled,bundle) All
               ├─(752,Enabled,longrun) tty-rc@ tty2
               ├─(751,Enabled,longrun) tty-rc@ tty1
               ├─(750,Enabled,longrun) tty-rc@ tty3
               └─(up,Enabled,module) boot@ system

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(666,Enabled,classic) dhcpcd-log
               └─(667,Enabled,classic) dhcpcd

Name         : boot-user
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) setenv@ fysnin
               ├─(701,Enabled,longrun) svscan@ fysnin-log
               ├─(739,Enabled,longrun) svscan@ fysnin
               ├─(up,Enabled,module) scandir@ fysnin
               ├─(up,Enabled,oneshot) mount-run@ fysnin
               └─(up,Enabled,module) boot-user@ fysnin
I am glad to see a fellow minimalist, no dbus no consolekit, :)

If you were to need dbus you would need a service in the user tree like dbus-session@ fysnin
pulseaudio,, pipewire, are also user level services that can go on that base tree.

Since you are not using it (% 66-tree -D base) will disable this tree.
The warning you see is because on your ~/.xinitrc you have a command that says 66-all ... up
You can add a comment on the command # to eliminate it if you have no use for user services.
Also, since you are not running user services you can disable the boot-user tree as root. This tree just sets up s6 to run and supervise user services, otherwise user services can't be supervised. Remember 66 just sets things up, the work is done by s6.
% sudo 66-tree -D boot-user
% sudo 66-all -t boot-user down
You can leave it for when and if you need to run more services, like sddm, consolekit, dbus, ..etc. but now your machine will boot cleaner.

Also, I haven't figured out if there is any difference, but xinit will also start your X session just like startx in most cases.
startx is a long script that ends in 
xinit "$client" $clientargs -- "$server" $display $serverargs
If you read the manual for xinit you may discover your own tricks for modifying this.

Powered by Obarun