solved*Missing @build=auto causing acpi@66serv 2.0-1 to fail 66-enable

WWat-now · May 28, 2020

I have had trouble with this update which I'm suspecting caused my root tree to reset which I had to rebuild.

# 66-enable acpid
66-enable: fatal: unable to parse service file: /usr/lib/66/service/acpid: or its dependencies

Solution?

Thanks

eric · May 28, 2020

Oops!!

Sorry, my bad
just synchronize again

banned_9-26-2021 · May 28, 2020

alsa-daemon did the same thing - wiped out all services from root and booted without it, when I checked 66-intree it was empty.
alsa-restore is a dependency of alsa-daemon and it does not exist.

~ % sudo 66-enable -t root -S alsa-daemon
66-enable: fatal: unable to parse service file: /usr/lib/66/service/alsa-daemon: or its dependencies

error: failed retrieving file 'acpid-66serv-0.2.0-1-x86_64.pkg.tar.xz' from repo.obarun.org : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

Using the older acpid-66serv from cache makes it work.

eric · May 28, 2020

your post crossed mine. Just sync and update.

eric · May 28, 2020

@ wat-now
i'm curious and i'm not sure to understand the manner you get a broken root tree. Can please you explain me what you did exactly?

WWat-now · May 28, 2020

@ eric

It seemed that when I updated 66 tools & the 2.0 versions of some @ 66-services, then tried to run 66-update without -d option because I assumed it would work like most times,

However, it broke&deleted all services from root tree because the acpid service script could not parse. Is this expected behavior?

Now I'm having trouble starting dbus&classic services after reboot so I cannot boot to gui& tty services have permission issues. I'm trying to troubleshoot to see if it is another fault of my system because before the reboot I had touble with:

 /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1  

(polkit-gnome-authentication-agent-1:14517): polkit-gnome-1-WARNING **: 02:57:05.946: Unable to determine the session we are in: GDBus.Error:org.freedesktop.ConsoleKit.Manager.Error.General: Unable to lookup session information for process '14517'

Following is a reading of my /run/66/log/0/current at failed boot

