I have updated my (XFCE) system, and I am unable to boot my system.
In the meanwhile, chroot and Timeshift has allowed me to roll back to a previously working configuration.

While updating, I answered yes to this:
66-0.7.0.1-2 and s6-rc-0.5.3.1-1 are in conflict. Remove s6-rc? [y/N]

While updating, I noticed the following message:
boot@: warning: Please reconfigure your boot@system service by using the following command as root user before rebooting:
66 reconfigure boot@system

I ran "sudo 66 reconfigure boot@system" before rebooting:
tree: info: Created successfully tree: global
tree: info: Enabled successfully tree: global
tree: info: Permissions rules set successfully for tree: global
reconfigure: fatal: services selection is not available -- have you already parsed a service?

I suspect the final line is related to my inability to reboot, as I was told this upon rebooting:
[Starts stage1 process...]
tree: fatal: invalid tree name: boot: No such file or directory
Give root password for maintenance
(or press Control-D to continue):

Just wondering how I can resolve this and update without rendering my system unbootable?
I would prefer being able to resolve the reconfigure issue before rebooting, as opposed to ignoring it (as I did) and trying to resolve it through the tty.

Thank you for letting me know!

I ran the following commands (while replacing oblive with my username, hyperspace):
$ mkdir -p ${HOME}/migration-backup/{etc,var/lib,usr/lib}/66
$ mkdir -p ${HOME}/migration-backup/user/hyperspace
$ sudo -E cp -rT /etc/66 ${HOME}/migration-backup/etc/66
$ sudo -E cp -rT /var/lib/66 ${HOME}/migration-backup/var/lib/66
$ sudo -E cp -rT /usr/lib/66 ${HOME}/migration-backup/usr/lib/66
$ cp -r ${HOME}/.66 ${HOME}/migration-backup/user/hyperspace/

Then, I also downloaded the latest packages (had to get s6-rc separately from obarchive) and made a list of my current services:
$ sudo pacman -Sw base skalibs execline s6 s6-rc s6-portable-utils s6-linux-utils s6-networking oblibs 66 66-tools oblog consolekit obsysusers
$ sudo -E 66-intree -o name,enabled,start,contents > ${HOME}/migration-backup/root-services.list

However, trying to backup my user tree gave me the error:
$ 66-intree -o name,enabled,start,contents > ${HOME}/migration-backup/user-services.list
66-intree: fatal: unable to get source service file at: /home/hyperspace/.66/system/.resolve/servicedirs/.resolve: No such file or directory

And it seems that my user tree was replaced with ".resolve".
Rebooting my system at this point gave no issue, as my system seems to start up fine.
$ 66-intree -zg
Name : .resolve
Initialized : no
Enabled : no
Starts after : None
Current : no
66-intree: fatal: unable to get permissions of tree at: /home/hyperspace/.66/system/.resolve/rules: No such file or directory

