I don't update my system very often, but for the first time this year I got around to it this week. The machine doesn't get rebooted if I can help it, it always has something useful to do. And I didn't check the Obarun news before I executed sudo pacman -Syu.

The result is that my old trusted commands like 66-intree don't function anymore. And in reading up on what is going on, it dawned on me that there is a big migration going on, that I accidentally put my machine through.

The migration instructions seem to have to start off from a system that has not been upgraded yet.

How do I get a listing of my trees if I already upgraded the 66 suite? How do I migrate properly if I upgraded 66 before making the backups that the migration instructions so wisely recommend?

    I had found those, they're great resources but they don't actually solve my problem.

    My current situation is that my computer booted with the previous version of 66, it's still running fine, all daemons are doing their job, but through 66 commands I can't find my trees or my daemon configurations. It seems new 66 is blind to the old 66 configuration. If I am to migrate, I have to look up how I got things to work the first time, and I seem to be unable to do that using 66 commands now.

    Plus: I wonder what I may have f*d up by not going through the migration recipe, and need to fix now.

    i'm guessing that your /etc/66 might be a bit a of mess now, with a mix of old and new files, i would think that original stuff is still there..
    pacman -Qo <file> might help in finding what is owned by the new 66 and what isn't, presumably is an old file..
    you might be able to ascertain what you current services are by looking in (maybe) /etc/66/service ..not sure now, it seems i've deleted the backup i made during the migration..
    and ~/.66 for any user services you might have.

    another approach, might be, if you have the old 66 version in pkg cache, try downgrading 66, and then do the migration as per the instructions:
    https://news.obarun.org/2024/03/25/66-migration-instructions/

    You should still have the directory /var/lib/66/system directory. The new version contains all its need at /var/lib/system/66/service. So all others directories than service found at /var/lib/66/system concern the old version.
    For example you will see /var/lib/66/system/boot. This directory contains all services previously used for your boot tree. Same for i.e. /var/lib/66/system/root directory.
    Inside i.e. /var/lib/66/system/root directory you will find the servicedirs/db/source which contains atomic service(A.K.A. bundles, longrun) previously used at root tree. You will also find the svc directoy which contains all your previous classic service.
    Theses can not be used but at least you know what your previous system used as services.

    You also will see the file /var/lib/66/system/state file. This file contains the name of all trees enabled previously in the order of start. The firs one is the tree first started tree at boot time.

    This is the exact same structure for user services and trees.

    You can also take a look at /etc/66/conf which contains all previous configuration used by the services. This directory is also used with the new version and the migration instructions under the sections Red line or keeping the old to the new explain how to import the previous service configuration.

    The frontend service are now located at /usr/share/66/service. The previous version used /usr/lib/66/service. So you should still have the old frontend file at /usr/lib/66/service. You can use this frontend (taking care about the change see https://web.obarun.org/software/66/0.7.0.1/66-upgrade.html) transferring these file from /usr/lib/66/service to /usr/share/66/service. This is only concern your personal service, service coming from observice should be up to date when you have installed the new version of 66 and the services.
    The /etc/66/service or $HOME/.66 directory for sysadmin service remain unchanged and still used by the new version.

    @ncmprhnsbl has right. Maybe the best way for you is to downgrade your system and make the migration correctly following the instructions provided.

    11 days later

    After some attempts to downgrade, I've come to the conclusion that somehow I don't have any old caches for 66. Is there an Obarun archive server, analogous to Server=https://archive.archlinux.org/repos/2023/04/11/$repo/os/$arch where I could get the old version?

    Should be:

    [obarchive]
    Server = https://cloud.server.obarun.org/$repo/os/$arch/

    if you want to to add it to your pacman.conf. or you can browse it

    @Wat-now
    This will not work.

    @Lijsterbes
    You can found archive here https://cloud.server.obarun.org/browse/
    Select the obarchive repo in the drop-down menu and click to the list button.

    You can obviously install the pacman through pacman. For instance to install the 0.6.2.0-1 version of 66 :

    # pacman -U https://cloud.server.obarun.org/obarchive/package/6/66/66-0.6.2.0-1-x86_64.pkg.tar.xz
    2 months later

    After trying to downgrade 66, the PC froze and got into a non-bootable state.
    I tried to get Obarun running again several times [whenever work and family permitted], but no joy.

    I wrote a rambling post asking for help in making my system bootable again, but that has become irrelevant - I've managed to make some progress, so I'm editing out all the irrelevant stuff from this post

    As it turned out, trying to downgrade broke a lot of packages. I restored the packages by chrooting from a liveUSB, and I set up the 66 ecosystem as best I could using the Migration guide, and it's not crashing in the same way it was before.

    Right now, the initial boot seems to go fine until I get to the point where it throws mount-swap: fatal: unable to activate the swap! at me and freezes.

    I have SWAP=!yes enabled in my boot.conf, edited in the canonical way using sudo 66 configure -e nano boot@system, with a sudo 66 reconfigure boot@system performed immediately after [no errors reported], I have a known-good fstab which contains a swap partition, I can't see where this is going wrong.

    Does anyone have hints or thoughts?

    • Edited

    the mount-swap service do at start process swapon -a and at stop process swapoff -a. Try to do it manually from e.g. tty12. And tell us what happens.
    Also, you can get log at /run/66/log/mount-swap and /run/66/log/0. Maybe you will find something relevant.

    I never even considered using tty12 when the boot messages on tty1 froze; it worked! As it turns out, somehow the UUID of the swap partition had changed from the one listed in fstab - bizarrely. After fixing fstab, the system now boots again. Very well done! One big step closer to things working as they used to.

    I do run into some issues though: the boot sequence is notably slower than it was before migrating, and my wifi refuses to come up. I'm surprised, because I think I set everything up in the same way that it used to be. I didn't change any configs since everything worked, and I think I enabled all the same services as before.

    Also, Double Commander complains that it Failed to create named pipe: /run/user/1000/doublecmd.pipe, which is puzzling to me - no clue what this means. And disk access as a whole seems off: my backgrounds in LXDE are all blank now. Does this add up to some single thing I'm doing wrong?

    Please post the output of the following command as root and regular user:

    66 tree status -g

    First some good news: my network is up! It turned out that a oneshot rc file that I need to get my WiFi card running wasn't launching, but now it is - and I have network. Since I did that, also the boot sequence has sped up significantly. Progress!

    Double Commander is still crashing due to the pipe problem though, and my wallpapers are still missing.

    My outputs:

    [lijster@lijsterbes ~]$ 66 tree status -g
    Name        : global
    Current     : no
    Enabled     : yes
    Allowed     : lijster
    Groups      : user
    Depends     : \
                  └─None
    Required by : \
                  └─None
    Contents    : \
                  └─None
    
    [lijster@lijsterbes ~]$ sudo 66 tree status -g
    Name        : global
    Current     : no
    Enabled     : yes
    Allowed     : root
    Groups      : admin
    Depends     : \
                  └─None
    Required by : \
                  └─session (Enabled)
    Contents    : \
                  ├─dhcpcd-log (pid=946, state=Enabled, type=classic, tree=global)
                  ├─dbus-log (pid=942, state=Enabled, type=classic, tree=global)
                  ├─consolekit-log (pid=955, state=Enabled, type=classic, tree=global)
                  ├─openntpd-log (pid=950, state=Enabled, type=classic, tree=global)
                  ├─alsa-log (pid=953, state=Enabled, type=classic, tree=global)
                  ├─rclite (pid=up, state=Enabled, type=oneshot, tree=global)
                  ├─wpa_supplicant-log (pid=3020, state=Enabled, type=classic, tree=global)
                  ├─dhcpcd (pid=968, state=Enabled, type=classic, tree=global)
                  ├─dbus (pid=966, state=Enabled, type=classic, tree=global)
                  ├─openntpd (pid=978, state=Enabled, type=classic, tree=global)
                  ├─alsa (pid=976, state=Enabled, type=classic, tree=global)
                  ├─wpa_supplicant (pid=3835, state=Enabled, type=classic, tree=global)
                  └─consolekit (pid=1005, state=Enabled, type=classic, tree=global)
    
    Name        : boot-user
    Current     : no
    Enabled     : no
    Allowed     : root
    Groups      : admin
    Depends     : \
                  └─None
    Required by : \
                  └─None
    Contents    : \
                  ├─boot-user@lijster:mount-run@lijster (pid=unitialized, state=Enabled, type=oneshot, tree=boot-user)
                  ├─scandir@lijster (pid=up, state=Enabled, type=module, tree=session)
                  ├─scandir@lijster:setenv@lijster (pid=up, state=Enabled, type=oneshot, tree=session)
                  ├─scandir@lijster:svscan@lijster-log (pid=1064, state=Enabled, type=classic, tree=session)
                  ├─boot-user@lijster (pid=unitialized, state=Enabled, type=module, tree=boot-user)
                  └─scandir@lijster:svscan@lijster (pid=1086, state=Enabled, type=classic, tree=session)
    
    Name        : boot
    Current     : no
    Enabled     : no
    Allowed     : root
    Groups      : boot
    Depends     : \
                  └─None
    Required by : \
                  └─None
    Contents    : \
                  ├─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:mount-proc (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=335, state=Enabled, type=classic, tree=boot)
                  ├─boot@system:tty-earlier@tty12 (pid=250, state=Enabled, type=classic, tree=boot)
                  ├─boot@system (pid=up, state=Enabled, type=module, 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-sys (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:populate-sys (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-dev (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-pts (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-shm (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=538, 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:local-time (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-tmpfiles (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:local-authfiles (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-swap (pid=up, state=Enabled, type=oneshot, tree=boot)
                  ├─boot@system:mount-netfs (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@tty1 (pid=1119, state=Enabled, type=classic, tree=boot)
                  ├─boot@system:tty-rc@tty2 (pid=1117, state=Enabled, type=classic, tree=boot)
                  ├─boot@system:tty-rc@tty3 (pid=1127, state=Enabled, type=classic, tree=boot)
                  ├─boot@system:tty-rc@tty4 (pid=1126, state=Enabled, type=classic, tree=boot)
                  ├─boot@system:tty-rc@tty5 (pid=1125, state=Enabled, type=classic, tree=boot)
                  ├─boot@system:tty-rc@tty6 (pid=1120, state=Enabled, type=classic, tree=boot)
                  └─boot@system:tty-rc@tty7 (pid=1123, state=Enabled, type=classic, tree=boot)
    
    Name        : session
    Current     : no
    Enabled     : yes
    Allowed     : root
    Groups      : admin
    Depends     : \
                  └─global (Enabled)
    Required by : \
                  └─None
    Contents    : \
                  ├─scandir@lijster:setenv@lijster (pid=up, state=Enabled, type=oneshot, tree=session)
                  ├─scandir@lijster:svscan@lijster-log (pid=1064, state=Enabled, type=classic, tree=session)
                  ├─scandir@lijster (pid=up, state=Enabled, type=module, tree=session)
                  └─scandir@lijster:svscan@lijster (pid=1086, state=Enabled, type=classic, tree=session)

    I would like to thank you for your ceaseless attention to this awesome distro, and for helping clueless users like me.

    • Edited

    try to enable the dbus service for your regular user.
    To do so (as regular user)

    $ 66 enable -S dbus@lijster

    This will enable the dbus@lijster service and start it right now. Maybe you need to reboot, it should not be mandatory but dbus... is dbus :).
    How do you start your Double Commander?

    Done! But no result, and the service seems not to be happy:

    [lijster@lijsterbes ~]$ 66 status dbus@lijster
    Name                  : dbus@lijster
    Version               : 0.7.0
    In tree               : global
    Status                : enabled, down (exitcode 111) 0 seconds, want up, ready 0 seconds
    Type                  : classic
    Description           : dbus session daemon for lijster user
    Part of               : None
    Notify                : 4
    Max death             : 3
    Earlier               : 0
    Source                : /usr/share/66/service/user/dbus@lijster
    Live                  : /run/66/scandir/1000/dbus@lijster
    Dependencies          : dbus@lijster-log
    Required by           : None
    Contents              : None
    Optional dependencies : None
    Start script          : 
                            #!/usr/bin/execlineb -P
                            /usr/bin/fdmove -c 2 1
                            execl-envfile -v4 /home/lijster/.66/conf/dbus@lijster/version
                                /usr/bin/execl-subuidgid -o lijster
                                /usr/bin/execl-toc -S ${Socket}
                                /usr/bin/execl-cmdline -s { /usr/bin/dbus-daemon ${Args} }
    Stop script           : 
                            #!/usr/bin/execlineb -P
                            /usr/bin/fdmove -c 2 1
                            execl-envfile -v4 /home/lijster/.66/conf/dbus@lijster/version
                                /usr/bin/execl-subuidgid -o lijster
                                /usr/bin/s6-rmrf ${Socket}
    Environment source    : /home/lijster/.66/conf/dbus@lijster/0.7.0
    Environment file      : environment variables from: /home/lijster/.66/conf/dbus@lijster/0.7.0/.dbus@lijster
                            Args=!--session --print-pid=4 --nofork --nopidfile --address=unix:path=${Socket}
                            Socket=!/run/user/${UID}/bus
    
    Log name              : dbus@lijster-log
    Log destination       : /home/lijster/.66/log/dbus@lijster
    Log file              : 
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    execl-toc: fatal: unable to create dir: /run/user/1000/: Permission denied
    • Edited

    have you rebooted?
    get it, do this as root

    66 tree enable boot-user
    66 tree admin -o depends=global boot-user
    66 tree admin -o depends=boot-user session

    then reboot

    Done that, rebooted:
    Everything is running as usual, buttery smooth! Very impressed. Not just by how smooth the system is performing right now, but also that you manage to tell me the commands I need from the rambling ignorance I write down in this thread. That's a rare skill!

    • Edited

    great news!
    you also can simplify a little bit your setup by doing the following (as root):

    # 66 -t session enable boot-user@lijster
    # 66 tree remove boot-user

    This will switch the boot-user@lijster service to the tree session and remove the tree session.

    When I do that and reboot, suddenly I have my dbus problems back:

    [lijster@lijsterbes ~]$ 66 status dbus@lijster
    Name                  : dbus@lijster
    Version               : 0.7.0
    In tree               : global
    Status                : enabled, None
    Type                  : classic
    Description           : dbus session daemon for lijster user
    Part of               : None
    Notify                : 4
    Max death             : 3
    Earlier               : 0
    Source                : /usr/share/66/service/user/dbus@lijster
    Live                  : /run/66/scandir/1000/dbus@lijster
    Dependencies          : dbus@lijster-log
    Required by           : None
    Contents              : None
    Optional dependencies : None
    Start script          : 
                            #!/usr/bin/execlineb -P
                            /usr/bin/fdmove -c 2 1
                            execl-envfile -v4 /home/lijster/.66/conf/dbus@lijster/version
                                /usr/bin/execl-subuidgid -o lijster
                                /usr/bin/execl-toc -S ${Socket}
                                /usr/bin/execl-cmdline -s { /usr/bin/dbus-daemon ${Args} }
    Stop script           : 
                            #!/usr/bin/execlineb -P
                            /usr/bin/fdmove -c 2 1
                            execl-envfile -v4 /home/lijster/.66/conf/dbus@lijster/version
                                /usr/bin/execl-subuidgid -o lijster
                                /usr/bin/s6-rmrf ${Socket}
    Environment source    : /home/lijster/.66/conf/dbus@lijster/0.7.0
    Environment file      : environment variables from: /home/lijster/.66/conf/dbus@lijster/0.7.0/.dbus@lijster
                            Args=!--session --print-pid=4 --nofork --nopidfile --address=unix:path=${Socket}
                            Socket=!/run/user/${UID}/bus
    
    Log name              : dbus@lijster-log
    Log destination       : /home/lijster/.66/log/dbus@lijster
    Log file              : 
    dbus-daemon[1236]: [session uid=1000 pid=1236] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
    dbus-daemon[1236]: [session uid=1000 pid=1236] Successfully activated service 'org.freedesktop.portal.Documents'
    
    (/usr/lib/xdg-desktop-portal:1417): xdg-desktop-portal-WARNING **: 11:00:17.402: Failed to load RealtimeKit property: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.RealtimeKit1 was not provided by any .service files
    
    (/usr/lib/xdg-desktop-portal:1417): xdg-desktop-portal-WARNING **: 11:00:17.402: Failed to load RealtimeKit property: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.RealtimeKit1 was not provided by any .service files
    
    (/usr/lib/xdg-desktop-portal:1417): xdg-desktop-portal-WARNING **: 11:00:17.402: Failed to load RealtimeKit property: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.RealtimeKit1 was not provided by any .service files
    
    (/usr/lib/xdg-desktop-portal:1417): xdg-desktop-portal-WARNING **: 11:00:17.403: No skeleton to export
    dbus-daemon[1236]: [session uid=1000 pid=1236] Successfully activated service 'org.freedesktop.portal.Desktop'
    dbus-daemon[1408]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=1287 comm="lxterminal")
    dbus-daemon[1408]: Successfully activated service 'org.a11y.atspi.Registry'
    SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    dbus-daemon[1236]: [session uid=1000 pid=1236] Activating service name='ca.desrt.dconf' requested by ':1.87' (uid=1000 pid=8087 comm="veracrypt")
    dbus-daemon[1236]: [session uid=1000 pid=1236] Successfully activated service 'ca.desrt.dconf'
    X connection to :0 broken (explicit kill or server shutdown).
    A connection to the bus can't be made
    A connection to the bus can't be made
    A connection to the bus can't be made

    Consolekit isn't happy either:

    [lijster@lijsterbes ~]$ sudo 66 status consolekit
    [sudo] password for lijster: 
    Name                  : consolekit
    Version               : 0.7.0
    In tree               : global
    Status                : enabled, up (pid 1006 pgid 1006) 1172 seconds
    Type                  : classic
    Description           : consolekit daemon
    Part of               : None
    Notify                : 0
    Max death             : 5
    Earlier               : 0
    Source                : /usr/share/66/service/consolekit
    Live                  : /run/66/scandir/0/consolekit
    Dependencies          : consolekit-log dbus-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/consolekit/version
                                execl-toc -d ${LiveDirectory}
                                execl-cmdline -s { console-kit-daemon ${Args} }
    Stop script           : 
                            #!/usr/bin/execlineb -P
                            /usr/bin/fdmove -c 2 1
                            execl-envfile -v4 /etc/66/conf/consolekit/version
                             s6-rmrf ${LiveDirectory} 
    Environment source    : /etc/66/conf/consolekit/0.7.0
    Environment file      : environment variables from: /etc/66/conf/consolekit/0.7.0/.consolekit
                            Args=!--no-daemon
                            LiveDirectory=!/run/ConsoleKit
    
                            environment variables from: /etc/66/conf/consolekit/0.7.0/consolekit
                            Args=!--no-daemon
                            LiveDirectory=!/run/ConsoleKit
    
    Log name              : consolekit-log
    Log destination       : /var/log/66/consolekit
    Log file              : 
    console-kit-daemon[984]: WARNING: unable to stat /run/user/1000, reason was: No such file or directory
    missing action
    
    console-kit-daemon[1008]: WARNING: unable to stat /run/user/1000, reason was: No such file or directory
    missing action
    
    console-kit-daemon[1005]: WARNING: unable to stat /run/user/1000, reason was: No such file or directory
    console-kit-daemon[1005]: WARNING: unable to stat /run/user/1000, reason was: No such file or directory
    console-kit-daemon[1005]: WARNING: unable to stat /run/user/1000, reason was: No such file or directory
    missing action
    
    console-kit-daemon[1005]: WARNING: unable to stat /run/user/1000, reason was: No such file or directory
    missing action
    
    missing action
    
    console-kit-daemon[1004]: WARNING: unable to stat /run/user/1000, reason was: No such file or directory
    missing action
    
    console-kit-daemon[1006]: WARNING: unable to stat /run/user/1000, reason was: No such file or directory

    I do have 2 more things I notice [although those aren't system-breaking problems]:

    1) I run a simple script as part of the boot process. It always worked in the past, and it is being started by a custom one-shot. It runs, this is confirmed because one of the things it does is play a sound when the machine is ready to be logged into. However, it also tries to write values to /sys/class/power_supply/BAT0/charge_control_end_threshold and /sys/class/power_supply/BAT0/charge_control_start_threshold and these values don't get written. I can write them as su, and then they persist and function normally. This never was a problem before the migration, it always worked. Is the new 66 not performing the one-shot as root anymore perhaps?

    2) As part of the boot, openntpd starts. It starts fine, but it tries to do its magic before the network is up. As a result, it fails several times, then sits in a corner and pouts. Is there a way to make openntpd wait for the network to be up before starting?

    Thanks!

    OK, Consolekit and dbus are happy again after enabling the session tree and rebooting!

    The other two minor issues still exist though.

    Powered by Obarun