@ 400000005ecfceb71bd7cd6d [Initiate db of tree boot...]
@ 400000005ecfceb724893932 [Start db services of tree boot...]
@ 400000005ecfceb72d33bd21 [system-hostname] starts...
@ 400000005ecfceb72fba64f9 [system-hostname] started successfully
@ 400000005ecfceb731b2f3c2 [populate-run] starts...
@ 400000005ecfceb732ef2b07 [populate-sys] starts...
@ 400000005ecfceb734055aff [mount-tmp] starts...
@ 400000005ecfceb734fd88df [populate-dev] starts...
@ 400000005ecfceb736e88001 [mount-tmp] started successfully
@ 400000005ecfceb73720a402 [mount-pts] starts...
@ 400000005ecfceb737494a98 [mount-shm] starts...
@ 400000005ecfceb737520160 [populate-tmp] starts...
@ 400000005ecfceb73a930561 [populate-tmp] started successfully
@ 400000005ecfceb73b388797 [devices-zfs] deactivated
@ 400000005ecfceb73b59ac1e [mount-cgroups] starts...
@ 400000005ecfceb80044dd0f [populate-run] started successfully
@ 400000005ecfceb800826c4e [mount-shm] started successfully
@ 400000005ecfceb8009c1e83 [mount-pts] started successfully
@ 400000005ecfceb800ed507c [populate-dev] started successfully
@ 400000005ecfceb802308d23 [populate-sys] started successfully
@ 400000005ecfceb8056802ed [mount-cgroups] started successfully
@ 400000005ecfceb8061c94a0 [system-sysctl] starts...
@ 400000005ecfceb8061df37f [system-random] starts...
@ 400000005ecfceb80664ad61 [modules-kernel] starts...
@ 400000005ecfceb807738b44 [modules-system] starts...
@ 400000005ecfceb807784ab5 [system-hwclock] starts...
@ 400000005ecfceb80a353fc0 [system-random] started successfully
@ 400000005ecfceb80ad21354 kernel.sysrq = 1
@ 400000005ecfceb80ad21bb3 kernel.core_uses_pid = 1
@ 400000005ecfceb80ad22355 fs.protected_hardlinks = 1
@ 400000005ecfceb80ad22962 fs.protected_symlinks = 1
@ 400000005ecfceb80ad22d99 fs.inotify.max_user_instances = 1024
@ 400000005ecfceb80ad231ab fs.inotify.max_user_watches = 524288
@ 400000005ecfceb80aecf83c [system-sysctl] started successfully
@ 400000005ecfceb81228a628 [system-hwclock] started successfully
@ 400000005ecfceb8165eb143 /usr/lib/66/scripts/modules.sh: No modules found -- nothing to do
@ 400000005ecfceb8167ccecb [modules-system] started successfully
@ 400000005ecfceb907dfbc70 [modules-kernel] started successfully
@ 400000005ecfceb908301652 [udevd] starts...
@ 400000005ecfceba09b9026f [udevadm] starts...
@ 400000005ecfcebb35390698 [udevadm] started successfully
@ 400000005ecfcebb35ff6071 [system-fontnkey] starts...
@ 400000005ecfcebb3643cb6c [devices-lvm] deactivated
@ 400000005ecfcebb364e16d3 [devices-crypttab] deactivated
@ 400000005ecfcebb368036eb [devices-btrfs] deactivated
@ 400000005ecfcebb36cf2477 [devices-dmraid] deactivated
@ 400000005ecfcebb3af4d9da [system-fontnkey] started successfully
@ 400000005ecfcebb3b714f72 [system-fsck] starts...
@ 400000005ecfcebc01e432ca Obarun: clean, 476751/3239520 files, 6256724/13003776 blocks
@ 400000005ecfcebc0209e298 [system-fsck] started successfully
@ 400000005ecfcebc0285783e [mount-fstab] starts...
@ 400000005ecfcebc0a9d068d [mount-fstab] started successfully
@ 400000005ecfcebc0afc8f85 [mount-rw] starts...
@ 400000005ecfcebc0b58401b [mount-rw] started successfully
@ 400000005ecfcebc0c4e54de [mount-swap] deactivated
@ 400000005ecfcebc0c7eb94b [local-tmpfiles] starts...
@ 400000005ecfcebc0cc85e00 [local-iptables] deactivated
@ 400000005ecfcebc0cea8c57 [local-time] starts...
@ 400000005ecfcebc0cf3e094 [local-sethostname] starts...
@ 400000005ecfcebc0cfda23d [local-authfiles] starts...
@ 400000005ecfcebc0d15776a [local-ip6tables] deactivated
@ 400000005ecfcebc0d5eee24 [local-authfiles] started successfully
@ 400000005ecfcebc0d747eaf [local-loop] starts...
@ 400000005ecfcebc10d61f3e [local-time] started successfully
@ 400000005ecfcebc122a1c45 [local-loop] started successfully
@ 400000005ecfcebc1279f34f _z /etc/brlapi.key 0640 root brlapi 0 
@ 400000005ecfcebc13575896 _d /var/lib/colord 0755 colord colord 0 
@ 400000005ecfcebc1470f88c _d /var/lib/colord/icc 0755 colord colord 0 
@ 400000005ecfcebc14ae2e11 _d /run/ConsoleKit 0755 0 0 0 
@ 400000005ecfcebc14ef95dc _d /run/dbus 0755 0 0 0 
@ 400000005ecfcebc1530934e _d /srv/deluge 0770 deluge deluge 0 
@ 400000005ecfcebc157147d3 _d /var/lib/dhcpcd 0700 dhcpcd dhcpcd 0 
@ 400000005ecfcebc16625081 _d /run/dhcpcd 0755 dhcpcd dhcpcd 0 
@ 400000005ecfcebc16abe07a _x /run/user/*/gvfs  0 0 0 
@ 400000005ecfcebc16b408ab _z /var/lib/libvirt/qemu 0751 0 0 0 
@ 400000005ecfcebc170ff164 _d /run/lighttpd 755 http http 0 
@ 400000005ecfcebc174bbd5a _d /var/cache/lighttpd 755 http http 10d 
@ 400000005ecfcebc1820e7c5 _w /sys/devices/system/cpu/microcode/reload - 0 0 0 1
@ 400000005ecfcebc182b76bd _d /run/lock/lockdev 0775 root lock 0 
@ 400000005ecfcebc186dea6f _d /var/lib/lxdm 0700 lxdm lxdm 0 
@ 400000005ecfcebc18b3fae5 _d /var/cache/man 0755 root root 1w 
@ 400000005ecfcebc18ea5e5f _d /run/initramfs 0755 root root 0 
@ 400000005ecfcebc191fd31c _d /run/nscd 0755 root root 0 
@ 400000005ecfcebc196341d2 _C /etc/crypttab  0 0 0 
@ 400000005ecfcebc196695c3 _C /etc/fstab  0 0 0 
@ 400000005ecfcebc1969be03 _C /etc/group  0 0 0 
@ 400000005ecfcebc196cae55 _C /etc/gshadow  0 0 0 
@ 400000005ecfcebc196fb855 _C /etc/host.conf  0 0 0 
@ 400000005ecfcebc197341cd _C /etc/hosts  0 0 0 
@ 400000005ecfcebc19764abc _C /etc/issue  0 0 0 
@ 400000005ecfcebc19796aad _C /etc/ld.so.conf  0 0 0 
@ 400000005ecfcebc1a4f0a90 _C /etc/motd  0 0 0 
@ 400000005ecfcebc1a521cd8 _C /etc/nsswitch.conf  0 0 0 
@ 400000005ecfcebc1a553191 _C /etc/passwd  0 0 0 
@ 400000005ecfcebc1a58156f _C /etc/profile  0 0 0 
@ 400000005ecfcebc1a5b255a _C /etc/securetty  0 0 0 
@ 400000005ecfcebc1a5e2b64 _C /etc/shadow  0 0 0 
@ 400000005ecfcebc1a612d60 _C /etc/shells  0 0 0 
@ 400000005ecfcebc1a6b7af7 _d /run/screens 0755 root root 0 
@ 400000005ecfcebc1aad02af _d /var/lib/sddm 0755 sddm sddm 0 
@ 400000005ecfcebc1ae31876 _d /var/empty 0755 root root 0 
@ 400000005ecfcebc1b1c2b86 _d /run/sudo 0711 root root 0 
@ 400000005ecfcebc1b570cbe _D /run/sudo/ts 0700 root root 0 
@ 400000005ecfcebc1b99983a [local-tmpfiles] started successfully
@ 400000005ecfcebc1c15e4f0 [local-rc] starts...
@ 400000005ecfcebd22097063 [local-rc] started successfully
@ 400000005ecfcebd226a3d7d [local-dmesg] starts...
@ 400000005ecfcebd233ac051 [local-dmesg] started successfully
@ 400000005ecfcec032ef81c4 s6-svlisten1: fatal: timed out
@ 400000005ecfcec032fedff7 66-start: fatal: unable to start services selection
@ 400000005ecfcec033037e25 66-all: fatal: unable to start services of tree: root
@ 400000005ecfcec033135f65 66-dbctl: fatal: unable to start services selection
@ 400000005ecfcec0334970c8 rc.init: fatal: please see the log at /run/66/log/0/current

eric · May 28, 2020

It seemed that when I updated 66 tools & the 2.0 versions of some @ 66-services, then tried to run 66-update without -d option because I assumed it would work like most times,

First rule for a dev: Never trust an user
First rule for an user: Never trust a dev
:p
Yeah, you should always use -d option with 66-update. This option is made for this.
Now, i think you misunderstood the purpose of 66-update. 66-update help you to update your system between two version of 66. A new version can have inner format files change and need to be updated, so in that case you use 66-update. But here the update concerns services and 66-tools not the 66 package itself. We are not on Systemd here. I mean, when a service is updated the only thing changed on your system is the frontend file located at /usr/lib/66/service. But your service already in use will not be touched. This is main advantage to use s6/s6-rc. Services are on compiled database and its never touched if you don't ask for it explicitly. You can update a service with pacman and keep an old service on your tree. It doesn't matter.

So, to update a service use the 66-enable tool with the -F option and -c/m/C depending of your need. In you case you just need to do:

# 66-enable -t root -F acpid

if something go wrong you will see it immediately and your actual service will not be touched. So, no risk for you to be in a situation like you have.

Well, now please edit your /etc/66/init.conf and set VERBOSITY=4.
Reboot and post the /run/66/log/0/current like you did previously. It surely something easy to fix and the log level setted to 4 will help a lot to see exactly what happens.

WWat-now · May 28, 2020

First rule for a dev: Never trust an user
First rule for an user: Never trust a dev

:D good one! I'm still learning so bear with me. Thank you for the tips and pointers.

Seems I'm having dbus issues, here is the verbosity=4 /run/66/log/0/current:

@ 400000005ed03de12089b1af [Initiate db of tree boot...]
@ 400000005ed03de121418f46 66-init(src/lib66/rc_init.c: rc_init: 119): tracing: initiate db of tree: boot ...
@ 400000005ed03de1265e1ebc 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-hostname
@ 400000005ed03de1265e2bbf 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-hostname
@ 400000005ed03de1265e6332 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-run
@ 400000005ed03de1265e6697 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-run
@ 400000005ed03de1265e696c 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: populate-run
@ 400000005ed03de1265e9ed5 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: populate-run
@ 400000005ed03de1265ea241 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-tmp
@ 400000005ed03de1265f1c3f 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-tmp
@ 400000005ed03de1265f200c 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: populate-tmp
@ 400000005ed03de1265f2278 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: populate-tmp
@ 400000005ed03de1265f3f97 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-proc
@ 400000005ed03de1265f598a 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-proc
@ 400000005ed03de1265f730c 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-sys
@ 400000005ed03de1265fa1f4 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-sys
@ 400000005ed03de1265fa551 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: populate-sys
@ 400000005ed03de1265fe409 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: populate-sys
@ 400000005ed03de1265fe784 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-dev
@ 400000005ed03de12660270b 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-dev
@ 400000005ed03de126602aa0 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-pts
@ 400000005ed03de12660699c 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-pts
@ 400000005ed03de126606d14 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-shm
@ 400000005ed03de12660c104 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-shm
@ 400000005ed03de12660c469 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: populate-dev
@ 400000005ed03de1266119be 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: populate-dev
@ 400000005ed03de126611d0c 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-cgroups
@ 400000005ed03de1266165aa 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-cgroups
@ 400000005ed03de126616916 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: 00
@ 400000005ed03de12661b954 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: 00
@ 400000005ed03de12661bdb4 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-hwclock
@ 400000005ed03de12661ecc1 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-hwclock
@ 400000005ed03de12661f04b 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: modules-kernel
@ 400000005ed03de126622c44 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: modules-kernel
@ 400000005ed03de126622ff4 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-random
@ 400000005ed03de126626c2a 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-random
@ 400000005ed03de126626fb0 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: modules-system
@ 400000005ed03de12662b1ee 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: modules-system
@ 400000005ed03de12662b5ad 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-sysctl
@ 400000005ed03de12662f110 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-sysctl
@ 400000005ed03de12662f4ad 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: udevd
@ 400000005ed03de126633184 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: udevd
@ 400000005ed03de126633521 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: udevadm
@ 400000005ed03de126637296 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: udevadm
@ 400000005ed03de126637633 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-fontnkey
@ 400000005ed03de12663b563 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-fontnkey
@ 400000005ed03de12663b90f 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-dmraid
@ 400000005ed03de12663f813 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-dmraid
@ 400000005ed03de12663fba0 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-btrfs
@ 400000005ed03de1266436f8 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-btrfs
@ 400000005ed03de126643a6f 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-crypttab
@ 400000005ed03de1266480ff 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-crypttab
@ 400000005ed03de126648482 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-lvm
@ 400000005ed03de12664c3eb 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-lvm
@ 400000005ed03de12664c771 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-zfs
@ 400000005ed03de12665057c 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-zfs
@ 400000005ed03de12665090e 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-Devices
@ 400000005ed03de1266550f8 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-Devices
@ 400000005ed03de126655485 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: all-Mount
@ 400000005ed03de126659390 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: all-Mount
@ 400000005ed03de12665970b 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-fsck
@ 400000005ed03de12665d448 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-fsck
@ 400000005ed03de12665d7ca 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-fstab
@ 400000005ed03de12666150b 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-fstab
@ 400000005ed03de126661877 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: all-System
@ 400000005ed03de1266656f3 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: all-System
@ 400000005ed03de126665a79 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-rw
@ 400000005ed03de126669988 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-rw
@ 400000005ed03de126669cec 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-authfiles
@ 400000005ed03de12666da8f 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-authfiles
@ 400000005ed03de12666de3a 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-swap
@ 400000005ed03de126671da0 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-swap
@ 400000005ed03de12667212a 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-iptables
@ 400000005ed03de1266762ec 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-iptables
@ 400000005ed03de1266766c1 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-ip6tables
@ 400000005ed03de12667abf7 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-ip6tables
@ 400000005ed03de12667afe7 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-loop
@ 400000005ed03de12667e454 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-loop
@ 400000005ed03de12667e80b 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-sethostname
@ 400000005ed03de126682584 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-sethostname
@ 400000005ed03de126682921 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-time
@ 400000005ed03de126686616 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-time
@ 400000005ed03de1266869a0 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-tmpfiles
@ 400000005ed03de12668aab2 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-tmpfiles
@ 400000005ed03de12668ae03 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-rc
@ 400000005ed03de1266914c8 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-rc
@ 400000005ed03de126691886 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-dmesg
@ 400000005ed03de126696137 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-dmesg
@ 400000005ed03de1266964c1 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: all-Local
@ 400000005ed03de12669a2dc 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: all-Local
@ 400000005ed03de12669a626 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: all-Runtime
@ 400000005ed03de12669e41b 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: all-Runtime
@ 400000005ed03de12669e783 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: All
@ 400000005ed03de1266a2e71 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: All
@ 400000005ed03de126787576 [Start db services of tree boot...]
@ 400000005ed03de1280f8dee s6-rc: info: bringing selected services up
@ 400000005ed03de128917f19 s6-rc: info: processing service s6rc-oneshot-runner: starting
@ 400000005ed03de1294e03dc s6-rc: info: service s6rc-oneshot-runner started successfully
@ 400000005ed03de129c02411 s6-rc: info: processing service system-hostname: starting
@ 400000005ed03de129ca845d s6-rc: info: processing service mount-tmp: starting
@ 400000005ed03de129cca91a s6-rc: info: processing service mount-run: starting
@ 400000005ed03de129d0b309 s6-rc: info: processing service mount-proc: starting
@ 400000005ed03de129e124f6 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de129ecd2a9 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de129f6c8e7 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de12a0057a6 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de12fe8bce8 [system-hostname] starts...
@ 400000005ed03de1305bba27 [system-hostname] started successfully
@ 400000005ed03de130602a17 s6-rc: info: service system-hostname started successfully
@ 400000005ed03de131020a75 s6-rc: info: service mount-run started successfully
@ 400000005ed03de131066c8f s6-rc: info: processing service populate-run: starting
@ 400000005ed03de131072b7b s6-rc: info: service mount-proc started successfully
@ 400000005ed03de1311740e4 s6-rc: info: processing service mount-sys: starting
@ 400000005ed03de1311a9923 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de131269281 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de1315f565b [populate-run] starts...
@ 400000005ed03de13224824e s6-rc: info: service mount-sys started successfully
@ 400000005ed03de1322c0e56 s6-rc: info: processing service populate-sys: starting
@ 400000005ed03de1322c1500 s6-rc: info: processing service mount-dev: starting
@ 400000005ed03de1323c68f8 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de1323d660a s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de1327d0823 [populate-sys] starts...
@ 400000005ed03de132c39836 s6-rc: info: service mount-dev started successfully
@ 400000005ed03de132c5cff3 s6-rc: info: processing service populate-dev: starting
@ 400000005ed03de132da6240 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de132ec2069 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de132ff3ca7 s6-rc: info: processing service mount-shm: starting
@ 400000005ed03de1330fe5f4 s6-rc: info: processing service mount-pts: starting
@ 400000005ed03de13317f0ec s6-rc: info: processing service mount-cgroups: starting
@ 400000005ed03de133197aad [populate-dev] starts...
@ 400000005ed03de1331b41fc s6-rc: info: processing service devices-zfs: starting
@ 400000005ed03de1332ac404 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de133449173 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de13351a888 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de1337743b0 [mount-shm] starts...
@ 400000005ed03de133d72c91 [mount-pts] starts...
@ 400000005ed03de1345fb732 [devices-zfs] deactivated
@ 400000005ed03de1348a599f s6-rc: info: service devices-zfs started successfully
@ 400000005ed03de134984e91 [mount-tmp] starts...
@ 400000005ed03de1349a9bb4 [mount-cgroups] starts...
@ 400000005ed03de136349eda [mount-tmp] started successfully
@ 400000005ed03de1363cb67f s6-rc: info: service mount-tmp started successfully
@ 400000005ed03de13640e18f s6-rc: info: processing service populate-tmp: starting
@ 400000005ed03de136556f7b s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de1366b40dc [mount-shm] started successfully
@ 400000005ed03de1367026ec s6-rc: info: service mount-shm started successfully
@ 400000005ed03de136983807 [populate-tmp] starts...
@ 400000005ed03de1369bdf3c [mount-pts] started successfully
@ 400000005ed03de136a0c12b s6-rc: info: service mount-pts started successfully
@ 400000005ed03de137d1ff57 [populate-dev] started successfully
@ 400000005ed03de137d6ba4e s6-rc: info: service populate-dev started successfully
@ 400000005ed03de138c024d9 [populate-tmp] started successfully
@ 400000005ed03de138c45d86 s6-rc: info: service populate-tmp started successfully
@ 400000005ed03de138daca97 [populate-run] started successfully
@ 400000005ed03de138def129 s6-rc: info: service populate-run started successfully
@ 400000005ed03de13936d9b4 [populate-sys] started successfully
@ 400000005ed03de1393b2e84 s6-rc: info: service populate-sys started successfully
@ 400000005ed03de20003598e [mount-cgroups] started successfully
@ 400000005ed03de20007e3f8 s6-rc: info: service mount-cgroups started successfully
@ 400000005ed03de2000a11b2 s6-rc: info: processing service system-sysctl: starting
@ 400000005ed03de200100f6c s6-rc: info: processing service system-random: starting
@ 400000005ed03de2001336e9 s6-rc: info: processing service system-hwclock: starting
@ 400000005ed03de200203c9b s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de20027fb11 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de2003eb1cb s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de200493896 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de20053cd50 s6-rc: info: processing service modules-system: starting
@ 400000005ed03de20069d537 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de20074ea7a s6-rc: info: processing service modules-kernel: starting
@ 400000005ed03de200afe915 [system-random] starts...
@ 400000005ed03de200dce73d [system-sysctl] starts...
@ 400000005ed03de200e81cd7 [modules-kernel] starts...
@ 400000005ed03de201096e55 [system-hwclock] starts...
@ 400000005ed03de20149d0fb [modules-system] starts...
@ 400000005ed03de20393ef17 [system-random] started successfully
@ 400000005ed03de20398b3ca s6-rc: info: service system-random started successfully
@ 400000005ed03de203b8bc03 kernel.sysrq = 1
@ 400000005ed03de203b8c253 kernel.core_uses_pid = 1
@ 400000005ed03de203b8c478 fs.protected_hardlinks = 1
@ 400000005ed03de203b8c661 fs.protected_symlinks = 1
@ 400000005ed03de203b8c886 fs.inotify.max_user_instances = 1024
@ 400000005ed03de203b8caf2 fs.inotify.max_user_watches = 524288
@ 400000005ed03de203d979b2 [system-sysctl] started successfully
@ 400000005ed03de203de344e s6-rc: info: service system-sysctl started successfully
@ 400000005ed03de20dd40a39 /usr/lib/66/scripts/modules.sh: No modules found -- nothing to do
@ 400000005ed03de20df3e8d0 [modules-system] started successfully
@ 400000005ed03de20dfa61a5 s6-rc: info: service modules-system started successfully
@ 400000005ed03de20dfd03ad [system-hwclock] started successfully
@ 400000005ed03de20e0127e2 s6-rc: info: service system-hwclock started successfully
@ 400000005ed03de235a9d372 [modules-kernel] started successfully
@ 400000005ed03de235ae2529 s6-rc: info: service modules-kernel started successfully
@ 400000005ed03de235b09a32 s6-rc: info: processing service udevd: starting
@ 400000005ed03de235f9fb38 [udevd] starts...
@ 400000005ed03de3371413fb s6-rc: info: service udevd started successfully
@ 400000005ed03de337167160 s6-rc: info: processing service udevadm: starting
@ 400000005ed03de337298962 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de3375e6740 [udevadm] starts...
@ 400000005ed03de52e13a79b [udevadm] started successfully
@ 400000005ed03de52e17d2cd s6-rc: info: service udevadm started successfully
@ 400000005ed03de52e19ed86 s6-rc: info: processing service system-fontnkey: starting
@ 400000005ed03de52e2f476c s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de52e41717a s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de52e54ff03 s6-rc: info: processing service devices-lvm: starting
@ 400000005ed03de52e658334 s6-rc: info: processing service devices-dmraid: starting
@ 400000005ed03de52e6e1976 s6-rc: info: processing service devices-crypttab: starting
@ 400000005ed03de52e721333 s6-rc: info: processing service devices-btrfs: starting
@ 400000005ed03de52e781d87 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de52e9db4f8 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de52ea141ef [system-fontnkey] starts...
@ 400000005ed03de52ec3750b s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de52eee30d8 [devices-lvm] deactivated
@ 400000005ed03de52ef2cf99 s6-rc: info: service devices-lvm started successfully
@ 400000005ed03de52f319ffa [devices-dmraid] deactivated
@ 400000005ed03de52f35e5df s6-rc: info: service devices-dmraid started successfully
@ 400000005ed03de52f6c25a2 [devices-btrfs] deactivated
@ 400000005ed03de52f7074cb s6-rc: info: service devices-btrfs started successfully
@ 400000005ed03de52f8c9cd1 [devices-crypttab] deactivated
@ 400000005ed03de52f914802 s6-rc: info: service devices-crypttab started successfully
@ 400000005ed03de532055481 [system-fontnkey] started successfully
@ 400000005ed03de532099bf0 s6-rc: info: service system-fontnkey started successfully
@ 400000005ed03de5320c0cff s6-rc: info: processing service system-fsck: starting
@ 400000005ed03de5321f7d21 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de532830710 [system-fsck] starts...
@ 400000005ed03de535946a2b Obarun: clean, 476820/3239520 files, 6256828/13003776 blocks
@ 400000005ed03de535b9774b [system-fsck] started successfully
@ 400000005ed03de535be7e7d s6-rc: info: service system-fsck started successfully
@ 400000005ed03de535c13bb7 s6-rc: info: processing service mount-fstab: starting
@ 400000005ed03de535d71c69 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de5363874a2 [mount-fstab] starts...
@ 400000005ed03de603ee7c54 fuse: failed to access mountpoint /media/Vista: No such file or directory
@ 400000005ed03de6041f5e9b [mount-fstab] started successfully
@ 400000005ed03de604241463 s6-rc: info: service mount-fstab started successfully
@ 400000005ed03de6042688d6 s6-rc: info: processing service mount-rw: starting
@ 400000005ed03de6043ba547 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de6048a6d6b [mount-rw] starts...
@ 400000005ed03de604e9fab1 [mount-rw] started successfully
@ 400000005ed03de604ede4d1 s6-rc: info: service mount-rw started successfully
@ 400000005ed03de604f0285d s6-rc: info: processing service mount-swap: starting
@ 400000005ed03de605056225 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de60517b5fa s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de6052afc3f s6-rc: info: processing service local-tmpfiles: starting
@ 400000005ed03de6053b93bd s6-rc: info: processing service local-time: starting
@ 400000005ed03de60543cd33 s6-rc: info: processing service local-sethostname: starting
@ 400000005ed03de6054746f4 s6-rc: info: processing service local-iptables: starting
@ 400000005ed03de605574a9c s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de6057b120c s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de6058bf59b [mount-swap] deactivated
@ 400000005ed03de60596e777 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de605b6f947 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de605c2113e s6-rc: info: processing service local-ip6tables: starting
@ 400000005ed03de605d7b3ac s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de605e26d24 s6-rc: info: processing service local-authfiles: starting
@ 400000005ed03de605e33405 s6-rc: info: service mount-swap started successfully
@ 400000005ed03de60607e772 [local-tmpfiles] starts...
@ 400000005ed03de6063ce9d5 [local-iptables] deactivated
@ 400000005ed03de60642273b s6-rc: info: service local-iptables started successfully
@ 400000005ed03de60651285e [local-sethostname] starts...
@ 400000005ed03de60674f41c [local-time] starts...
@ 400000005ed03de606847736 [local-authfiles] starts...
@ 400000005ed03de606bec78b [local-ip6tables] deactivated
@ 400000005ed03de606c3ae85 s6-rc: info: service local-ip6tables started successfully
@ 400000005ed03de606c635cb s6-rc: info: processing service local-loop: starting
@ 400000005ed03de606ef5bd5 [local-authfiles] started successfully
@ 400000005ed03de606f44cd6 s6-rc: info: service local-authfiles started successfully
@ 400000005ed03de606f63b6e s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de6073871fd [local-loop] starts...
@ 400000005ed03de60db6e8e1 [local-time] started successfully
@ 400000005ed03de60dbc563c s6-rc: info: service local-time started successfully
@ 400000005ed03de60e09f9c6 s6-rc: info: service local-sethostname started successfully
@ 400000005ed03de60e0e6724 _z /etc/brlapi.key 0640 root brlapi 0 
@ 400000005ed03de60f06d004 [local-loop] started successfully
@ 400000005ed03de60f0b8878 s6-rc: info: service local-loop started successfully
@ 400000005ed03de60f48628f _d /var/lib/colord 0755 colord colord 0 
@ 400000005ed03de60fe0730e _d /var/lib/colord/icc 0755 colord colord 0 
@ 400000005ed03de6101d9647 _d /run/ConsoleKit 0755 0 0 0 
@ 400000005ed03de610fc3be1 _d /run/dbus 0755 0 0 0 
@ 400000005ed03de6113d784f _d /srv/deluge 0770 deluge deluge 0 
@ 400000005ed03de61213ee3b _d /var/lib/dhcpcd 0700 dhcpcd dhcpcd 0 
@ 400000005ed03de6132444b4 _d /run/dhcpcd 0755 dhcpcd dhcpcd 0 
@ 400000005ed03de6136f15bc _x /run/user/*/gvfs  0 0 0 
@ 400000005ed03de613786adb _z /var/lib/libvirt/qemu 0751 0 0 0 
@ 400000005ed03de6141222f8 _d /run/lighttpd 755 http http 0 
@ 400000005ed03de6144d36da _d /var/cache/lighttpd 755 http http 10d 
@ 400000005ed03de614e183c0 _w /sys/devices/system/cpu/microcode/reload - 0 0 0 1
@ 400000005ed03de614ecb2d5 _d /run/lock/lockdev 0775 root lock 0 
@ 400000005ed03de6152f0345 _d /var/lib/lxdm 0700 lxdm lxdm 0 
@ 400000005ed03de6157542b5 _d /var/cache/man 0755 root root 1w 
@ 400000005ed03de615ac0f10 _d /run/initramfs 0755 root root 0 
@ 400000005ed03de615e27a69 _d /run/nscd 0755 root root 0 
@ 400000005ed03de6162dfda2 _C /etc/crypttab  0 0 0 
@ 400000005ed03de616332191 _C /etc/fstab  0 0 0 
@ 400000005ed03de61637a4e3 _C /etc/group  0 0 0 
@ 400000005ed03de6163bf9a0 _C /etc/gshadow  0 0 0 
@ 400000005ed03de616407fde _C /etc/host.conf  0 0 0 
@ 400000005ed03de61644ff2e _C /etc/hosts  0 0 0 
@ 400000005ed03de61649ad26 _C /etc/issue  0 0 0 
@ 400000005ed03de6164e20b2 _C /etc/ld.so.conf  0 0 0 
@ 400000005ed03de617116caa _C /etc/motd  0 0 0 
@ 400000005ed03de617146f04 _C /etc/nsswitch.conf  0 0 0 
@ 400000005ed03de617175bf8 _C /etc/passwd  0 0 0 
@ 400000005ed03de6171a915a _C /etc/profile  0 0 0 
@ 400000005ed03de6171d9b75 _C /etc/securetty  0 0 0 
@ 400000005ed03de61720a840 _C /etc/shadow  0 0 0 
@ 400000005ed03de61723a880 _C /etc/shells  0 0 0 
@ 400000005ed03de6172d969c _d /run/screens 0755 root root 0 
@ 400000005ed03de6176ec833 _d /var/lib/sddm 0755 sddm sddm 0 
@ 400000005ed03de617a4a96f _d /var/empty 0755 root root 0 
@ 400000005ed03de617dc5319 _d /run/sudo 0711 root root 0 
@ 400000005ed03de61816bc0b _D /run/sudo/ts 0700 root root 0 
@ 400000005ed03de61858274d [local-tmpfiles] started successfully
@ 400000005ed03de6185c7fdc s6-rc: info: service local-tmpfiles started successfully
@ 400000005ed03de6185ed59e s6-rc: info: processing service local-rc: starting
@ 400000005ed03de618729fca s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de618d4fba1 [local-rc] starts...
@ 400000005ed03de72d5577f7 [local-rc] started successfully
@ 400000005ed03de72d5a31a3 s6-rc: info: service local-rc started successfully
@ 400000005ed03de72d5cb690 s6-rc: info: processing service local-dmesg: starting
@ 400000005ed03de72d7119cf s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de72db61b7a [local-dmesg] starts...
@ 400000005ed03de72e89f3a8 [local-dmesg] started successfully
@ 400000005ed03de72e8e68fb s6-rc: info: service local-dmesg started successfully
@ 400000005ed03de72e908f0b s6-rc: info: processing service all-Runtime: starting
@ 400000005ed03de72ea4f3f3 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ed03de7324f75eb 66-init(src/lib66/ss_resolve.c: ss_resolve_create_live: 1136): tracing: point symlink: /run/66/state/0/root/servicedirs to /var/lib/66/system/root/servicedirs
@ 400000005ed03de7324fb0f8 66-init(src/lib66/svc_init.c: svc_init: 96): tracing: init service: openntpd-log
@ 400000005ed03de7324fb4b6 66-init(src/lib66/svc_init.c: svc_init: 101): tracing: copy: /var/lib/66/system/root/servicedirs/svc/openntpd to /run/66/scandir/0/openntpd
@ 400000005ed03de732ee2716 66-init(src/lib66/svc_init.c: svc_init: 141): tracing: create file: /run/66/scandir/0/openntpd/log/down
@ 400000005ed03de732ee5c9d 66-init(src/lib66/svc_init.c: svc_init: 149): tracing: create fifo: /run/66/scandir/0/openntpd/log/event
@ 400000005ed03de732eeca66 66-init(src/lib66/svc_init.c: svc_init: 155): tracing: subcribe to fifo: /run/66/scandir/0/openntpd/log/event
@ 400000005ed03de732f158c0 66-init(src/lib66/svc_init.c: svc_init: 96): tracing: init service: openntpd
@ 400000005ed03de732f15e2c 66-init(src/lib66/svc_init.c: svc_init: 141): tracing: create file: /run/66/scandir/0/openntpd/down
@ 400000005ed03de732f18010 66-init(src/lib66/svc_init.c: svc_init: 149): tracing: create fifo: /run/66/scandir/0/openntpd/event
@ 400000005ed03de732f1adb8 66-init(src/lib66/svc_init.c: svc_init: 155): tracing: subcribe to fifo: /run/66/scandir/0/openntpd/event
@ 400000005ed03de732f2f1a5 66-init(src/lib66/svc_init.c: svc_init: 96): tracing: init service: acpid-log
@ 400000005ed03de732f2f70c 66-init(src/lib66/svc_init.c: svc_init: 101): tracing: copy: /var/lib/66/system/root/servicedirs/svc/acpid to /run/66/scandir/0/acpid
@ 400000005ed03de73317e18b 66-init(src/lib66/svc_init.c: svc_init: 141): tracing: create file: /run/66/scandir/0/acpid/log/down
@ 400000005ed03de73317e923 66-init(src/lib66/svc_init.c: svc_init: 149): tracing: create fifo: /run/66/scandir/0/acpid/log/event
@ 400000005ed03de733181821 66-init(src/lib66/svc_init.c: svc_init: 155): tracing: subcribe to fifo: /run/66/scandir/0/acpid/log/event
@ 400000005ed03de73319c518 66-init(src/lib66/svc_init.c: svc_init: 96): tracing: init service: acpid
@ 400000005ed03de73319cbe5 66-init(src/lib66/svc_init.c: svc_init: 141): tracing: create file: /run/66/scandir/0/acpid/down
@ 400000005ed03de7331a09f0 66-init(src/lib66/svc_init.c: svc_init: 149): tracing: create fifo: /run/66/scandir/0/acpid/event
@ 400000005ed03de7331a24b2 66-init(src/lib66/svc_init.c: svc_init: 155): tracing: subcribe to fifo: /run/66/scandir/0/acpid/event
@ 400000005ed03de7331b4446 66-init(src/lib66/svc_init.c: svc_init: 96): tracing: init service: tty@ tty2
@ 400000005ed03de7331b4962 66-init(src/lib66/svc_init.c: svc_init: 101): tracing: copy: /var/lib/66/system/root/servicedirs/svc/tty@ tty2 to /run/66/scandir/0/tty@ tty2
@ 400000005ed03de733279eae 66-init(src/lib66/svc_init.c: svc_init: 141): tracing: create file: /run/66/scandir/0/tty@ tty2/down
@ 400000005ed03de73327a737 66-init(src/lib66/svc_init.c: svc_init: 149): tracing: create fifo: /run/66/scandir/0/tty@ tty2/event
@ 400000005ed03de73327dc8d 66-init(src/lib66/svc_init.c: svc_init: 155): tracing: subcribe to fifo: /run/66/scandir/0/tty@ tty2/event
@ 400000005ed03de73329a509 66-init(src/lib66/svc_init.c: svc_init: 96): tracing: init service: cupsd-log
@ 400000005ed03de73329ac96 66-init(src/lib66/svc_init.c: svc_init: 101): tracing: copy: /var/lib/66/system/root/servicedirs/svc/cupsd to /run/66/scandir/0/cupsd
@ 400000005ed03de73341a458 66-init(src/lib66/svc_init.c: svc_init: 141): tracing: create file: /run/66/scandir/0/cupsd/log/down
@ 400000005ed03de73341d673 66-init(src/lib66/svc_init.c: svc_init: 149): tracing: create fifo: /run/66/scandir/0/cupsd/log/event
@ 400000005ed03de733427f18 66-init(src/lib66/svc_init.c: svc_init: 155): tracing: subcribe to fifo: /run/66/scandir/0/cupsd/log/event
@ 400000005ed03de73343e6f4 66-init(src/lib66/svc_init.c: svc_init: 96): tracing: init service: cupsd
@ 400000005ed03de73343eb81 66-init(src/lib66/svc_init.c: svc_init: 141): tracing: create file: /run/66/scandir/0/cupsd/down
@ 400000005ed03de73343ee44 66-init(src/lib66/svc_init.c: svc_init: 149): tracing: create fifo: /run/66/scandir/0/cupsd/event
@ 400000005ed03de733443bd1 66-init(src/lib66/svc_init.c: svc_init: 155): tracing: subcribe to fifo: /run/66/scandir/0/cupsd/event
@ 400000005ed03de733459eeb 66-init(src/lib66/svc_init.c: svc_init: 96): tracing: init service: tty@ tty1
@ 400000005ed03de73345a3ed 66-init(src/lib66/svc_init.c: svc_init: 101): tracing: copy: /var/lib/66/system/root/servicedirs/svc/tty@ tty1 to /run/66/scandir/0/tty@ tty1
@ 400000005ed03de7334f9d81 66-init(src/lib66/svc_init.c: svc_init: 141): tracing: create file: /run/66/scandir/0/tty@ tty1/down
@ 400000005ed03de7334fbdd7 66-init(src/lib66/svc_init.c: svc_init: 149): tracing: create fifo: /run/66/scandir/0/tty@ tty1/event
@ 400000005ed03de733500581 66-init(src/lib66/svc_init.c: svc_init: 155): tracing: subcribe to fifo: /run/66/scandir/0/tty@ tty1/event
@ 400000005ed03de73350fd58 66-init(src/lib66/svc_init.c: svc_init: 167): tracing: reload scandir: /run/66/scandir/0
@ 400000005ed03de733514eca 66-init(src/lib66/svc_init.c: svc_init: 174): tracing: waiting for events on fifo
@ 400000005ed03de73398c1a5 66-init(src/lib66/svc_init.c: svc_init: 180): tracing: delete down file at: /run/66/scandir/0/openntpd/log/down
@ 400000005ed03de73398ce2b 66-init(src/lib66/svc_init.c: svc_init: 180): tracing: delete down file at: /run/66/scandir/0/openntpd/down
@ 400000005ed03de733990f1b 66-init(src/lib66/svc_init.c: svc_init: 180): tracing: delete down file at: /run/66/scandir/0/acpid/log/down
@ 400000005ed03de733991459 66-init(src/lib66/svc_init.c: svc_init: 180): tracing: delete down file at: /run/66/scandir/0/acpid/down
@ 400000005ed03de733991845 66-init(src/lib66/svc_init.c: svc_init: 180): tracing: delete down file at: /run/66/scandir/0/tty@ tty2/down
@ 400000005ed03de733993eac 66-init(src/lib66/svc_init.c: svc_init: 180): tracing: delete down file at: /run/66/scandir/0/cupsd/log/down
@ 400000005ed03de733994245 66-init(src/lib66/svc_init.c: svc_init: 180): tracing: delete down file at: /run/66/scandir/0/cupsd/down
@ 400000005ed03de733995c56 66-init(src/lib66/svc_init.c: svc_init: 180): tracing: delete down file at: /run/66/scandir/0/tty@ tty1/down
@ 400000005ed03de73399765f 66-init(src/lib66/svc_init.c: svc_init: 190): tracing: Write state file of: openntpd-log
@ 400000005ed03de73399c751 66-init(src/lib66/svc_init.c: svc_init: 196): info: Initialized successfully: openntpd-log
@ 400000005ed03de73399cb01 66-init(src/lib66/svc_init.c: svc_init: 190): tracing: Write state file of: openntpd
@ 400000005ed03de7339a7c84 66-init(src/lib66/svc_init.c: svc_init: 196): info: Initialized successfully: openntpd
@ 400000005ed03de7339a80d5 66-init(src/lib66/svc_init.c: svc_init: 190): tracing: Write state file of: acpid-log
@ 400000005ed03de7339ab8ee 66-init(src/lib66/svc_init.c: svc_init: 196): info: Initialized successfully: acpid-log
@ 400000005ed03de7339abca5 66-init(src/lib66/svc_init.c: svc_init: 190): tracing: Write state file of: acpid
@ 400000005ed03de7339afc8b 66-init(src/lib66/svc_init.c: svc_init: 196): info: Initialized successfully: acpid
@ 400000005ed03de7339b002f 66-init(src/lib66/svc_init.c: svc_init: 190): tracing: Write state file of: tty@ tty2
@ 400000005ed03de7339b3f11 66-init(src/lib66/svc_init.c: svc_init: 196): info: Initialized successfully: tty@ tty2
@ 400000005ed03de7339b42c4 66-init(src/lib66/svc_init.c: svc_init: 190): tracing: Write state file of: cupsd-log
@ 400000005ed03de7339b8180 66-init(src/lib66/svc_init.c: svc_init: 196): info: Initialized successfully: cupsd-log
@ 400000005ed03de7339b84f0 66-init(src/lib66/svc_init.c: svc_init: 190): tracing: Write state file of: cupsd
@ 400000005ed03de7339bc49c 66-init(src/lib66/svc_init.c: svc_init: 196): info: Initialized successfully: cupsd
@ 400000005ed03de7339bc82a 66-init(src/lib66/svc_init.c: svc_init: 190): tracing: Write state file of: tty@ tty1
@ 400000005ed03de7339c11aa 66-init(src/lib66/svc_init.c: svc_init: 196): info: Initialized successfully: tty@ tty1
@ 400000005ed03de7348fec8e 66-init(src/lib66/rc_init.c: rc_init: 119): tracing: initiate db of tree: root ...
@ 400000005ed03de73868fcb5 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: consolekit-log
@ 400000005ed03de738690b7e 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: consolekit-log
@ 400000005ed03de738690f23 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: dbus-log
@ 400000005ed03de738693ed9 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: dbus-log
@ 400000005ed03de738694249 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: dbus
@ 400000005ed03de738695d5d 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: dbus
@ 400000005ed03de738697739 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: consolekit
@ 400000005ed03de73869a7b7 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: consolekit
@ 400000005ed03de73869ab23 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: sddm-log
@ 400000005ed03de73869e8a7 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: sddm-log
@ 400000005ed03de73869ebed 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: sddm
@ 400000005ed03de7386a3652 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: sddm
@ 400000005ed03de7386a3a58 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: connmand-log
@ 400000005ed03de7386a76e0 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: connmand-log
@ 400000005ed03de7386a7aae 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: connmand
@ 400000005ed03de7386abbe2 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: connmand
@ 400000005ed03de7386cb4ba 66-all(src/66/66-all.c: main: 350): tracing: reload scandir: /run/66/scandir/0
@ 400000005ed03de73897834f 66-start(src/lib66/ssexec_start.c: ssexec_start: 335): tracing: sanitize classic services list...
@ 400000005ed03de738978bbd 66-start(src/lib66/ssexec_start.c: ssexec_start: 338): tracing: start classic services list ...
@ 400000005ed03de738abe821 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 51): tracing: clean up fifo: /run/66/scandir/0/tty@ tty1/event
@ 400000005ed03de738ac0ff4 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 55): tracing: subcribe to fifo: /run/66/scandir/0/tty@ tty1/event
@ 400000005ed03de738adf0bf 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 51): tracing: clean up fifo: /run/66/scandir/0/cupsd/log/event
@ 400000005ed03de738adf72d 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 55): tracing: subcribe to fifo: /run/66/scandir/0/cupsd/log/event
@ 400000005ed03de738af6df8 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 51): tracing: clean up fifo: /run/66/scandir/0/cupsd/event
@ 400000005ed03de738af7389 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 55): tracing: subcribe to fifo: /run/66/scandir/0/cupsd/event
@ 400000005ed03de738b0a63c 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 51): tracing: clean up fifo: /run/66/scandir/0/tty@ tty2/event
@ 400000005ed03de738b12008 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 55): tracing: subcribe to fifo: /run/66/scandir/0/tty@ tty2/event
@ 400000005ed03de738b25d03 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 51): tracing: clean up fifo: /run/66/scandir/0/acpid/log/event
@ 400000005ed03de738b261ee 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 55): tracing: subcribe to fifo: /run/66/scandir/0/acpid/log/event
@ 400000005ed03de738b3b6f6 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 51): tracing: clean up fifo: /run/66/scandir/0/acpid/event
@ 400000005ed03de738b3bc43 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 55): tracing: subcribe to fifo: /run/66/scandir/0/acpid/event
@ 400000005ed03de738b4d634 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 51): tracing: clean up fifo: /run/66/scandir/0/openntpd/log/event
@ 400000005ed03de738b5098e 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 55): tracing: subcribe to fifo: /run/66/scandir/0/openntpd/log/event
@ 400000005ed03de738b5f22b 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 51): tracing: clean up fifo: /run/66/scandir/0/openntpd/event
@ 400000005ed03de738b613d0 66-start(src/lib66/svc_init_pipe.c: svc_init_pipe: 55): tracing: subcribe to fifo: /run/66/scandir/0/openntpd/event
@ 400000005ed03de738b8de98 66-start(src/lib66/ssexec_svctl.c: svc_writectl: 401): tracing: send signal: u to: /run/66/scandir/0/tty@ tty1/supervise
@ 400000005ed03de738bab5c4 66-start(src/lib66/ssexec_svctl.c: svc_writectl: 401): tracing: send signal: uwU to: /run/66/scandir/0/cupsd/log/supervise
@ 400000005ed03de738de22e4 66-start(src/lib66/ssexec_svctl.c: svc_writectl: 401): tracing: send signal: u to: /run/66/scandir/0/tty@ tty2/supervise
@ 400000005ed03de738df4542 66-start(src/lib66/ssexec_svctl.c: svc_writectl: 401): tracing: send signal: u to: /run/66/scandir/0/cupsd/supervise
@ 400000005ed03de738fa73b5 66-start(src/lib66/ssexec_svctl.c: svc_writectl: 401): tracing: send signal: uwU to: /run/66/scandir/0/acpid/log/supervise
@ 400000005ed03de738fe5be1 66-start(src/lib66/ssexec_svctl.c: svc_writectl: 401): tracing: send signal: u to: /run/66/scandir/0/acpid/supervise
@ 400000005ed03de7392003f1 66-start(src/lib66/ssexec_svctl.c: svc_writectl: 401): tracing: send signal: uwU to: /run/66/scandir/0/openntpd/log/supervise
@ 400000005ed03de739222dfb 66-start(src/lib66/ssexec_svctl.c: svc_writectl: 401): tracing: send signal: u to: /run/66/scandir/0/openntpd/supervise
@ 400000005ed03de80a5399f2 66-start(src/lib66/ssexec_svctl.c: announce: 255): info: tty@ tty1: started successfully
@ 400000005ed03de80a53cdb2 66-start(src/lib66/ssexec_svctl.c: write_state: 230): tracing: Write state file of: tty@ tty1
@ 400000005ed03de80a53e9f3 66-start(src/lib66/ssexec_svctl.c: announce: 255): info: cupsd-log: started successfully
@ 400000005ed03de80a53ed48 66-start(src/lib66/ssexec_svctl.c: write_state: 230): tracing: Write state file of: cupsd-log
@ 400000005ed03de80a544547 66-start(src/lib66/ssexec_svctl.c: announce: 255): info: cupsd: started successfully
@ 400000005ed03de80a5449bd 66-start(src/lib66/ssexec_svctl.c: write_state: 230): tracing: Write state file of: cupsd
@ 400000005ed03de80a549e45 66-start(src/lib66/ssexec_svctl.c: announce: 255): info: tty@ tty2: started successfully
@ 400000005ed03de80a54a32c 66-start(src/lib66/ssexec_svctl.c: write_state: 230): tracing: Write state file of: tty@ tty2
@ 400000005ed03de80a54fc39 66-start(src/lib66/ssexec_svctl.c: announce: 255): info: acpid-log: started successfully
@ 400000005ed03de80a550065 66-start(src/lib66/ssexec_svctl.c: write_state: 230): tracing: Write state file of: acpid-log
@ 400000005ed03de80a555221 66-start(src/lib66/ssexec_svctl.c: announce: 255): info: acpid: started successfully
@ 400000005ed03de80a555633 66-start(src/lib66/ssexec_svctl.c: write_state: 230): tracing: Write state file of: acpid
@ 400000005ed03de80a55ad1b 66-start(src/lib66/ssexec_svctl.c: announce: 255): info: openntpd-log: started successfully
@ 400000005ed03de80a55b177 66-start(src/lib66/ssexec_svctl.c: write_state: 230): tracing: Write state file of: openntpd-log
@ 400000005ed03de80a5604d2 66-start(src/lib66/ssexec_svctl.c: announce: 255): info: openntpd: started successfully
@ 400000005ed03de80a5608ae 66-start(src/lib66/ssexec_svctl.c: write_state: 230): tracing: Write state file of: openntpd
@ 400000005ed03de80a5bf074 66-start(src/lib66/ssexec_start.c: ssexec_start: 341): tracing: switch classic service list of: root to source
@ 400000005ed03de80a5cecc6 66-start(src/lib66/ssexec_start.c: ssexec_start: 349): tracing: sanitize atomic services list...
@ 400000005ed03de80a5cf11b 66-start(src/lib66/ssexec_start.c: ssexec_start: 354): tracing: start atomic services list ...
@ 400000005ed03de80c5400fa s6-rc: info: bringing selected services up
@ 400000005ed03de80c576496 s6-rc: info: processing service s6rc-fdholder: starting
@ 400000005ed03de80dfaac86 s6-rc: info: service s6rc-fdholder started successfully
@ 400000005ed03de80dfd0c85 s6-rc: info: processing service sddm-log: starting
@ 400000005ed03de80e29b47e s6-rc: info: processing service dbus-log: starting
@ 400000005ed03de80e31a1e2 s6-rc: info: processing service consolekit-log: starting
@ 400000005ed03de80e421b23 s6-rc: info: processing service connmand-log: starting
@ 400000005ed03de80f98f923 s6-rc: info: service dbus-log started successfully
@ 400000005ed03de80f9c6d66 s6-rc: info: processing service dbus: starting
@ 400000005ed03de80f9d4012 s6-rc: info: service consolekit-log started successfully
@ 400000005ed03de81014e562 s6-rc: info: service connmand-log started successfully
@ 400000005ed03de810181835 s6-rc: info: service sddm-log started successfully
@ 400000005ed03deb0fbffd66 s6-svlisten1: fatal: timed out
@ 400000005ed03deb0fc48689 s6-rc: warning: unable to start service dbus: command exited 99
@ 400000005ed03deb0fc6529e 66-start(src/lib66/ssexec_dbctl.c: ssexec_dbctl: 343): fatal: unable to start services selection
@ 400000005ed03deb0fc83f21 66-all(src/66/66-all.c: main: 356): fatal: unable to start services of tree: root
@ 400000005ed03deb0fccf2ff s6-rc: warning: unable to start service all-Runtime: command exited 111
@ 400000005ed03deb0fce7985 66-dbctl(src/lib66/ssexec_dbctl.c: ssexec_dbctl: 343): fatal: unable to start services selection
@ 400000005ed03deb0fdc9ecb rc.init: fatal: please see the log at /run/66/log/0/current