However, repeatedly rebooting and running the "66-intree -zg" command keeps giving me this ".resolve" tree, instead of my user tree, despite everything running fine upon each reboot.
How do I access my current user tree again and back it up?
Or could I be misunderstanding something?

  • eric replied to this.

    Hyperspace Then, I also downloaded the latest packages (had to get s6-rc separately from obarchive) and made a list of my current services:
    $ sudo pacman -Sw base skalibs execline s6 s6-rc s6-portable-utils s6-linux-utils s6-networking oblibs 66 66-tools oblog consolekit obsysusers
    $ sudo -E 66-intree -o name,enabled,start,contents > ${HOME}/migration-backup/root-services.list

    This is wrong. 66 is now an independent service manager. S6-rc was dropped and enter now in conflicts with 66. Please follow the instructions without assuming error on it. The instructions was tested by many users and for now, nobody reported it that it not working.

    Hyperspace $ 66-intree -o name,enabled,start,contents > ${HOME}/migration-backup/user-services.list
    66-intree: fatal: unable to get source service file at: /home/hyperspace/.66/system/.resolve/servicedirs/.resolve: No such file or directory

    You seem to have a corrupted 66 home user directory. Can you please send me an archive of your ~/.66 directory at eric@obarun.org?

    It could very well be an issue with my home directory.
    I have emailed you an archive of my ~/.66 folder.
    Thank you for your offer to help, and I look forward to your guidance here, on helping me migrate.

    • Edited

    Ok, so this is strange your ~/.66 seems to be a mix between the old and new version of 66. Did you have made your backup before upgrading the package?

    Anyway, to get your old HOME directory working again, simply remove the following components:

    • ~/.66/system/.resolve directory entirely.
    • ~/.66/system/service directory entirely.

    and you should be able to use your HOME directory with the previous version of 66.

    Thank you for your guidance, I have updated my system with the new 66!

    However, there are 3 2 caveats I have noticed upon rebooting, which may be related to my personal error:

    1. Autologin no longer works, and I need to manually type my username, password and then run "startx" to get into XFCE.
    2. (RESOLVED) In Thunar, I am no longer able to eject USB drives, nor click to mount them, and I am told "not authorized to perform operation".
    3. The Network Manager Applet in the XFCE tray states that "networking is disabled" and that "NetworkManager is not running", despite my internet working fine on wired Ethernet (e.g. pacman updates and the browser). I lose internet access if I unplug the cable, since I can't use wireless if NetworkManager isn't working.

    Just wondering if anyone might know what I have done wrongly?
    Below are my trees, if it helps.

    Name        : boot
    Current     : no
    Enabled     : no
    Allowed     : root
    Groups      : boot
    Depends     : \
                  └─None
    Required by : \
                  └─None
    Contents    : \
                  ├─boot@system:mount-proc (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:system-hostname (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-run (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-tmp (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:system-sysctl (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:udevd-log (pid=371, state=Enabled, type=classic, tree=boot)
                  ├─boot@system:tty-earlier@tty12 (pid=287, state=Enabled, type=classic, tree=boot)
                  ├─boot@system (pid=up, state=Enabled, type=module, tree=boot)
                  ├─boot@system:mount-sys (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:populate-run (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:populate-tmp (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-dev (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:populate-sys (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-shm (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-pts (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:populate-dev (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-cgroups (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-branch (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:system-hwclock (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:modules-kernel (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:system-random (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:modules-system (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:udevd (pid=557, state=Enabled, type=classic, tree=boot)
                  ├─boot@system:udevadm (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:system-fontnkey (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:system-fsck (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-fstab (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:system-branch (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-rw (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-netfs (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:local-loop (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:local-sethostname (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:local-time (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:local-authfiles (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:local-tmpfiles (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:local-dmesg (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:local-branch (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:runtime-branch (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:canopy (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:tty-rc@tty2 (pid=1108, state=Enabled, type=classic, tree=boot)
                  └─boot@system:tty-rc@tty1 (pid=1107, state=Enabled, type=classic, tree=boot)
    
    Name        : global
    Current     : no
    Enabled     : yes
    Allowed     : root
    Groups      : admin
    Depends     : \
                  └─None
    Required by : \
                  └─session (Enabled)
    Contents    : \
                  ├─wpa_supplicant-log (pid=1057, state=Enabled, type=classic, tree=global)
                  ├─dbus-log (pid=959, state=Enabled, type=classic, tree=global)
                  ├─consolekit-log (pid=960, state=Enabled, type=classic, tree=global)
                  ├─connmand-log (pid=961, state=Enabled, type=classic, tree=global)
                  ├─openntpd-log (pid=962, state=Enabled, type=classic, tree=global)
                  ├─networkmanager-log (pid=1059, state=Enabled, type=classic, tree=global)
                  ├─wpa_supplicant (pid=0, state=Enabled, type=classic, tree=global)
                  ├─dbus (pid=973, state=Enabled, type=classic, tree=global)
                  ├─openntpd (pid=975, state=Enabled, type=classic, tree=global)
                  ├─consolekit (pid=992, state=Enabled, type=classic, tree=global)
                  ├─connmand (pid=993, state=Enabled, type=classic, tree=global)
                  └─networkmanager (pid=0, state=Enabled, type=classic, tree=global)
    
    Name        : session
    Current     : no
    Enabled     : yes
    Allowed     : root
    Groups      : admin
    Depends     : \
                  └─global (Enabled)
    Required by : \
                  └─None
    Contents    : \
                  ├─scandir@hyperspace:setenv@hyperspace (pid=up, state=Enabled, type=oneshot, tree=session)
                  ├─scandir@hyperspace:svscan@hyperspace-log (pid=1056, state=Enabled, type=classic, tree=session)
                  ├─scandir@hyperspace (pid=up, state=Enabled, type=module, tree=session)
                  ├─boot-user@hyperspace:mount-run@hyperspace (pid=up, state=Enabled, type=oneshot, tree=session)
                  ├─scandir@hyperspace:svscan@hyperspace (pid=1080, state=Enabled, type=classic, tree=session)
                  └─boot-user@hyperspace (pid=up, state=Enabled, type=module, tree=session)
    
    Name        : global
    Current     : no
    Enabled     : yes
    Allowed     : hyperspace
    Groups      : user
    Depends     : \
                  └─None
    Required by : \
                  └─None
    Contents    : \
                  ├─dbus@hyperspace-log (pid=1322, state=Enabled, type=classic, tree=global)
                  ├─xdg-user-dirs (pid=up, state=Enabled, type=oneshot, tree=global)
                  ├─pulseaudio-log (pid=1323, state=Enabled, type=classic, tree=global)
                  ├─dbus@hyperspace (pid=1330, state=Enabled, type=classic, tree=global)
                  └─pulseaudio (pid=1331, state=Enabled, type=classic, tree=global)

    My .xsession file in my home looks like this.
    "66-all up" is deprecated, but I am not sure how to change it, or if it's even related to any of my issues, since switching it with "66 tree start" didn't resolve issue 1 nor 3:

    list=( $(ls -A1 /home/hyperspace/.66/conf/svscan@hyperspace) )
    for i in ${list[@]};do
        var=( $(</home/hyperspace/.66/conf/svscan@hyperspace/${i}) )
        for j in ${var[@]}; do
            export ${j}
        done
    done
    
    66-all up

    For issue 1:
    I have used this thread in the past (https://forum.obarun.org/d/1345-autologin-and-starting-x-wmde-without-a-dm) to enable autologin, but I am not sure how to do it on the new 66 system.

    For issue 2 (RESOLVED):
    I managed to resolve my issue by adding "dbus-run-session" to the "cmd=" line like this, to my home's .xinitrc:

    #!/usr/bin/bash
    
    if [ -d /etc/X11/xinit/xinitrc.d ] ; then
     for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
      [ -x "$f" ] && . "$f"
     done
     unset f
    fi
    
    list=( $(ls -A1 /home/hyperspace/.66/conf/svscan@hyperspace | sort) )
    for i in ${list[@]};do
        var=( $(</home/hyperspace/.66/conf/svscan@hyperspace/${i}) )
        for j in ${var[@]}; do
            export ${j}
        done
    done
    
    66 tree start
    
    ## Try consolekit
    if 66-which -q ck-launch-session; then
        cmd="exec ck-launch-session dbus-run-session $@"
    else
        cmd="exec $@"
    fi
    
    ## Select the session to start
    ${cmd} xfce4-session

    For issue 3:
    Using "66 disable/enable", "66 restart", and "66 start" on networkmanager and wpa_supplicant has no effect, despite no errors reported.
    Rebooting the PC doesn't resolve the issue either.

    what does

    66 -z status networkmanager -g

    (or is it NetworkManager?) says;

    "sudo 66 -z status networkmanager -g" says the following:

    Name                  : networkmanager
    Version               : 0.7.0
    In tree               : global
    Status                : enabled, down (exitcode 1) 0 seconds, normally up, want up, ready 0 seconds
    Type                  : classic
    Description           : networkmanager daemon
    Part of               : None
    Notify                : 0
    Max death             : 5
    Earlier               : 0
    Source                : /usr/share/66/service/networkmanager
    Live                  : /run/66/scandir/0/networkmanager
    Dependencies          : dbus-log networkmanager-log dbus
    Required by           : None
    Contents              : None
    Optional dependencies : None
    Start script          : 
                            #!/usr/bin/execlineb -P
                            /usr/bin/fdmove -c 2 1
                            execl-envfile -v4 /etc/66/conf/networkmanager/version
                             /usr/bin/execl-cmdline -s { /usr/bin/NetworkManager ${Args} } 
    Stop script           : 
                            None
    Environment source    : /etc/66/conf/networkmanager/0.7.0
    Environment file      : 
                            environment variables from: /etc/66/conf/networkmanager/0.7.0/.networkmanager
                            Args=!-n --debug
    
    Log name              : networkmanager-log
    Log destination       : /var/log/66/networkmanager
    Log file              : 
    <info>  [1715610542.2819] manager: Networking is enabled by state file
    <info>  [1715610542.2821] settings: Loaded settings plugin: keyfile (internal)
    <info>  [1715610542.2854] dhcp: init: Using DHCP client 'dhclient'
    <info>  [1715610542.2857] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
    <info>  [1715610542.2861] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
    <info>  [1715610542.2865] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
    <info>  [1715610542.2872] device (lo): Activation: starting connection 'lo' (b2786524-e120-4379-89f1-1cb19e2f0915)
    <info>  [1715610542.2878] device (enp4s0f1): carrier: link connected
    <info>  [1715610542.2881] manager: (enp4s0f1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
    <info>  [1715610542.2886] device (enp4s0f1): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
    <info>  [1715610542.2892] device (enp4s0f1): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
    <info>  [1715610542.2903] device (enp4s0f1): Activation: starting connection 'enp4s0f1' (8062da30-20f9-470f-b101-d16bcfa6a4e0)
    <info>  [1715610542.2908] device (wlp3s0): driver supports Access Point (AP) mode
    <info>  [1715610542.2916] manager: (wlp3s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
    <info>  [1715610542.2920] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
    <info>  [1715610542.2926] device (wlp3s0): set-hw-addr: set MAC address to 1E:A1:13:23:38:0C (scanning)
    <error> [1715610542.2934] bus-manager: fatal failure to acquire D-Bus service "org.freedesktop.NetworkManager" (3). Service already taken
    <info>  [1715610542.2942] device (wlp3s0): state change: unavailable -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed')
    <info>  [1715610542.2945] device (wlp3s0): set-hw-addr: reset MAC address to 0C:8B:FD:3D:DE:CF (unmanage)
    <info>  [1715610542.2983] exiting (error)

    On the other hand, "sudo 66 -z status wpa_supplicant -g" says the following:

    Name                  : wpa_supplicant
    Version               : 0.7.0
    In tree               : global
    Status                : enabled, down (exitcode 255) 0 seconds, normally up, want up, ready 0 seconds
    Type                  : classic
    Description           : wpa_supplicant daemon
    Part of               : None
    Notify                : 0
    Max death             : 5
    Earlier               : 0
    Source                : /usr/share/66/service/wpa_supplicant
    Live                  : /run/66/scandir/0/wpa_supplicant
    Dependencies          : wpa_supplicant-log
    Required by           : None
    Contents              : None
    Optional dependencies : None
    Start script          : 
                            #!/usr/bin/execlineb -P
                            /usr/bin/fdmove -c 2 1
                            execl-envfile -v4 /etc/66/conf/wpa_supplicant/version
                             /usr/bin/execl-cmdline -s { /usr/bin/wpa_supplicant ${Args} } 
    Stop script           : 
                            None
    Environment source    : /etc/66/conf/wpa_supplicant/0.7.0
    Environment file      : 
                            environment variables from: /etc/66/conf/wpa_supplicant/0.7.0/.wpa_supplicant
                            Args=!-udW
    
    Log name              : wpa_supplicant-log
    Log destination       : /var/log/66/wpa_supplicant
    Log file              : 
    wpa_supplicant v2.10
    dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
    dbus: Could not request service name: already registered
    Failed to initialize wpa_supplicant
    wpa_supplicant v2.10
    dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
    dbus: Could not request service name: already registered
    Failed to initialize wpa_supplicant
    wpa_supplicant v2.10
    dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
    dbus: Could not request service name: already registered
    Failed to initialize wpa_supplicant
    wpa_supplicant v2.10
    dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
    dbus: Could not request service name: already registered
    Failed to initialize wpa_supplicant
    wpa_supplicant v2.10
    dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
    dbus: Could not request service name: already registered
    Failed to initialize wpa_supplicant

    They both seem to indicate D-Bus being the issue, though D-Bus is already running on my global root and user trees (output above on post #7).

    Do you usually have connmand and network manager running at the same time?

    ok i switched to networkmanager hours ago (been using connmand) and after a restart this morning, internet was down.

    66 -z tree status -g shows that some services were down (consolekit, networkmanager, wpa_supplicant). there was also a lingering copy of connmand service, even if i already run 66 remove connmand. so removed connmand, again. and removed networkmanager. restarted and everything is fine. i think you dont need wpa_supplicant when using networkmanager (anyone correct me in this, it might be needed on something).

    Maybe the backend has switched to iwd? unless wpa_supplicant still shows up in the active processes showing that it was started without 66.

    It turns out that removing "connmand" from the tree allows "networkmanager" to work normally!
    Wireless internet is also usable again from the Network Manager Applet.

    My tree now looks like this, as reference:

    Name        : global
    Current     : no
    Enabled     : yes
    Allowed     : root
    Groups      : admin
    Depends     : \
                  └─None
    Required by : \
                  └─session (Enabled)
    Contents    : \
                  ├─dbus-log (pid=932, state=Enabled, type=classic, tree=global)
                  ├─consolekit-log (pid=931, state=Enabled, type=classic, tree=global)
                  ├─openntpd-log (pid=936, state=Enabled, type=classic, tree=global)
                  ├─networkmanager-log (pid=1987, state=Enabled, type=classic, tree=global)
                  ├─dbus (pid=942, state=Enabled, type=classic, tree=global)
                  ├─openntpd (pid=945, state=Enabled, type=classic, tree=global)
                  ├─consolekit (pid=961, state=Enabled, type=classic, tree=global)
                  └─networkmanager (pid=1982, state=Enabled, type=classic, tree=global)

    A random online search says that "networkmanager" is already a wrapper around "wpa_supplicant".
    Thus, running wpa_supplicant yet again is not necessary, as networkmanager already bundles it together.
    "iwd" seems to be an alternative to wpa_supplicant, that can also work within networkmanager.

    In practice, disabling the wpa_supplicant service (and connmand) from my system while leaving only networkmanager running, has no noticable ill effects so far.

    Your comments have been helpful in providing further clues for me to troubleshoot this issue.
    Thank you!

    For now, I'll mark this topic as solved, since I technically can boot my system now upon updating.
    I'll ask about configuring DM-free autologin in XFCE, in a separate thread.

    Powered by Obarun