jbkeh
I must have done something wrong, but I cannot find anything like this.
Once I was able to install Obarun, things run reasonably well, except for the times I need to run in sudo mode. The two main situations are Geany and Thunar. Both actually function but the invoking terminal is flooded with repeating errors, leaving me always wondering if some day my luck will run out.
Possibly related, I just tried to create a btrfs raid1 (two-disk) which functions well under SystemRescueCd (Arch based), but Obarun cannot boot as it cannot find the second copy (uuid).
Any thoughts, ideas, answers?
(geany:1641): dconf-WARNING **: 13:26:16.448: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=33bb46e66a97de0042a160b75e97a554 --binary-syntax --close-stderr”: Child process exited with code 1
(geany:1641): dconf-WARNING **: 13:26:16.466: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=33bb46e66a97de0042a160b75e97a554 --binary-syntax --close-stderr”: Child process exited with code 1
(geany:1641): dconf-WARNING **: 13:26:16.477: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=33bb46e66a97de0042a160b75e97a554 --binary-syntax --close-stderr”: Child process exited with code 1
thunar: Failed to initialize Xfconf: Error spawning command line ?dbus-launch --autolaunch=33bb46e66a97de0042a160b75e97a554 --binary-syntax --close-stderr?: Child process exited with code 1
(thunar:1708): thunar-WARNING **: 13:31:45.777: Name 'org.xfce.FileManager' lost on the message dbus.
(thunar:1708): thunar-WARNING **: 13:31:45.777: Name 'org.freedesktop.FileManager1' lost on the message dbus.
ThunarThumbnailer: failed to create proxy: Error spawning command line “dbus-launch --autolaunch=33bb46e66a97de0042a160b75e97a554 --binary-syntax --close-stderr”: Child process exited with code 1
eric
btrfs issue:
try to edit your /etc/66/boot.conf and set BTRFS=!yes
reboot
geany and all dbus program issue:
Do you have a running dbus and dbus-session@ service? Did you have follow this
https://wiki.obarun.org/doku.php?id=dbus_and_dm?
jbkeh
Sadly, I batted 0 for 2.....
On the btrfs front, you were correct in the assumption that BTRFS=!no was set, but changing it to BTRFS=!yes had no effect.
This seems to be a function of whether the btrfs pool has one or more devices/partitions. IIUC, each member device/partition of the pool contains a list of all the device/partition uuids, so that mounting any one member of the pool device/partition provides the path to mount them all. While this works under Arch (SystemRescueCd), under Obarun the pointer (uuid) to the second member appears to be garbage - it does not match anything.
Turning to the dbus situation, I thought I had already covered this, but retraced the steps to which you pointed.
1. Everything was already installed and current.
2. Creating the set of services was rejected as already existing.
3. In the third to last step, there is no mention of 'consolekit'
4. In the second to last step, 'consolekit ' is flagged as source not found
5. I repeated second to last step using 'consolekit2'
Not critical, but it would be nice to solve the btrfs problem.
eric
This seems to be a function of whether the btrfs pool has one or more devices/partitions. IIUC, each member device/partition of the pool contains a list of all the device/partition uuids, so that mounting any one member of the pool device/partition provides the path to mount them all. While this works under Arch (SystemRescueCd), under Obarun the pointer (uuid) to the second member appears to be garbage - it does not match anything.
i guess:
- you use a compatible bootlaoder.(usually grub)
- your kernel parameter is correctly set in case of sub-volume use.
- your /etc/fstab is correctly set with the correct mount options
- you set FSTAB=!yes at your /etc/66/boot.conf file
right?
About dbus. Your explanation confuse me and now I have some difficulty to know if it's working for you or not.
If not, please provide the following:
% sudo 66-intree -g
% 66-intree -g
jbkeh
As requested, here are the two 66-intree -g:
Name : boot
Initialized : yes
Enabled : no
Starts after : None
Current : no
Allowed : root
Symlinks : svc->source db->source
Contents : /
├─(241,Enabled,classic) tty12
├─(up,Enabled,oneshot) system-hostname
├─(up,Enabled,oneshot) mount-run
├─(up,Enabled,oneshot) populate-run
├─(up,Enabled,oneshot) mount-tmp
├─(up,Enabled,oneshot) populate-tmp
├─(up,Enabled,oneshot) mount-proc
├─(up,Enabled,oneshot) mount-sys
├─(up,Enabled,oneshot) populate-sys
├─(up,Enabled,oneshot) mount-dev
├─(up,Enabled,oneshot) mount-pts
├─(up,Enabled,oneshot) mount-shm
├─(up,Enabled,oneshot) populate-dev
├─(up,Enabled,oneshot) mount-cgroups
├─(up,Enabled,bundle) 00
├─(up,Enabled,bundle) all-Mount
├─(up,Enabled,oneshot) system-hwclock
├─(up,Enabled,oneshot) modules-kernel
├─(up,Enabled,oneshot) system-random
├─(up,Enabled,oneshot) modules-system
├─(up,Enabled,oneshot) system-sysctl
├─(458,Enabled,longrun) udevd
├─(up,Enabled,oneshot) udevadm
├─(up,Enabled,oneshot) system-fontnkey
├─(up,Enabled,oneshot) devices-dmraid
├─(up,Enabled,oneshot) devices-btrfs
├─(up,Enabled,oneshot) devices-crypttab
├─(up,Enabled,oneshot) devices-lvm
├─(up,Enabled,oneshot) devices-zfs
├─(up,Enabled,bundle) system-Devices
├─(up,Enabled,oneshot) system-fsck
├─(up,Enabled,oneshot) mount-fstab
├─(up,Enabled,bundle) all-System
├─(up,Enabled,oneshot) mount-rw
├─(up,Enabled,oneshot) mount-swap
├─(up,Enabled,oneshot) local-iptables
├─(up,Enabled,oneshot) local-ip6tables
├─(up,Enabled,oneshot) local-loop
├─(up,Enabled,oneshot) local-sethostname
├─(up,Enabled,oneshot) local-time
├─(up,Enabled,oneshot) local-authfiles
├─(up,Enabled,oneshot) local-tmpfiles
├─(up,Enabled,oneshot) local-rc
├─(up,Enabled,oneshot) local-dmesg
├─(up,Enabled,bundle) all-Local
├─(up,Enabled,oneshot) all-Runtime
└─(up,Enabled,bundle) All
Name : boot-user
Initialized : yes
Enabled : yes
Starts after : None
Current : no
Allowed : root
Symlinks : svc->source db->source
Contents : /
├─(up,Enabled,oneshot) mount-run-uras
├─(up,Enabled,oneshot) setenv-uras
├─(757,Enabled,longrun) scandir-uras-log
├─(779,Enabled,longrun) scandir-uras
└─(up,Enabled,bundle) All-uras
Name : root
Initialized : yes
Enabled : yes
Starts after : boot-user
Current : yes
Allowed : root
Symlinks : svc->source db->source
Contents : /
├─(805,Enabled,classic) wpa_supplicant-log
├─(856,Enabled,classic) wpa_supplicant
├─(810,Enabled,classic) openntpd-log
├─(809,Enabled,classic) openntpd
├─(808,Enabled,classic) tty@ tty2
├─(811,Enabled,classic) tty@ tty1
├─(839,Enabled,longrun) dbus-log
├─(843,Enabled,longrun) dbus
├─(838,Enabled,longrun) networkmanager-log
├─(855,Enabled,longrun) networkmanager
├─(837,Enabled,longrun) sddm-log
└─(854,Enabled,longrun) sddm
Name : uras
Initialized : no
Enabled : yes
Starts after : boot-user root
Current : no
Allowed : root
Symlinks : svc->source db->source
Contents : /
└─None
------------------------------------------------------------------------
Name : boot-user
Initialized : no
Enabled : yes
Starts after : graphics
Current : no
Allowed : uras
Symlinks : svc->source db->source
Contents : /
└─None
Name : graphics
Initialized : yes
Enabled : yes
Starts after : None
Current : yes
Allowed : uras
Symlinks : svc->source db->source
Contents : /
├─(up,Enabled,oneshot) xdg-user-dirs
├─(982,Enabled,longrun) dbus-session@ uras-log
└─(986,Enabled,longrun) dbus-session@ uras
------------------------------------------------------------------------
As to the question of 'working', I cannot directly attribute any actual
malfunction other than the plethora of 'complaints' issued when I run
either geany or thunar under sudo. For all I know, it could be the
source of the btrfs problem.
Turning to btrfs, I 're-arranged the deck chairs' and configured the two
disks used for the btrfs 'pools' thusly:
sda1 - Single (data=1 mdata=dup) filesystem (label=POOL)
sda2 - 1st member of Raid1 (as btrfs defines it) (data=raid1 mdata=raid1)
(label=POND)
sdb1 - Empty unformatted partition (intended second member of POOL in
Raid1 configuration)
sdb2 - 2nd member member of Raid1 filesystem POND
I then 'copied' the contents of the POOL filesystem into the POND
filesystem.
Note that ALL of this was done under Obarun (no SystemRescueCd) using
gparted to create Single filesystems and btrfs commands to then produce
the Raid1 POND.
The POND filesystem appears to operate without flaw, but I have yet to
explore the question of booting it (today's exercise). From past
experience, I expect the same failure as before. In short, I suspect
this is strictly a 'boot' problem.
So, turning to the boot configuration:
The bootloader is Linux (EFI-stub).
The bootmanager is rEFInd.
The rEFInd 'stanza' used for boot is
menuentry "Obarun (Arch) Linux" {
icon EFI/BOOT/icons/os_arch.png
ostype Linux
volume POOL
loader svols/@ DIST_obarun/boot/vmlinuz-linux
initrd svols/@ DIST_obarun/boot/initramfs-linux.img
options "root=LABEL=POOL rootflags=subvol=svols/@ DIST_obarun rw add_efi_memmap"
}
The fstab is
LABEL=POOL / btrfs rw,noatime,space_cache,subvol=svols/@ DIST_obarun 0 1
LABEL=POOL /.fstop btrfs rw,noatime,space_cache,noauto,subvolid=5 0 2
LABEL=POOL /home/uras/URAS@ btrfs rw,noatime,space_cache,subvol=svols/@ URAS 0 3
LABEL=POOL /home/uras/URAS@ _nobup btrfs rw,noatime,space_cache,subvol=svols/@ URAS_nobup 0 4
BTRFS=!yes was set when it was first suggested and remains so.
It has had no effect.
Some other notes:
Subvolume names start with '@ ' (a reflection of my Ubuntu past)
Top-level (5) is used to hold the snapshots (which, being subvolumes,
have names starting with '@ '). In addition to the snapshots, there is
one directory 'svols', which contains the 'working' subvolumes.
The 'working' subvolume is either a 'Distro' or user-data which is
INDEPENDANT of any 'Distro'. 'Distro' users link to their corresponding
subvolumes.
There are NO 'nested' subvolumes.
Hopefully, I have covered everything.
To me, this seems strictly related to booting a multi-device filesystem.
The same parameters work fine if the filesystem is one device.
Thanks for your support.
jbkeh
Update: As expected, the "re-arranged" RAID1 failed in exactly the same manner (different bogus uuid).
eric
first dbus problem:
Your trees don't start in a good order.The field "Start After" show you the name of tree started before the inquired one. Boot-user tree should start after the root tree.
% sudo 66-tree -S root boot-user
Do you need an empty tree? The following command remove the tree uras:
% sudo 66-tree -R uras
Note: never remove a running tree with service inside without using the -U options (see 66-tree documentation for further information).
Equal for the user uras tree
% 66-tree -R uras
Please try to enable consolekit on your root tree.
% sudo pacman -S consolekit-66serv
% sudo 66-enable -t root consolekit
Consolekit should start after a reboot. You can start consolekit directly (66-start -t root consolekit) but dbus is stubborn and sometime need a reboot to work properly.
Btrfs:
First, i need to be honest here. I never used btrfs and it's the very first time that an user ask for it.
So, the devices-btfrs service just do:
btrfs device scan
This service is started after udevd and before mounting the / in rw permissions.
So, please change rw by ro on your menuentry
options "root=LABEL=POOL rootflags=subvol=svols/@ DIST_obarun ro add_efi_memmap"
This is the default behavior on Obarun. The boot set of service do a huge number of commands in ro permissions before switching to rw permissions like devices-btrfs service.
As far as can tell the others configurations seems correct for me, but again i'm not accustomed to btrfs volume.
But, do you have any information in your uncaught-logs? Please edit your /etc/66/init.conf and set VERBOSITY=3. Reboot and post here the content of the /run/66/log/0/current file.
Many many thanks for your reports and for testing this. This is really appreciated.
jbkeh
In regard to BTRFS, I am sorry to say changing from "rw" to "ro" made no difference (single device filesystem boots, multiple device filesystem fails).
Could I please ask that you 'flesh out' your advice in regard to dbus? An ominous reference to -U without a pointer to the relevant documentation (or a straight example) will leave me wandering through reams of documentation I really don't understand searching for 'something' I must do or my system may be destroyed.
Thanks.
eric
Could I please ask that you 'flesh out' your advice in regard to dbus?
yes, sure. But this is not concerning only dbus but the start order of your tree at boot time. You can have strange or expected behavior if you don't set it correctly. Also, the consolekit service concern permissions issue. But it's up to you :).
pointer to the relevant documentation (or a straight example)
online documentation:
https://web.obarun.org/software/66/66-tree.html
on your machine: man 66-tree or /usr/share/doc/66/66-tree.html
not so difficult to find it ;).
In regard to BTRFS, I am sorry to say changing from "rw" to "ro" made no difference (single device filesystem boots, multiple device filesystem fails).
Please show us the uncaught-logs as ask in my previous post. This will really much relevant as information than what you said me.
jbkeh
As requested (all 535 lines)
(An aside - when setting VERBOSITY=3, I noted that the second to last line was
RESCAN=0)
@ 400000005ef0c95c20f71d28 [Initiate db of tree boot...]
@ 400000005ef0c95c211eb434 66-init: tracing: initiate db of tree: boot ...
@ 400000005ef0c95c22471dc0 66-init: tracing: Write state file of: system-hostname
@ 400000005ef0c95c224728ca 66-init: info: Initialized successfully: system-hostname
@ 400000005ef0c95c22473958 66-init: tracing: Write state file of: mount-run
@ 400000005ef0c95c22474029 66-init: info: Initialized successfully: mount-run
@ 400000005ef0c95c22474619 66-init: tracing: Write state file of: populate-run
@ 400000005ef0c95c2247a561 66-init: info: Initialized successfully: populate-run
@ 400000005ef0c95c2247aa98 66-init: tracing: Write state file of: mount-tmp
@ 400000005ef0c95c2247aecf 66-init: info: Initialized successfully: mount-tmp
@ 400000005ef0c95c2247b394 66-init: tracing: Write state file of: populate-tmp
@ 400000005ef0c95c2247ebb6 66-init: info: Initialized successfully: populate-tmp
@ 400000005ef0c95c22481fae 66-init: tracing: Write state file of: mount-proc
@ 400000005ef0c95c2248541e 66-init: info: Initialized successfully: mount-proc
@ 400000005ef0c95c224858af 66-init: tracing: Write state file of: mount-sys
@ 400000005ef0c95c2248fd10 66-init: info: Initialized successfully: mount-sys
@ 400000005ef0c95c224901db 66-init: tracing: Write state file of: populate-sys
@ 400000005ef0c95c2249385b 66-init: info: Initialized successfully: populate-sys
@ 400000005ef0c95c22496b16 66-init: tracing: Write state file of: mount-dev
@ 400000005ef0c95c22499de9 66-init: info: Initialized successfully: mount-dev
@ 400000005ef0c95c2249a24d 66-init: tracing: Write state file of: mount-pts
@ 400000005ef0c95c224a1178 66-init: info: Initialized successfully: mount-pts
@ 400000005ef0c95c224a16b9 66-init: tracing: Write state file of: mount-shm
@ 400000005ef0c95c224a7af0 66-init: info: Initialized successfully: mount-shm
@ 400000005ef0c95c224a7f7f 66-init: tracing: Write state file of: populate-dev
@ 400000005ef0c95c224ad795 66-init: info: Initialized successfully: populate-dev
@ 400000005ef0c95c224adc36 66-init: tracing: Write state file of: mount-cgroups
@ 400000005ef0c95c224b3b12 66-init: info: Initialized successfully: mount-cgroups
@ 400000005ef0c95c224b4001 66-init: tracing: Write state file of: 00
@ 400000005ef0c95c224b9b6f 66-init: info: Initialized successfully: 00
@ 400000005ef0c95c224ba005 66-init: tracing: Write state file of: all-Mount
@ 400000005ef0c95c224c2715 66-init: info: Initialized successfully: all-Mount
@ 400000005ef0c95c224c2bcb 66-init: tracing: Write state file of: system-hwclock
@ 400000005ef0c95c224c61d7 66-init: info: Initialized successfully: system-hwclock
@ 400000005ef0c95c224c6641 66-init: tracing: Write state file of: modules-kernel
@ 400000005ef0c95c224cc350 66-init: info: Initialized successfully: modules-kernel
@ 400000005ef0c95c224cc7f8 66-init: tracing: Write state file of: system-random
@ 400000005ef0c95c224d2401 66-init: info: Initialized successfully: system-random
@ 400000005ef0c95c224d28e3 66-init: tracing: Write state file of: modules-system
@ 400000005ef0c95c224d8626 66-init: info: Initialized successfully: modules-system
@ 400000005ef0c95c224d8ab4 66-init: tracing: Write state file of: system-sysctl
@ 400000005ef0c95c224df053 66-init: info: Initialized successfully: system-sysctl
@ 400000005ef0c95c224df4e0 66-init: tracing: Write state file of: udevd
@ 400000005ef0c95c224e5474 66-init: info: Initialized successfully: udevd
@ 400000005ef0c95c224e5924 66-init: tracing: Write state file of: udevadm
@ 400000005ef0c95c224eb542 66-init: info: Initialized successfully: udevadm
@ 400000005ef0c95c224eb9c4 66-init: tracing: Write state file of: system-fontnkey
@ 400000005ef0c95c224f1612 66-init: info: Initialized successfully: system-fontnkey
@ 400000005ef0c95c224f1adf 66-init: tracing: Write state file of: devices-dmraid
@ 400000005ef0c95c224f7333 66-init: info: Initialized successfully: devices-dmraid
@ 400000005ef0c95c224f77d0 66-init: tracing: Write state file of: devices-btrfs
@ 400000005ef0c95c224fd240 66-init: info: Initialized successfully: devices-btrfs
@ 400000005ef0c95c224fd6f3 66-init: tracing: Write state file of: devices-crypttab
@ 400000005ef0c95c2250388c 66-init: info: Initialized successfully: devices-crypttab
@ 400000005ef0c95c22503d7b 66-init: tracing: Write state file of: devices-lvm
@ 400000005ef0c95c2250759a 66-init: info: Initialized successfully: devices-lvm
@ 400000005ef0c95c225079de 66-init: tracing: Write state file of: devices-zfs
@ 400000005ef0c95c2250db8d 66-init: info: Initialized successfully: devices-zfs
@ 400000005ef0c95c2250e049 66-init: tracing: Write state file of: system-Devices
@ 400000005ef0c95c22513ac7 66-init: info: Initialized successfully: system-Devices
@ 400000005ef0c95c22513f61 66-init: tracing: Write state file of: system-fsck
@ 400000005ef0c95c2251b9bb 66-init: info: Initialized successfully: system-fsck
@ 400000005ef0c95c2251be68 66-init: tracing: Write state file of: mount-fstab
@ 400000005ef0c95c22521b3a 66-init: info: Initialized successfully: mount-fstab
@ 400000005ef0c95c22521ff3 66-init: tracing: Write state file of: all-System
@ 400000005ef0c95c22527990 66-init: info: Initialized successfully: all-System
@ 400000005ef0c95c22527e5f 66-init: tracing: Write state file of: mount-rw
@ 400000005ef0c95c2252d871 66-init: info: Initialized successfully: mount-rw
@ 400000005ef0c95c2252dd53 66-init: tracing: Write state file of: mount-swap
@ 400000005ef0c95c22533841 66-init: info: Initialized successfully: mount-swap
@ 400000005ef0c95c22533cd7 66-init: tracing: Write state file of: local-iptables
@ 400000005ef0c95c2253947d 66-init: info: Initialized successfully: local-iptables
@ 400000005ef0c95c22539949 66-init: tracing: Write state file of: local-ip6tables
@ 400000005ef0c95c22541da3 66-init: info: Initialized successfully: local-ip6tables
@ 400000005ef0c95c2254230c 66-init: tracing: Write state file of: local-loop
@ 400000005ef0c95c22545935 66-init: info: Initialized successfully: local-loop
@ 400000005ef0c95c22545d8b 66-init: tracing: Write state file of: local-sethostname
@ 400000005ef0c95c2254b8b6 66-init: info: Initialized successfully: local-sethostname
@ 400000005ef0c95c2254bd8b 66-init: tracing: Write state file of: local-time
@ 400000005ef0c95c22551d9b 66-init: info: Initialized successfully: local-time
@ 400000005ef0c95c22552269 66-init: tracing: Write state file of: local-authfiles
@ 400000005ef0c95c2255803a 66-init: info: Initialized successfully: local-authfiles
@ 400000005ef0c95c225584c9 66-init: tracing: Write state file of: local-tmpfiles
@ 400000005ef0c95c2255e004 66-init: info: Initialized successfully: local-tmpfiles
@ 400000005ef0c95c2255e4d0 66-init: tracing: Write state file of: local-rc
@ 400000005ef0c95c22563e54 66-init: info: Initialized successfully: local-rc
@ 400000005ef0c95c225642ef 66-init: tracing: Write state file of: local-dmesg
@ 400000005ef0c95c2256a139 66-init: info: Initialized successfully: local-dmesg
@ 400000005ef0c95c2256a5e3 66-init: tracing: Write state file of: all-Local
@ 400000005ef0c95c2256fe44 66-init: info: Initialized successfully: all-Local
@ 400000005ef0c95c225702e6 66-init: tracing: Write state file of: all-Runtime
@ 400000005ef0c95c22577250 66-init: info: Initialized successfully: all-Runtime
@ 400000005ef0c95c22577712 66-init: tracing: Write state file of: All
@ 400000005ef0c95c2257d483 66-init: info: Initialized successfully: All
@ 400000005ef0c95c22771e82 [Start db services of tree boot...]
@ 400000005ef0c95c233c7ac3 s6-rc: info: bringing selected services up
@ 400000005ef0c95c234b3e0d s6-rc: info: processing service s6rc-oneshot-runner: starting
@ 400000005ef0c95c240c36ec s6-rc: info: service s6rc-oneshot-runner started successfully
@ 400000005ef0c95c2425fc95 s6-rc: info: processing service system-hostname: starting
@ 400000005ef0c95c242c5bfd s6-rc: info: processing service mount-tmp: starting
@ 400000005ef0c95c24320504 s6-rc: info: processing service mount-run: starting
@ 400000005ef0c95c2439ce9a s6-rc: info: processing service mount-proc: starting
@ 400000005ef0c95c25216ca2 [system-hostname] starts...
@ 400000005ef0c95c257768e4 [system-hostname] started successfully
@ 400000005ef0c95c257fe4e4 s6-rc: info: service system-hostname started successfully
@ 400000005ef0c95c262e8749 s6-rc: info: service mount-run started successfully
@ 400000005ef0c95c2635a106 s6-rc: info: processing service populate-run: starting
@ 400000005ef0c95c2637fe33 s6-rc: info: service mount-proc started successfully
@ 400000005ef0c95c263d849f s6-rc: info: processing service mount-sys: starting
@ 400000005ef0c95c265f0688 [mount-tmp] starts...
@ 400000005ef0c95c26bc6008 [mount-tmp] started successfully
@ 400000005ef0c95c26bf7bdd [populate-run] starts...
@ 400000005ef0c95c26c80582 s6-rc: info: service mount-tmp started successfully
@ 400000005ef0c95c26cd98a1 s6-rc: info: processing service populate-tmp: starting
@ 400000005ef0c95c26ecee9d s6-rc: info: service mount-sys started successfully
@ 400000005ef0c95c26fa1ca3 s6-rc: info: processing service populate-sys: starting
@ 400000005ef0c95c26ff3b3f s6-rc: info: processing service mount-dev: starting
@ 400000005ef0c95c2747ca81 [populate-tmp] starts...
@ 400000005ef0c95c276aee76 [populate-sys] starts...
@ 400000005ef0c95c27818099 s6-rc: info: service mount-dev started successfully
@ 400000005ef0c95c278424c5 s6-rc: info: processing service populate-dev: starting
@ 400000005ef0c95c278707f2 s6-rc: info: processing service mount-shm: starting
@ 400000005ef0c95c279be280 s6-rc: info: processing service mount-pts: starting
@ 400000005ef0c95c279be8a5 s6-rc: info: processing service mount-cgroups: starting
@ 400000005ef0c95c279ee0cb s6-rc: info: processing service devices-zfs: starting
@ 400000005ef0c95c27d27f7c [populate-dev] starts...
@ 400000005ef0c95c27ec96ae [populate-tmp] started successfully
@ 400000005ef0c95c27f02e72 s6-rc: info: service populate-tmp started successfully
@ 400000005ef0c95c27f65219 [populate-run] started successfully
@ 400000005ef0c95c27fa1c9e s6-rc: info: service populate-run started successfully
@ 400000005ef0c95c27fdd5e5 [mount-pts] starts...
@ 400000005ef0c95c280321d7 [mount-shm] starts...
@ 400000005ef0c95c281e16f0 [devices-zfs] deactivated
@ 400000005ef0c95c28267a06 s6-rc: info: service devices-zfs started successfully
@ 400000005ef0c95c28319bda [mount-cgroups] starts...
@ 400000005ef0c95c28458ed3 [mount-pts] started successfully
@ 400000005ef0c95c2848c30e s6-rc: info: service mount-pts started successfully
@ 400000005ef0c95c2862afc7 [mount-shm] started successfully
@ 400000005ef0c95c286e3baa s6-rc: info: service mount-shm started successfully
@ 400000005ef0c95c2885b57d [populate-dev] started successfully
@ 400000005ef0c95c2888eb6e s6-rc: info: service populate-dev started successfully
@ 400000005ef0c95c28e4de68 [populate-sys] started successfully
@ 400000005ef0c95c28e8e3f5 s6-rc: info: service populate-sys started successfully
@ 400000005ef0c95c2b21fe05 [mount-cgroups] started successfully
@ 400000005ef0c95c2b264daa s6-rc: info: service mount-cgroups started successfully
@ 400000005ef0c95c2b288507 s6-rc: info: processing service system-sysctl: starting
@ 400000005ef0c95c2b2991b6 s6-rc: info: processing service system-random: starting
@ 400000005ef0c95c2b33b823 s6-rc: info: processing service system-hwclock: starting
@ 400000005ef0c95c2b33bad1 s6-rc: info: processing service modules-system: starting
@ 400000005ef0c95c2b33bc11 s6-rc: info: processing service modules-kernel: starting
@ 400000005ef0c95c2b49b9e5 [system-random] starts...
@ 400000005ef0c95c2b515962 [modules-kernel] starts...
@ 400000005ef0c95c2b51afbb [modules-system] starts...
@ 400000005ef0c95c2b5ce67e [system-hwclock] starts...
@ 400000005ef0c95c2b60a15b [system-sysctl] starts...
@ 400000005ef0c95c2be3c4b4 [system-random] started successfully
@ 400000005ef0c95c2be63e14 s6-rc: info: service system-random started successfully
@ 400000005ef0c95c2c194926 kernel.sysrq = 1
@ 400000005ef0c95c2c194b9a kernel.core_uses_pid = 1
@ 400000005ef0c95c2c194cb7 fs.protected_hardlinks = 1
@ 400000005ef0c95c2c194dac fs.protected_symlinks = 1
@ 400000005ef0c95c2c194ec2 fs.inotify.max_user_instances = 1024
@ 400000005ef0c95c2c194ffb fs.inotify.max_user_watches = 524288
@ 400000005ef0c95c2c28418a [system-sysctl] started successfully
@ 400000005ef0c95c2c2ba02a s6-rc: info: service system-sysctl started successfully
@ 400000005ef0c95c2dc7a5d7 [system-hwclock] started successfully
@ 400000005ef0c95c2dccd9a0 s6-rc: info: service system-hwclock started successfully
@ 400000005ef0c95c2e1ef09e /usr/lib/66/scripts/modules.sh: No modules found -- nothing to do
@ 400000005ef0c95c2e39b691 [modules-system] started successfully
@ 400000005ef0c95c2e3f1445 s6-rc: info: service modules-system started successfully
@ 400000005ef0c95d03be0885 [modules-kernel] started successfully
@ 400000005ef0c95d03c83e4f s6-rc: info: service modules-kernel started successfully
@ 400000005ef0c95d03ced757 s6-rc: info: processing service udevd: starting
@ 400000005ef0c95d0446783d [udevd] starts...
@ 400000005ef0c95e056b01f7 s6-rc: info: service udevd started successfully
@ 400000005ef0c95e05710042 s6-rc: info: processing service udevadm: starting
@ 400000005ef0c95e05e62a05 [udevadm] starts...
@ 400000005ef0c95f0715458a [udevadm] started successfully
@ 400000005ef0c95f071d15c8 s6-rc: info: service udevadm started successfully
@ 400000005ef0c95f07223b5b s6-rc: info: processing service system-fontnkey: starting
@ 400000005ef0c95f07269d35 s6-rc: info: processing service devices-lvm: starting
@ 400000005ef0c95f07532a14 s6-rc: info: processing service devices-dmraid: starting
@ 400000005ef0c95f075336a2 s6-rc: info: processing service devices-crypttab: starting
@ 400000005ef0c95f07579de2 s6-rc: info: processing service devices-btrfs: starting
@ 400000005ef0c95f07f38c40 [system-fontnkey] starts...
@ 400000005ef0c95f07f592f3 [devices-dmraid] deactivated
@ 400000005ef0c95f081ccba4 s6-rc: info: service devices-dmraid started successfully
@ 400000005ef0c95f082a1d7e [devices-crypttab] deactivated
@ 400000005ef0c95f0831f813 s6-rc: info: service devices-crypttab started successfully
@ 400000005ef0c95f08350a72 [devices-btrfs] starts...
@ 400000005ef0c95f0844e531 [devices-lvm] deactivated
@ 400000005ef0c95f084bf71c s6-rc: info: service devices-lvm started successfully
@ 400000005ef0c95f0c3e0c94 [system-fontnkey] started successfully
@ 400000005ef0c95f0c435f9f s6-rc: info: service system-fontnkey started successfully
@ 400000005ef0c95f1457656c Scanning for Btrfs filesystems
@ 400000005ef0c95f145c9822 [devices-btrfs] started successfully
@ 400000005ef0c95f145e9203 s6-rc: info: service devices-btrfs started successfully
@ 400000005ef0c95f145fa78c s6-rc: info: processing service system-fsck: starting
@ 400000005ef0c95f148c53bb [system-fsck] starts...
@ 400000005ef0c95f14ef8551 [system-fsck] started successfully
@ 400000005ef0c95f14f12bc2 s6-rc: info: service system-fsck started successfully
@ 400000005ef0c95f14f2331a s6-rc: info: processing service mount-fstab: starting
@ 400000005ef0c95f151c7f79 [mount-fstab] starts...
@ 400000005ef0c95f156622f3 [mount-fstab] started successfully
@ 400000005ef0c95f1567e0d7 s6-rc: info: service mount-fstab started successfully
@ 400000005ef0c95f1568e514 s6-rc: info: processing service mount-rw: starting
@ 400000005ef0c95f1585e660 [mount-rw] starts...
@ 400000005ef0c95f15989ebd [mount-rw] started successfully
@ 400000005ef0c95f159a2c07 s6-rc: info: service mount-rw started successfully
@ 400000005ef0c95f159b3cab s6-rc: info: processing service mount-swap: starting
@ 400000005ef0c95f159c3d9a s6-rc: info: processing service local-tmpfiles: starting
@ 400000005ef0c95f15addd73 s6-rc: info: processing service local-time: starting
@ 400000005ef0c95f15ade0b9 s6-rc: info: processing service local-sethostname: starting
@ 400000005ef0c95f15ade21b s6-rc: info: processing service local-iptables: starting
@ 400000005ef0c95f15ade364 s6-rc: info: processing service local-ip6tables: starting
@ 400000005ef0c95f15ae1eef s6-rc: info: processing service local-authfiles: starting
@ 400000005ef0c95f15da4008 [local-iptables] deactivated
@ 400000005ef0c95f15dcd4df s6-rc: info: service local-iptables started successfully
@ 400000005ef0c95f15dd23a8 [local-sethostname] starts...
@ 400000005ef0c95f15de57df [local-time] starts...
@ 400000005ef0c95f15dfb64e [mount-swap] deactivated
@ 400000005ef0c95f15e24fd7 [local-authfiles] starts...
@ 400000005ef0c95f15e3bc61 s6-rc: info: service mount-swap started successfully
@ 400000005ef0c95f15e60c91 [local-tmpfiles] starts...
@ 400000005ef0c95f169f78b7 [local-ip6tables] deactivated
@ 400000005ef0c95f16a1644a s6-rc: info: service local-ip6tables started successfully
@ 400000005ef0c95f16a5a4f5 s6-rc: info: processing service local-loop: starting
@ 400000005ef0c95f16a6ce08 s6-rc: info: service local-sethostname started successfully
@ 400000005ef0c95f16aa2322 [local-time] started successfully
@ 400000005ef0c95f16acac2a s6-rc: info: service local-time started successfully
@ 400000005ef0c95f16c1df1d [local-loop] starts...
@ 400000005ef0c95f16cad787 [local-authfiles] started successfully
@ 400000005ef0c95f16cc9018 s6-rc: info: service local-authfiles started successfully
@ 400000005ef0c95f170814f0 _d /var/lib/colord 0755 colord colord 0
@ 400000005ef0c95f178c1ad3 _d /var/lib/colord/icc 0755 colord colord 0
@ 400000005ef0c95f1794fb52 [local-loop] started successfully
@ 400000005ef0c95f179a2a38 s6-rc: info: service local-loop started successfully
@ 400000005ef0c95f17a9b6ad _d /run/ConsoleKit 0755 0 0 0
@ 400000005ef0c95f17cd984f _d /run/dbus 0755 0 0 0
@ 400000005ef0c95f17ef720e _d /var/lib/dhcpcd 0700 dhcpcd dhcpcd 0
@ 400000005ef0c95f1807b58c _d /run/dhcpcd 0755 dhcpcd dhcpcd 0
@ 400000005ef0c95f1827ee59 _w /sys/devices/system/cpu/microcode/reload - 0 0 0 1
@ 400000005ef0c95f182ac79d _d /run/lirc 0755 root root 0
@ 400000005ef0c95f1848c36e _d /var/cache/man 0755 root root 1w
@ 400000005ef0c95f1863546b _d /run/initramfs 0755 root root 0
@ 400000005ef0c95f187dd689 _d /run/nscd 0755 root root 0
@ 400000005ef0c95f189db102 _C /etc/crypttab 0 0 0
@ 400000005ef0c95f189f9e8e _C /etc/fstab 0 0 0
@ 400000005ef0c95f18a1535d _C /etc/group 0 0 0
@ 400000005ef0c95f18a2efc8 _C /etc/gshadow 0 0 0
@ 400000005ef0c95f18a4f013 _C /etc/host.conf 0 0 0
@ 400000005ef0c95f18a69c00 _C /etc/hosts 0 0 0
@ 400000005ef0c95f18a84c5f _C /etc/issue 0 0 0
@ 400000005ef0c95f18a940d3 _C /etc/ld.so.conf 0 0 0
@ 400000005ef0c95f18aa8da3 _C /etc/motd 0 0 0
@ 400000005ef0c95f18abdb39 _C /etc/nsswitch.conf 0 0 0
@ 400000005ef0c95f18ad1526 _C /etc/passwd 0 0 0
@ 400000005ef0c95f18ae4ca4 _C /etc/profile 0 0 0
@ 400000005ef0c95f18af9ae5 _C /etc/securetty 0 0 0
@ 400000005ef0c95f18b166f6 _C /etc/shadow 0 0 0
@ 400000005ef0c95f18b2b2cd _C /etc/shells 0 0 0
@ 400000005ef0c95f18b4747a _d /var/lib/sddm 0755 sddm sddm 0
@ 400000005ef0c95f18d221b6 _d /var/empty 0755 root root 0
@ 400000005ef0c95f18ee8d44 _d /run/sudo 0711 root root 0
@ 400000005ef0c95f190ce643 _D /run/sudo/ts 0700 root root 0
@ 400000005ef0c95f1931dc51 [local-tmpfiles] started successfully
@ 400000005ef0c95f193668f5 s6-rc: info: service local-tmpfiles started successfully
@ 400000005ef0c95f19388fdc s6-rc: info: processing service local-rc: starting
@ 400000005ef0c95f196ccc06 [local-rc] deactivated
@ 400000005ef0c95f19716342 s6-rc: info: service local-rc started successfully
@ 400000005ef0c95f19749270 s6-rc: info: processing service local-dmesg: starting
@ 400000005ef0c95f199b0d57 [local-dmesg] starts...
@ 400000005ef0c95f19cb0d36 [local-dmesg] started successfully
@ 400000005ef0c95f19ccb1c1 s6-rc: info: service local-dmesg started successfully
@ 400000005ef0c95f19cdb836 s6-rc: info: processing service all-Runtime: starting
@ 400000005ef0c95f1a0fe0e4 66-init: info: Initialization report: no classic services into tree: boot-user
@ 400000005ef0c95f1a10810f 66-init: tracing: point symlink: /run/66/state/0/boot-user/servicedirs to /var/lib/66/system/boot-user/servicedirs
@ 400000005ef0c95f1a109dbc 66-init: tracing: initiate db of tree: boot-user ...
@ 400000005ef0c95f1a30c068 66-init: tracing: Write state file of: mount-run-uras
@ 400000005ef0c95f1a30d464 66-init: info: Initialized successfully: mount-run-uras
@ 400000005ef0c95f1a30d5bc 66-init: tracing: Write state file of: setenv-uras
@ 400000005ef0c95f1a30e237 66-init: info: Initialized successfully: setenv-uras
@ 400000005ef0c95f1a30edbe 66-init: tracing: Write state file of: scandir-uras-log
@ 400000005ef0c95f1a30f944 66-init: info: Initialized successfully: scandir-uras-log
@ 400000005ef0c95f1a30fa41 66-init: tracing: Write state file of: scandir-uras
@ 400000005ef0c95f1a3110fb 66-init: info: Initialized successfully: scandir-uras
@ 400000005ef0c95f1a3111f8 66-init: tracing: Write state file of: All-uras
@ 400000005ef0c95f1a312475 66-init: info: Initialized successfully: All-uras
@ 400000005ef0c95f1a31e58f 66-all: tracing: reload scandir: /run/66/scandir/0
@ 400000005ef0c95f1a52e44d 66-start: tracing: sanitize atomic services list...
@ 400000005ef0c95f1a52f2ce 66-start: tracing: start atomic services list ...
@ 400000005ef0c95f1a6a219a s6-rc: info: bringing selected services up
@ 400000005ef0c95f1a6b54b1 s6-rc: info: processing service s6rc-fdholder: starting
@ 400000005ef0c95f1a6c5aee s6-rc: info: processing service s6rc-oneshot-runner: starting
@ 400000005ef0c95f1a89f4e2 s6-rc: info: service s6rc-oneshot-runner started successfully
@ 400000005ef0c95f1a8b0566 s6-rc: info: processing service setenv-uras: starting
@ 400000005ef0c95f1a8c0b3d s6-rc: info: processing service mount-run-uras: starting
@ 400000005ef0c95f1ac69a6a s6-rc: info: service s6rc-fdholder started successfully
@ 400000005ef0c95f1ac7d03c s6-rc: info: processing service scandir-uras-log: starting
@ 400000005ef0c95f1ad03d03 s6-rc: info: service mount-run-uras started successfully
@ 400000005ef0c95f1b8312e9 s6-rc: info: service setenv-uras started successfully
@ 400000005ef0c95f1bba3eea s6-rc: info: service scandir-uras-log started successfully
@ 400000005ef0c95f1bbb6217 s6-rc: info: processing service scandir-uras: starting
@ 400000005ef0c95f1c0b43b7 s6-rc: info: service scandir-uras started successfully
@ 400000005ef0c95f1c0c018c 66-start: tracing: Write state file of: mount-run-uras
@ 400000005ef0c95f1c0c2cfc 66-start: info: Started successfully: mount-run-uras
@ 400000005ef0c95f1c0c2e19 66-start: tracing: Write state file of: setenv-uras
@ 400000005ef0c95f1c0c4856 66-start: info: Started successfully: setenv-uras
@ 400000005ef0c95f1c0c60db 66-start: tracing: Write state file of: scandir-uras-log
@ 400000005ef0c95f1c0c7a3a 66-start: info: Started successfully: scandir-uras-log
@ 400000005ef0c95f1c0c8686 66-start: tracing: Write state file of: scandir-uras
@ 400000005ef0c95f1c0ca060 66-start: info: Started successfully: scandir-uras
@ 400000005ef0c95f1c0ca162 66-start: tracing: Write state file of: All-uras
@ 400000005ef0c95f1c0cb8f0 66-start: info: Started successfully: All-uras
@ 400000005ef0c95f1c0cc4a9 66-start: tracing: switch atomic services list of: boot-user to source
@ 400000005ef0c95f1c30cbb2 66-init: tracing: point symlink: /run/66/state/0/root/servicedirs to /var/lib/66/system/root/servicedirs
@ 400000005ef0c95f1c30e1b1 66-init: tracing: init service: tty@ tty1
@ 400000005ef0c95f1c30eea6 66-init: tracing: copy: /var/lib/66/system/root/servicedirs/svc/tty@ tty1 to /run/66/scandir/0/tty@ tty1
@ 400000005ef0c95f1c319251 66-init: tracing: create file: /run/66/scandir/0/tty@ tty1/down
@ 400000005ef0c95f1c31a6b0 66-init: tracing: create fifo: /run/66/scandir/0/tty@ tty1/event
@ 400000005ef0c95f1c31bce3 66-init: tracing: subcribe to fifo: /run/66/scandir/0/tty@ tty1/event
@ 400000005ef0c95f1c326997 66-init: tracing: init service: tty@ tty2
@ 400000005ef0c95f1c327552 66-init: tracing: copy: /var/lib/66/system/root/servicedirs/svc/tty@ tty2 to /run/66/scandir/0/tty@ tty2
@ 400000005ef0c95f1c32ff30 66-init: tracing: create file: /run/66/scandir/0/tty@ tty2/down
@ 400000005ef0c95f1c330c0d 66-init: tracing: create fifo: /run/66/scandir/0/tty@ tty2/event
@ 400000005ef0c95f1c332417 66-init: tracing: subcribe to fifo: /run/66/scandir/0/tty@ tty2/event
@ 400000005ef0c95f1c337f71 66-init: tracing: init service: openntpd-log
@ 400000005ef0c95f1c338b18 66-init: tracing: copy: /var/lib/66/system/root/servicedirs/svc/openntpd to /run/66/scandir/0/openntpd
@ 400000005ef0c95f1c353abe 66-init: tracing: create file: /run/66/scandir/0/openntpd/log/down
@ 400000005ef0c95f1c354f5b 66-init: tracing: create fifo: /run/66/scandir/0/openntpd/log/event
@ 400000005ef0c95f1c35642c 66-init: tracing: subcribe to fifo: /run/66/scandir/0/openntpd/log/event
@ 400000005ef0c95f1c35c2e5 66-init: tracing: init service: openntpd
@ 400000005ef0c95f1c35ce70 66-init: tracing: create file: /run/66/scandir/0/openntpd/down
@ 400000005ef0c95f1c35d9c3 66-init: tracing: create fifo: /run/66/scandir/0/openntpd/event
@ 400000005ef0c95f1c35ec5f 66-init: tracing: subcribe to fifo: /run/66/scandir/0/openntpd/event
@ 400000005ef0c95f1c36400f 66-init: tracing: init service: wpa_supplicant-log
@ 400000005ef0c95f1c364c29 66-init: tracing: copy: /var/lib/66/system/root/servicedirs/svc/wpa_supplicant to /run/66/scandir/0/wpa_supplicant
@ 400000005ef0c95f1c37ad80 66-init: tracing: create file: /run/66/scandir/0/wpa_supplicant/log/down
@ 400000005ef0c95f1c37b9c8 66-init: tracing: create fifo: /run/66/scandir/0/wpa_supplicant/log/event
@ 400000005ef0c95f1c37d130 66-init: tracing: subcribe to fifo: /run/66/scandir/0/wpa_supplicant/log/event
@ 400000005ef0c95f1c382859 66-init: tracing: init service: wpa_supplicant
@ 400000005ef0c95f1c383474 66-init: tracing: create file: /run/66/scandir/0/wpa_supplicant/down
@ 400000005ef0c95f1c383fc1 66-init: tracing: create fifo: /run/66/scandir/0/wpa_supplicant/event
@ 400000005ef0c95f1c3853a2 66-init: tracing: subcribe to fifo: /run/66/scandir/0/wpa_supplicant/event
@ 400000005ef0c95f1c38abcf 66-init: tracing: reload scandir: /run/66/scandir/0
@ 400000005ef0c95f1c38c2d1 66-init: tracing: waiting for events on fifo
@ 400000005ef0c95f1c42f8fe 66-init: tracing: delete down file at: /run/66/scandir/0/tty@ tty1/down
@ 400000005ef0c95f1c430bc1 66-init: tracing: delete down file at: /run/66/scandir/0/tty@ tty2/down
@ 400000005ef0c95f1c430ce9 66-init: tracing: delete down file at: /run/66/scandir/0/openntpd/log/down
@ 400000005ef0c95f1c4318e5 66-init: tracing: delete down file at: /run/66/scandir/0/openntpd/down
@ 400000005ef0c95f1c4319f5 66-init: tracing: delete down file at: /run/66/scandir/0/wpa_supplicant/log/down
@ 400000005ef0c95f1c432571 66-init: tracing: delete down file at: /run/66/scandir/0/wpa_supplicant/down
@ 400000005ef0c95f1c4330e9 66-init: tracing: Write state file of: tty@ tty1
@ 400000005ef0c95f1c434e11 66-init: info: Initialized successfully: tty@ tty1
@ 400000005ef0c95f1c434f25 66-init: tracing: Write state file of: tty@ tty2
@ 400000005ef0c95f1c436686 66-init: info: Initialized successfully: tty@ tty2
@ 400000005ef0c95f1c4367af 66-init: tracing: Write state file of: openntpd-log
@ 400000005ef0c95f1c43b0e4 66-init: info: Initialized successfully: openntpd-log
@ 400000005ef0c95f1c43b230 66-init: tracing: Write state file of: openntpd
@ 400000005ef0c95f1c43c121 66-init: info: Initialized successfully: openntpd
@ 400000005ef0c95f1c43c21e 66-init: tracing: Write state file of: wpa_supplicant-log
@ 400000005ef0c95f1c43e876 66-init: info: Initialized successfully: wpa_supplicant-log
@ 400000005ef0c95f1c43eb28 66-init: tracing: Write state file of: wpa_supplicant
@ 400000005ef0c95f1c43fd3b 66-init: info: Initialized successfully: wpa_supplicant
@ 400000005ef0c95f1c4543dc 66-init: tracing: initiate db of tree: root ...
@ 400000005ef0c95f1c82f3d3 66-init: tracing: Write state file of: dbus-log
@ 400000005ef0c95f1c8308f3 66-init: info: Initialized successfully: dbus-log
@ 400000005ef0c95f1c830a0d 66-init: tracing: Write state file of: dbus
@ 400000005ef0c95f1c8316d6 66-init: info: Initialized successfully: dbus
@ 400000005ef0c95f1c8317dc 66-init: tracing: Write state file of: networkmanager-log
@ 400000005ef0c95f1c833093 66-init: info: Initialized successfully: networkmanager-log
@ 400000005ef0c95f1c8331a0 66-init: tracing: Write state file of: networkmanager
@ 400000005ef0c95f1c834cad 66-init: info: Initialized successfully: networkmanager
@ 400000005ef0c95f1c834db1 66-init: tracing: Write state file of: sddm-log
@ 400000005ef0c95f1c836307 66-init: info: Initialized successfully: sddm-log
@ 400000005ef0c95f1c83641b 66-init: tracing: Write state file of: sddm
@ 400000005ef0c95f1c837940 66-init: info: Initialized successfully: sddm
@ 400000005ef0c95f1c844a67 66-all: tracing: reload scandir: /run/66/scandir/0
@ 400000005ef0c95f1c8be605 66-start: tracing: sanitize classic services list...
@ 400000005ef0c95f1c8be8b9 66-start: tracing: start classic services list ...
@ 400000005ef0c95f1c91cfba 66-start: tracing: clean up fifo: /run/66/scandir/0/wpa_supplicant/log/event
@ 400000005ef0c95f1c91f255 66-start: tracing: subcribe to fifo: /run/66/scandir/0/wpa_supplicant/log/event
@ 400000005ef0c95f1c929e36 66-start: tracing: clean up fifo: /run/66/scandir/0/wpa_supplicant/event
@ 400000005ef0c95f1c92b772 66-start: tracing: subcribe to fifo: /run/66/scandir/0/wpa_supplicant/event
@ 400000005ef0c95f1c930ee9 66-start: tracing: clean up fifo: /run/66/scandir/0/openntpd/log/event
@ 400000005ef0c95f1c9322fb 66-start: tracing: subcribe to fifo: /run/66/scandir/0/openntpd/log/event
@ 400000005ef0c95f1c936e4a 66-start: tracing: clean up fifo: /run/66/scandir/0/openntpd/event
@ 400000005ef0c95f1c93828d 66-start: tracing: subcribe to fifo: /run/66/scandir/0/openntpd/event
@ 400000005ef0c95f1c93d5f4 66-start: tracing: clean up fifo: /run/66/scandir/0/tty@ tty2/event
@ 400000005ef0c95f1c93eda1 66-start: tracing: subcribe to fifo: /run/66/scandir/0/tty@ tty2/event
@ 400000005ef0c95f1c9444aa 66-start: tracing: clean up fifo: /run/66/scandir/0/tty@ tty1/event
@ 400000005ef0c95f1c945887 66-start: tracing: subcribe to fifo: /run/66/scandir/0/tty@ tty1/event
@ 400000005ef0c95f1c958c67 66-start: tracing: send signal: uwU to: /run/66/scandir/0/wpa_supplicant/log/supervise
@ 400000005ef0c95f1c96735e 66-start: tracing: send signal: u to: /run/66/scandir/0/wpa_supplicant/supervise
@ 400000005ef0c95f1c96754d 66-start: tracing: send signal: uwU to: /run/66/scandir/0/openntpd/log/supervise
@ 400000005ef0c95f1c982ce9 66-start: tracing: send signal: u to: /run/66/scandir/0/tty@ tty2/supervise
@ 400000005ef0c95f1c982ecc 66-start: tracing: send signal: u to: /run/66/scandir/0/tty@ tty1/supervise
@ 400000005ef0c95f1cad570e 66-start: tracing: send signal: u to: /run/66/scandir/0/openntpd/supervise
@ 400000005ef0c95f1cb284ba 66-start: info: wpa_supplicant-log: started successfully
@ 400000005ef0c95f1cb2876b 66-start: tracing: Write state file of: wpa_supplicant-log
@ 400000005ef0c95f1cb28883 66-start: info: wpa_supplicant: started successfully
@ 400000005ef0c95f1cb2895b 66-start: tracing: Write state file of: wpa_supplicant
@ 400000005ef0c95f1cb28a40 66-start: info: openntpd-log: started successfully
@ 400000005ef0c95f1cb28b40 66-start: tracing: Write state file of: openntpd-log
@ 400000005ef0c95f1cb294fd 66-start: info: openntpd: started successfully
@ 400000005ef0c95f1cb2963b 66-start: tracing: Write state file of: openntpd
@ 400000005ef0c95f1cb2977e 66-start: info: tty@ tty2: started successfully
@ 400000005ef0c95f1cb29954 66-start: tracing: Write state file of: tty@ tty2
@ 400000005ef0c95f1cb29a97 66-start: info: tty@ tty1: started successfully
@ 400000005ef0c95f1cb29c3e 66-start: tracing: Write state file of: tty@ tty1
@ 400000005ef0c95f1cb69dd0 66-start: tracing: switch classic service list of: root to source
@ 400000005ef0c95f1cb6a00d 66-start: tracing: sanitize atomic services list...
@ 400000005ef0c95f1cb6a10b 66-start: tracing: start atomic services list ...
@ 400000005ef0c95f1cc120c2 s6-rc: info: bringing selected services up
@ 400000005ef0c95f1cc2417d s6-rc: info: processing service s6rc-fdholder: starting
@ 400000005ef0c95f1cf1ef78 s6-rc: info: service s6rc-fdholder started successfully
@ 400000005ef0c95f1cf305c6 s6-rc: info: processing service sddm-log: starting
@ 400000005ef0c95f1cf40212 s6-rc: info: processing service networkmanager-log: starting
@ 400000005ef0c95f1cf517fe s6-rc: info: processing service dbus-log: starting
@ 400000005ef0c95f1d1e8219 s6-rc: info: service sddm-log started successfully
@ 400000005ef0c95f1d1fb668 s6-rc: info: service networkmanager-log started successfully
@ 400000005ef0c95f1d226ac9 s6-rc: info: service dbus-log started successfully
@ 400000005ef0c95f1d23848f s6-rc: info: processing service dbus: starting
@ 400000005ef0c95f1eca51b4 s6-rc: info: service dbus started successfully
@ 400000005ef0c95f1ecb74db s6-rc: info: processing service sddm: starting
@ 400000005ef0c95f1ecc8f65 s6-rc: info: processing service networkmanager: starting
@ 400000005ef0c95f1ede9866 s6-rc: info: service sddm started successfully
@ 400000005ef0c95f1ee5e89d s6-rc: info: service networkmanager started successfully
@ 400000005ef0c95f1ee64e2c 66-start: tracing: Write state file of: dbus-log
@ 400000005ef0c95f1ee67485 66-start: info: Started successfully: dbus-log
@ 400000005ef0c95f1ee68799 66-start: tracing: Write state file of: dbus
@ 400000005ef0c95f1ee69e1d 66-start: info: Started successfully: dbus
@ 400000005ef0c95f1ee6b252 66-start: tracing: Write state file of: sddm-log
@ 400000005ef0c95f1ee6c9c8 66-start: info: Started successfully: sddm-log
@ 400000005ef0c95f1ee6d574 66-start: tracing: Write state file of: sddm
@ 400000005ef0c95f1ee6f065 66-start: info: Started successfully: sddm
@ 400000005ef0c95f1ee70413 66-start: tracing: Write state file of: networkmanager-log
@ 400000005ef0c95f1ee71c29 66-start: info: Started successfully: networkmanager-log
@ 400000005ef0c95f1ee727e0 66-start: tracing: Write state file of: networkmanager
@ 400000005ef0c95f1ee740e5 66-start: info: Started successfully: networkmanager
@ 400000005ef0c95f1ee74cbd 66-start: tracing: switch atomic services list of: root to source
@ 400000005ef0c95f1eeca408 66-all: info: empty tree: uras -- nothing to do
@ 400000005ef0c95f1eeed1fe s6-rc: info: service all-Runtime started successfully
@ 400000005ef0c95f1eef8d1e 66-dbctl: tracing: Write state file of: system-hostname
@ 400000005ef0c95f1eefaaa6 66-dbctl: info: Started successfully: system-hostname
@ 400000005ef0c95f1eefabcb 66-dbctl: tracing: Write state file of: mount-run
@ 400000005ef0c95f1eefc4e2 66-dbctl: info: Started successfully: mount-run
@ 400000005ef0c95f1eefc5ed 66-dbctl: tracing: Write state file of: populate-run
@ 400000005ef0c95f1eefdd09 66-dbctl: info: Started successfully: populate-run
@ 400000005ef0c95f1eefde23 66-dbctl: tracing: Write state file of: mount-tmp
@ 400000005ef0c95f1eeff4de 66-dbctl: info: Started successfully: mount-tmp
@ 400000005ef0c95f1eeff5f3 66-dbctl: tracing: Write state file of: populate-tmp
@ 400000005ef0c95f1ef00dfe 66-dbctl: info: Started successfully: populate-tmp
@ 400000005ef0c95f1ef00f0f 66-dbctl: tracing: Write state file of: mount-proc
@ 400000005ef0c95f1ef025c3 66-dbctl: info: Started successfully: mount-proc
@ 400000005ef0c95f1ef026db 66-dbctl: tracing: Write state file of: mount-sys
@ 400000005ef0c95f1ef03da8 66-dbctl: info: Started successfully: mount-sys
@ 400000005ef0c95f1ef03eb0 66-dbctl: tracing: Write state file of: populate-sys
@ 400000005ef0c95f1ef055c8 66-dbctl: info: Started successfully: populate-sys
@ 400000005ef0c95f1ef056d0 66-dbctl: tracing: Write state file of: mount-dev
@ 400000005ef0c95f1ef06dd9 66-dbctl: info: Started successfully: mount-dev
@ 400000005ef0c95f1ef06ee8 66-dbctl: tracing: Write state file of: mount-pts
@ 400000005ef0c95f1ef08615 66-dbctl: info: Started successfully: mount-pts
@ 400000005ef0c95f1ef0873d 66-dbctl: tracing: Write state file of: mount-shm
@ 400000005ef0c95f1ef09f87 66-dbctl: info: Started successfully: mount-shm
@ 400000005ef0c95f1ef0a08e 66-dbctl: tracing: Write state file of: populate-dev
@ 400000005ef0c95f1ef0b817 66-dbctl: info: Started successfully: populate-dev
@ 400000005ef0c95f1ef0b929 66-dbctl: tracing: Write state file of: mount-cgroups
@ 400000005ef0c95f1ef0d06d 66-dbctl: info: Started successfully: mount-cgroups
@ 400000005ef0c95f1ef0d177 66-dbctl: tracing: Write state file of: 00
@ 400000005ef0c95f1ef0e8bc 66-dbctl: info: Started successfully: 00
@ 400000005ef0c95f1ef0e9c9 66-dbctl: tracing: Write state file of: all-Mount
@ 400000005ef0c95f1ef0ffe8 66-dbctl: info: Started successfully: all-Mount
@ 400000005ef0c95f1ef100ef 66-dbctl: tracing: Write state file of: system-hwclock
@ 400000005ef0c95f1ef1187c 66-dbctl: info: Started successfully: system-hwclock
@ 400000005ef0c95f1ef11989 66-dbctl: tracing: Write state file of: modules-kernel
@ 400000005ef0c95f1ef12f67 66-dbctl: info: Started successfully: modules-kernel
@ 400000005ef0c95f1ef13069 66-dbctl: tracing: Write state file of: system-random
@ 400000005ef0c95f1ef146f4 66-dbctl: info: Started successfully: system-random
@ 400000005ef0c95f1ef1480c 66-dbctl: tracing: Write state file of: modules-system
@ 400000005ef0c95f1ef15e96 66-dbctl: info: Started successfully: modules-system
@ 400000005ef0c95f1ef15fa4 66-dbctl: tracing: Write state file of: system-sysctl
@ 400000005ef0c95f1ef176aa 66-dbctl: info: Started successfully: system-sysctl
@ 400000005ef0c95f1ef191b1 66-dbctl: tracing: Write state file of: udevd
@ 400000005ef0c95f1ef1a7bc 66-dbctl: info: Started successfully: udevd
@ 400000005ef0c95f1ef1a8d4 66-dbctl: tracing: Write state file of: udevadm
@ 400000005ef0c95f1ef1bfe4 66-dbctl: info: Started successfully: udevadm
@ 400000005ef0c95f1ef1c0db 66-dbctl: tracing: Write state file of: system-fontnkey
@ 400000005ef0c95f1ef1d8f1 66-dbctl: info: Started successfully: system-fontnkey
@ 400000005ef0c95f1ef1da1f 66-dbctl: tracing: Write state file of: devices-dmraid
@ 400000005ef0c95f1ef1efc1 66-dbctl: info: Started successfully: devices-dmraid
@ 400000005ef0c95f1ef1f0bc 66-dbctl: tracing: Write state file of: devices-btrfs
@ 400000005ef0c95f1ef20788 66-dbctl: info: Started successfully: devices-btrfs
@ 400000005ef0c95f1ef20893 66-dbctl: tracing: Write state file of: devices-crypttab
@ 400000005ef0c95f1ef21f27 66-dbctl: info: Started successfully: devices-crypttab
@ 400000005ef0c95f1ef22023 66-dbctl: tracing: Write state file of: devices-lvm
@ 400000005ef0c95f1ef237f2 66-dbctl: info: Started successfully: devices-lvm
@ 400000005ef0c95f1ef238ea 66-dbctl: tracing: Write state file of: devices-zfs
@ 400000005ef0c95f1ef24f00 66-dbctl: info: Started successfully: devices-zfs
@ 400000005ef0c95f1ef24ffd 66-dbctl: tracing: Write state file of: system-Devices
@ 400000005ef0c95f1ef267b0 66-dbctl: info: Started successfully: system-Devices
@ 400000005ef0c95f1ef268b3 66-dbctl: tracing: Write state file of: system-fsck
@ 400000005ef0c95f1ef28004 66-dbctl: info: Started successfully: system-fsck
@ 400000005ef0c95f1ef28100 66-dbctl: tracing: Write state file of: mount-fstab
@ 400000005ef0c95f1ef298d3 66-dbctl: info: Started successfully: mount-fstab
@ 400000005ef0c95f1ef299d5 66-dbctl: tracing: Write state file of: all-System
@ 400000005ef0c95f1ef2b0fd 66-dbctl: info: Started successfully: all-System
@ 400000005ef0c95f1ef2b1f2 66-dbctl: tracing: Write state file of: mount-rw
@ 400000005ef0c95f1ef2ca6a 66-dbctl: info: Started successfully: mount-rw
@ 400000005ef0c95f1ef2cb6c 66-dbctl: tracing: Write state file of: mount-swap
@ 400000005ef0c95f1ef2e261 66-dbctl: info: Started successfully: mount-swap
@ 400000005ef0c95f1ef2e35f 66-dbctl: tracing: Write state file of: local-iptables
@ 400000005ef0c95f1ef2f99b 66-dbctl: info: Started successfully: local-iptables
@ 400000005ef0c95f1ef2fa98 66-dbctl: tracing: Write state file of: local-ip6tables
@ 400000005ef0c95f1ef3117b 66-dbctl: info: Started successfully: local-ip6tables
@ 400000005ef0c95f1ef3127c 66-dbctl: tracing: Write state file of: local-loop
@ 400000005ef0c95f1ef329b9 66-dbctl: info: Started successfully: local-loop
@ 400000005ef0c95f1ef32ab7 66-dbctl: tracing: Write state file of: local-sethostname
@ 400000005ef0c95f1ef3432d 66-dbctl: info: Started successfully: local-sethostname
@ 400000005ef0c95f1ef3442c 66-dbctl: tracing: Write state file of: local-time
@ 400000005ef0c95f1ef35a97 66-dbctl: info: Started successfully: local-time
@ 400000005ef0c95f1ef35b92 66-dbctl: tracing: Write state file of: local-authfiles
@ 400000005ef0c95f1ef372ee 66-dbctl: info: Started successfully: local-authfiles
@ 400000005ef0c95f1ef373eb 66-dbctl: tracing: Write state file of: local-tmpfiles
@ 400000005ef0c95f1ef38b64 66-dbctl: info: Started successfully: local-tmpfiles
@ 400000005ef0c95f1ef38c62 66-dbctl: tracing: Write state file of: local-rc
@ 400000005ef0c95f1ef3a33e 66-dbctl: info: Started successfully: local-rc
@ 400000005ef0c95f1ef3a435 66-dbctl: tracing: Write state file of: local-dmesg
@ 400000005ef0c95f1ef3ba8d 66-dbctl: info: Started successfully: local-dmesg
@ 400000005ef0c95f1ef3bb88 66-dbctl: tracing: Write state file of: all-Local
@ 400000005ef0c95f1ef3d2c4 66-dbctl: info: Started successfully: all-Local
@ 400000005ef0c95f1ef3d3c4 66-dbctl: tracing: Write state file of: all-Runtime
@ 400000005ef0c95f1ef3ebb5 66-dbctl: info: Started successfully: all-Runtime
@ 400000005ef0c95f1ef3ecb2 66-dbctl: tracing: Write state file of: All
@ 400000005ef0c95f1ef40446 66-dbctl: info: Started successfully: All
jbkeh
And after applying the dbus changes, still no progress with both thunar and geany issuing 'complaints' under sudo (thunar immediately, geany when it is asked to load a file).
The current version of consolekit was missing.
Here are the 66-intree -g (s) as they now stand.
Name : boot
Initialized : yes
Enabled : no
Starts after : None
Current : no
Allowed : root
Symlinks : svc->source db->source
Contents : /
├─(239,Enabled,classic) tty12
├─(up,Enabled,oneshot) system-hostname
├─(up,Enabled,oneshot) mount-run
├─(up,Enabled,oneshot) populate-run
├─(up,Enabled,oneshot) mount-tmp
├─(up,Enabled,oneshot) populate-tmp
├─(up,Enabled,oneshot) mount-proc
├─(up,Enabled,oneshot) mount-sys
├─(up,Enabled,oneshot) populate-sys
├─(up,Enabled,oneshot) mount-dev
├─(up,Enabled,oneshot) mount-pts
├─(up,Enabled,oneshot) mount-shm
├─(up,Enabled,oneshot) populate-dev
├─(up,Enabled,oneshot) mount-cgroups
├─(up,Enabled,bundle) 00
├─(up,Enabled,bundle) all-Mount
├─(up,Enabled,oneshot) system-hwclock
├─(up,Enabled,oneshot) modules-kernel
├─(up,Enabled,oneshot) system-random
├─(up,Enabled,oneshot) modules-system
├─(up,Enabled,oneshot) system-sysctl
├─(456,Enabled,longrun) udevd
├─(up,Enabled,oneshot) udevadm
├─(up,Enabled,oneshot) system-fontnkey
├─(up,Enabled,oneshot) devices-dmraid
├─(up,Enabled,oneshot) devices-btrfs
├─(up,Enabled,oneshot) devices-crypttab
├─(up,Enabled,oneshot) devices-lvm
├─(up,Enabled,oneshot) devices-zfs
├─(up,Enabled,bundle) system-Devices
├─(up,Enabled,oneshot) system-fsck
├─(up,Enabled,oneshot) mount-fstab
├─(up,Enabled,bundle) all-System
├─(up,Enabled,oneshot) mount-rw
├─(up,Enabled,oneshot) mount-swap
├─(up,Enabled,oneshot) local-iptables
├─(up,Enabled,oneshot) local-ip6tables
├─(up,Enabled,oneshot) local-loop
├─(up,Enabled,oneshot) local-sethostname
├─(up,Enabled,oneshot) local-time
├─(up,Enabled,oneshot) local-authfiles
├─(up,Enabled,oneshot) local-tmpfiles
├─(up,Enabled,oneshot) local-rc
├─(up,Enabled,oneshot) local-dmesg
├─(up,Enabled,bundle) all-Local
├─(up,Enabled,oneshot) all-Runtime
└─(up,Enabled,bundle) All
Name : boot-user
Initialized : yes
Enabled : yes
Starts after : root
Current : no
Allowed : root
Symlinks : svc->source db->source
Contents : /
├─(up,Enabled,oneshot) mount-run-uras
├─(up,Enabled,oneshot) setenv-uras
├─(818,Enabled,longrun) scandir-uras-log
├─(850,Enabled,longrun) scandir-uras
└─(up,Enabled,bundle) All-uras
Name : root
Initialized : yes
Enabled : yes
Starts after : None
Current : yes
Allowed : root
Symlinks : svc->source db->source
Contents : /
├─(727,Enabled,classic) tty@ tty1
├─(730,Enabled,classic) tty@ tty2
├─(733,Enabled,classic) openntpd-log
├─(731,Enabled,classic) openntpd
├─(732,Enabled,classic) wpa_supplicant-log
├─(907,Enabled,classic) wpa_supplicant
├─(766,Enabled,longrun) dbus-log
├─(771,Enabled,longrun) dbus
├─(765,Enabled,longrun) consolekit-log
├─(786,Enabled,longrun) consolekit
├─(763,Enabled,longrun) sddm-log
├─(784,Enabled,longrun) sddm
├─(761,Enabled,longrun) networkmanager-log
└─(785,Enabled,longrun) networkmanager
------------------------------------------------------------------------
Name : boot-user
Initialized : no
Enabled : yes
Starts after : graphics
Current : no
Allowed : uras
Symlinks : svc->source db->source
Contents : /
└─None
Name : graphics
Initialized : yes
Enabled : yes
Starts after : None
Current : yes
Allowed : uras
Symlinks : svc->source db->source
Contents : /
├─(up,Enabled,oneshot) xdg-user-dirs
├─(996,Enabled,longrun) dbus-session@ uras-log
└─(1000,Enabled,longrun) dbus-session@ uras
banned_9-26-2021
Please when including code in the forum use code tags:
[code]
# pacman -Syu obcore/linux-lts
[/code]
eric
your thunar and geany is clearly a permissions issues. I'm surprise to see consolekit running on your root tree but i doesn't see it on your boot log.
you can check if you consolekit session is valid doing
% ck-list-sessions
So, i was "hoping" for a btrfs service crash on your boot log or an fstab issue but apparently both started correctly
@ 400000005ef0c95f1457656c Scanning for Btrfs filesystems
@ 400000005ef0c95f145c9822 [devices-btrfs] started successfully
....
@ 400000005ef0c95f151c7f79 [mount-fstab] starts...
@ 400000005ef0c95f156622f3 [mount-fstab] started successfully
I tried to read the brtfs Arch wiki if i can found something wrong on your configuration, but i didn't saw nothing, but again i'm not accustomed to brtfs stuff. I read some stuff about refind and brtfs issue. Have you try with other bootloader?
The boot process seems to be ok. Your trees seems to be configured correctly too. Maybe a supplementary command need to be used for btrfs at boot time, so i checked what other distro do like Void and i found the same command and nothing more.
I suspect something "wrong" at the boot entry menu but well i don't know exactly.
For the moment i have no time to test a brtfs installed on a VM.
jbkeh
Sorry, but I don't know how to interpret this:
~ % ck-list-sessions
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = 'unspecified'
session-class = 'user'
session-state = 'active'
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2020-06-23T10:54:20.241084Z'
login-session-id = '1'
XDG_RUNTIME_DIR = '/run/user/1000'
VTNr = '7'
In regard to BTRFS, it is simply a filesystem. Granted, it incorporates
some functions which have been 'wrapped' around other filesystems via
mdadm etc, but it is an enclosed entity and should not react differenty
simply because its "pool" consists of more than one device/partition.
I have been using BTRFS for several years, but strictly as a 'standard'
filesystem. In all that time, a 'scrub' would occasionally detect errors
(likely from power being cut before buffers were cleared) and they were
always successfully repaired.
You may readily be correct that I have a 'permissions' problem.
One of the main 'frustrations' I have with EVERY 'distro' is their
'insistence' to 'force' 'help' in setting up partitions and structures
(which can be incredibly wrong).
What I would give for a 'distro' that (outside from the usual
keyboard/locale questions) simply asked, "What partition/path is to be
loaded?" and replied "Done. Your kernel parameters should be .........;
good luck with your bootmanager/loader/fstab".
Why cannot kernel parameters be part of the installation documentation?
I think I am at the point of a complete re-installation (and hours of
updates).
Thanks
eric
Your session seems active. The important field to see this is:
active = TRUE
Why cannot kernel parameters be part of the installation documentation?
It's difficult to cover every case for every one
I think I am at the point of a complete re-installation (and hours of
updates).
Well, i don't know how to help you more here. You know what to do for your partitions scheme and bootloader better than me. No errors from the boot, no errors from your service, no errors for your trees, so....
jbkeh
Well, events precipitated the complete re-install.
In the same vein as reported (
https://forum.obarun.org/viewtopic.php?pid=6024# p6024 )
the introduction of the latest 66 packages, although the 66-updates ( dry run and
actual) produce the request for the root password and reject the value given even
though it is correct.
The re-install (to a SINGLE device BTRFS system) did fix the problem (one step back
and one step forward).
One thing of note - immediately after the install, I ran the dbus steps you
had requested. The install had already done them!
uras@ klin ~ % sudo mount /dev/sda2 /mnt/a2
[sudo] password for uras:
uras@ klin ~ % sudo pacman -S boot-user@ -66mod
[sudo] password for uras:
warning: boot-user@ -66mod-0.2.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) boot-user@ -66mod-0.2.1-1
Total Download Size: 0.01 MiB
Total Installed Size: 0.01 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
boot-user@ -66mod... 6.7 KiB 0.00 B/s 00:00 [# #####################] 100%
(1/1) checking keys in keyring [# #####################] 100%
(1/1) checking package integrity [# #####################] 100%
(1/1) loading package files [# #####################] 100%
(1/1) checking for file conflicts [# #####################] 100%
(1/1) checking available disk space [# #####################] 100%
:: Processing package changes...
(1/1) reinstalling boot-user@ -66mod [# #####################] 100%
uras@ klin ~ % sudo 66-mods.sh boot-user@ uras
66-mods.sh: fatal: /usr/lib/66/service/boot-user@ uras already exist
uras@ klin [111] ~ % sudo 66-tree -nE boot-user
66-tree: fatal: unable to create: /var/lib/66/system/boot-user: already exist
uras@ klin [100] ~ % sudo 66-enable -t boot-user All-uras
66-enable: info: Ignoring: All-uras service: already enabled
uras@ klin ~ % sudo pacman -S sddm sddm-66serv consolekit2 consolekit-66serv dbus dbus-66serv
[sudo] password for uras:
warning: sddm-0.18.1-5 is up to date -- reinstalling
warning: sddm-66serv-0.2.1-1 is up to date -- reinstalling
warning: consolekit2-1.2.1-7 is up to date -- reinstalling
warning: consolekit-66serv-0.2.0-1 is up to date -- reinstalling
warning: dbus-1.12.16-11 is up to date -- reinstalling
warning: dbus-66serv-0.1.6-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (6) consolekit-66serv-0.2.0-1 consolekit2-1.2.1-7 dbus-1.12.16-11
dbus-66serv-0.1.6-1 sddm-0.18.1-5 sddm-66serv-0.2.1-1
Total Download Size: 3.82 MiB
Total Installed Size: 6.34 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
dbus-1.12.16-11-... 275.1 KiB 555 KiB/s 00:00 [# #####################] 100%
sddm-0.18.1-5-x86_64 3.4 MiB 956 KiB/s 00:04 [# #####################] 100%
consolekit2-1.2.... 156.8 KiB 134 KiB/s 00:01 [# #####################] 100%
dbus-66serv-0.1.... 14.9 KiB 0.00 B/s 00:00 [# #####################] 100%
sddm-66serv-0.2.... 3.7 KiB 0.00 B/s 00:00 [# #####################] 100%
consolekit-66ser... 3.3 KiB 0.00 B/s 00:00 [# #####################] 100%
(6/6) checking keys in keyring [# #####################] 100%
(6/6) checking package integrity [# #####################] 100%
(6/6) loading package files [# #####################] 100%
(6/6) checking for file conflicts [# #####################] 100%
(6/6) checking available disk space [# #####################] 100%
:: Processing package changes...
(1/6) reinstalling dbus [# #####################] 100%
(2/6) reinstalling sddm [# #####################] 100%
(3/6) reinstalling dbus-66serv [# #####################] 100%
(4/6) reinstalling sddm-66serv [# #####################] 100%
(5/6) reinstalling consolekit2 [# #####################] 100%
warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 700 package: 750
(6/6) reinstalling consolekit-66serv [# #####################] 100%
:: Running post-transaction hooks...
(1/1) Updating system user/group accounts...
obsysusers: info: add user: bin to group: daemon
obsysusers: info: add user: bin to group: sys
obsysusers: info: add user: daemon to group: adm
obsysusers: info: add user: daemon to group: bin
obsysusers: info: add user: daemon to group: lp
obsysusers: info: add user: cups to group: lp
obsysusers: info: add user: sddm to group: video
uras@ klin [111] ~ % 66-enable dbus-session@ uras
66-enable: info: Ignoring: dbus-session@ uras service: already enabled
Do note the "warning" following the re-installation of consolekit2.
My next step was to repeat the re-installation, this time to a EXT4 partition.
I had hoped that by removing BTRFS, the dbus 'problem' would vanish. It did NOT.
I did note that ALL the error messages have a common element - Error spawning
command line “dbus-launch --autolaunch=b6ce6e4c1e0c54d068295cf75ef4a8d0
--binary-syntax --close-stderr”: Child process exited with code 1
What can I do to help pin this down?
eric
It's really difficult to follow you :/
In the same vein as reported (
https://forum.obarun.org/viewtopic.php?pid=6024# p6024 )
the introduction of the latest 66 packages, although the 66-updates ( dry run and
actual) produce the request for the root password and reject the value given even
though it is correct.
I don't understand how you can get the same error as reported on the
https://forum.obarun.org/viewtopic.php?pid=6024# p6024. This error come when the dbus is updated without updating its configuration file. You said that you did a complete reinstall. In that case the configuration file should correspond to the installed dbus version (first time used, so no mix between e.g. 0.1.5 and 0.1.6 dbus configuration file).
Also, how did you make the installation? manually? through the obarun-install script? Because if you do a fresh installation you don't need to run any 66-update program. You should get directly the last 66 version.
I did note that ALL the error messages have a common element - Error spawning
command line “dbus-launch --autolaunch=b6ce6e4c1e0c54d068295cf75ef4a8d0
--binary-syntax --close-stderr”: Child process exited with code 1
where this error message come from??? dbus service??
jbkeh
Sorry about any confusion. I must try to remember that I am but one
voice clamoring for attention and that the thread is rather dynamic.
The installation on an EXT4 filesystem was a 'one-off' simply to establish
that BTRFS had no part in the dbus 'errors'. It was then removed.
The current installation was 'forced' when the most recent 66 updates
were applied to the then running system and rendered it unbootable.
Yes, when the 66 updates were applied to that previous system, I did run
66-update (dry and actual, root and user) before the ill-fated reboot.
Everything was deemed 'successful'.
I mentioned the other thread only as to the 'appearance' of the type of
boot error - the root password is requested for "maintenance", but is
rejected.
The current system was indeed installed 'by the script'
(bootloader=EFI-stub, no GRUB). As mentioned in my previous post I ran
though the 'dbus' steps (
https://wiki.obarun.org/doku.php?id=1.php )
as both you and the documentation had suggested.
I was somewhat surprised that this had already been done in the
installation and wonder why there is the 'permissions' discrepancy.
At least I can now run my daily "sudo pacman -Syu" and reboot after.
So, we are back to the original situation:
1. At least two programs, 'thunar' and 'geany' throw myriad errors if
invoked under 'sudo', yet still "appear" to function correctly.
2. If the BTRFS filesystem has two device/partitions, the boot
fails trying the find the second device (the stated uuid is garbage).
Note this is strictly a BOOT problem - the BTRFS filesytem is fully
functional regardless of its number of devices/partitions.
I will again post examples of the 'sudo invoked' errors:
uras@ klin ~ % sudo thunar
[sudo] password for uras:
thunar: Failed to initialize Xfconf: Error spawning command line ?dbus-launch --autolaunch=b6ce6e4c1e0c54d068295cf75ef4a8d0 --binary-syntax --close-stderr?: Child process exited with code 1
(thunar:4331): thunar-WARNING **: 12:13:31.127: Name 'org.xfce.FileManager' lost on the message dbus.
(thunar:4331): thunar-WARNING **: 12:13:31.127: Name 'org.freedesktop.FileManager1' lost on the message dbus.
ThunarThumbnailer: failed to create proxy: Error spawning command line “dbus-launch --autolaunch=b6ce6e4c1e0c54d068295cf75ef4a8d0 --binary-syntax --close-stderr”: Child process exited with code 1
uras@ klin ~ % sudo geany
[sudo] password for uras:
(geany:4406): dconf-WARNING **: 12:22:58.846: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=b6ce6e4c1e0c54d068295cf75ef4a8d0 --binary-syntax --close-stderr”: Child process exited with code 1
(geany:4406): dconf-WARNING **: 12:22:58.864: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=b6ce6e4c1e0c54d068295cf75ef4a8d0 --binary-syntax --close-stderr”: Child process exited with code 1
......repeats again and again......
(geany:4406): dconf-WARNING **: 12:23:02.283: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=b6ce6e4c1e0c54d068295cf75ef4a8d0 --binary-syntax --close-stderr”: Child process exited with code 1
Please note the commonality: "Error spawning command line “dbus-launch --autolaunch=b6ce6e4c1e0c54d068295cf75ef4a8d0 --binary-syntax --close-stderr”: Child process exited with code 1"
Thank you for your forbearance...
banned_9-26-2021
jbkeh wrote
I think I am at the point of a complete re-installation (and hours of
updates).
This is easy. Make a small partition to fit your cached pkgs, (/var/cache/pacman/pkg) contents, move them all there, then mount the partition as /var/cache/pacman/pkg
When you do a reinstallation mount the same partition into that directory and everything that has ever been downloaded will not download again. So it should take 3minutes to do the next installation if you are using the same.
One shot in the wild, maybe unrelated, what does your /var/log/66 look like? All contents of all subdirectories should be owned by s6log:log not root:root, are they?
jbkeh
friedmushroom wrote
So it should take 3minutes to do the next installation if you are using the same.
One shot in the wild, maybe unrelated, what does your /var/log/66 look like? All contents of all subdirectories should be owned by s6log:log not root:root, are they?
Nice. Thanks.
root:root ownership goes down to /var/log/66 - below that, it's all s6log:log