No services depending on dbus are working:

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(1041,Enabled,classic) tty@ tty1
               ├─(949,Enabled,classic) openntpd-log
               ├─(938,Enabled,classic) cupsd-log
               ├─(946,Enabled,classic) cupsd
               ├─(945,Enabled,classic) tty@ tty2
               ├─(947,Enabled,classic) acpid-log
               ├─(948,Enabled,classic) acpid
               ├─(0,Enabled,classic) openntpd
               ├─(977,Enabled,longrun) consolekit-log
               ├─(973,Enabled,longrun) dbus-log
               ├─(0,Enabled,longrun) dbus
               ├─(0,Enabled,longrun) consolekit
               ├─(971,Enabled,longrun) sddm-log
               ├─(0,Enabled,longrun) sddm
               ├─(976,Enabled,longrun) connmand-log
               └─(0,Enabled,longrun) connmand

I'm using startx, wpa_supplicant&dhcp as workaround....

eric · May 28, 2020

yeah dbus stuff here. Please provide the following:

# 66-inservice -t root -g dbus

Also, you can try to do

# 66-enable -F -C -t root dbus
# 66-start -t root -R dbus
# 66-inservice -o status dbus # to check if it's running

Something dbus is stubborn and a reboot it needed.

WWat-now · May 29, 2020

result:

# 66-inservice -t root -g dbus
Name                  : dbus
Version               : 0.1.4
In tree               : root
Status                : enabled, down (exitcode 111) 6696 seconds, ready 6696 seconds
Type                  : longrun
Description           : dbus system daemon
Source                : /usr/lib/66/service/dbus
Live                  : /run/66/tree/0/root/servicedirs/dbus
Dependencies          : /
                        └─(973,Enabled,longrun) dbus-log
External dependencies : None
Optional dependencies : None
Start script          : 	execl-toc -S ${socket_name} -m 0755
                        	foreground { dbus-uuidgen --ensure }
                        	execl-cmdline -s { dbus-daemon ${cmd_args} }
Stop script           :  s6-rmrf ${socket_name} 
Environment source    : /etc/66/conf/dbus
Environment file      : 
                        cmd_args=!--system --print-pid=4 --nofork --nopidfile --address=unix:path=/run/dbus/system_bus_socket
                        socket_dir=!/run/dbus
                        socket_name=!system_bus_socket
Log name              : dbus-log
Log destination       : /var/log/66/dbus
Log file              : 
2020-05-28 10:02:59.468906580  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 10:03:00.475194426  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 10:03:01.476336249  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 15:18:04.972217771  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 15:18:05.949529961  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 15:18:06.950552723  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 15:19:53.931963802  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 15:19:54.914157207  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 15:19:55.914995153  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 15:55:35.014290008  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 15:55:35.992526519  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 15:55:36.998323952  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 16:03:03.100546341  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 16:03:04.108950498  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 16:03:05.110247178  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 17:40:03.280488879  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 17:40:04.277872679  execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-05-28 17:40:05.278583583  execl-toc: fatal: unable to get dirname of: system_bus_socket

then

# 66-enable -F -C -t root dbus
66-enable: info: Enabled successfully: dbus
# 66-start -t root -R dbus
66-start: info: Already down: sddm
66-start: info: Already down: consolekit
66-start: info: Already down: connmand
66-start: info: Already down: dbus
66-start: info: Already down: connmand
66-start: info: Already down: sddm
66-start: info: Already down: consolekit
66-start: info: Already down: dbus
66-start: info: Started successfully: dbus
66-start: info: Started successfully: consolekit
66-start: info: Started successfully: sddm
66-start: info: Started successfully: connmand
# 66-inservice -o status dbus
Status                : enabled, up (pid 24902) 42 seconds, ready 42 seconds

Thank you much! it's solved! Until next time have a good one.

Edit: Spoke too soon,not all solved SDDM still not working& some force closing of x is going on with unzipped tarball palemoon app I use.

Might be theming using qt5ct causing problems

Edit2: Solved, indeed have a good one! Seems I needed mesa-vdpau driver+mesa and not only mesa with libva-intel-driver? Im not using xf86-video-intel driver.

eric · May 29, 2020

Edit2: Solved

good! :)

This thread show me something that should be "fixed". Actually the 66-update tool do not use the -C option at enable process. It works for the majority of the case but if a service was updated (and so possibly the variable at the configuration file environment), the new service keep running with an old configuration file which can cause trouble. I think this is what you hit.

I need to think about this...

WWat-now · May 29, 2020

May you&your brain have all the power you need, that is quite above my level!

:cool: thumbs up!

Question: Estimated time of Arrival of new version of qtbase from extra?

Edit: also for shutdown sequence I always see "target is busy" when umount is executed to unmount /sys/kernel/debug & sometimes /tmp is there a way to change that. Pardon if that is petty. I know using umount -lr /mounted/point usually works when mounts are busy after chroot...

eric · May 29, 2020

Question: Estimated time of Arrival of new version of qtbase from extra?

I can't answer. This is not depending on us but on Arch.

Edit: also for shutdown sequence I always see "target is busy" when umount is executed to unmount /sys/kernel/debug & sometimes /tmp is there a way to change that. Pardon if that is petty. I know using umount -lr /mounted/point usually works when mounts are busy after chroot...

we aware about that, this will change with the new boot set of service which come soon :)

WWat-now · May 29, 2020

I can't answer. This is not depending on us but on Arch.

I meant obextra...arch has updated their qtbase to 5.15....but fungalnet on this forum advised to wait for obextra qtbase version 5.15....

say?

banned_9-26-2021 · May 29, 2020

I checked 4 different mirrors EU and it is not on extra yet, 5.15 is still on testing
So if your mirror shows it on extra not all mirrors have caught up to the change yet. This means that if obextra adds 5.15 everyone else's qt5 will break, having the base from 5.15 and the rest from 5.14 ...

Unfortunately this is the drawback of having uncontrolled mirrors and rely on other distributions.
This happens with other package bundles but this is the most frequent as the Qt team is very active in revising everything. Imagine that on AUR there are still currently revised software that still need Qt4, haven't been able to transition to Qt5 yet...
There is also many independent software (not carried by most distributions like forks of browsers) that people download directly and are compiled with 1-2 major versions back of GlibC and will not run on Arch because it is way ahead of everyone else. Most sw is published as "linux" software as long as it runs on Debian. In some basic core libraries Debian may be 1-2 years behind Arch, Void, and a few others. Even Debian Unstable is months behind Arch.

How many people are conscious of this difference is pure speculation. The majority of people running Ubuntu and Mint upgrading 3-4 times a day will not admit they are aware they are running 2 years old software. "It is Stable"

But we have pacman :)

WWat-now · May 29, 2020

Oh I see, I activated testing repo&i'm surprised i must Ignorepkg=qt5* or else pacman tries to update...which confused me into thinking it was on extra already...carry on :)

banned_9-26-2021 · May 29, 2020

at times like this when it becomes too much of a hustle to ignore so many pkgs you turn testing off and wait :)

But we have deviated from topic way too much

banned_9-26-2021 · May 29, 2020

By the way, there was this failing point in your boot:

@ 400000005ed03de603ee7c54 fuse: failed to access mountpoint /media/Vista: No such file or directory

Is this a network mount point of is it just a mispelled mounting point?

WWat-now · May 29, 2020

It's a mount point that is used to mount my NTFS partition ....I had added it to fstab to auto mount-im not sure why it resulted that error....I use grub2win software in windows rather than let linux manage my grub2 for managing boot of multiple distros in different partitions,multiple kernels &even some iso boots. I find it easier.

Edit: Maybe something is blocking it from mounting at boot- im not sure

banned_9-26-2021 · May 29, 2020

What is the line on /etc/fstab for /media/Vista