Wat-now seems there still cannot be two boot-user@ active at the same time in my system, even in different trees, is this expected behavior
nope, and i can't reproduce the issue
Name : session
Current : yes
Enabled : yes
Allowed : root
Groups : admin
Depends : \
└─global (Enabled)
Required by : \
└─None
Contents : \
├─scandir@obarun:setenv@obarun (pid=up, state=Enabled, type=oneshot, tree=session)
├─scandir@obarun:svscan@obarun-log (pid=3988, state=Enabled, type=classic, tree=session)
├─scandir@obarun (pid=up, state=Enabled, type=module, tree=session)
├─boot-user@obarun:mount-run@obarun (pid=up, state=Enabled, type=oneshot, tree=session)
├─dbus-log (pid=3993, state=Enabled, type=classic, tree=global)
├─consolekit-log (pid=3991, state=Enabled, type=classic, tree=global)
├─seatd-log (pid=3990, state=Enabled, type=classic, tree=session)
├─postgresql-log (pid=0, state=Disabled, type=classic, tree=session)
├─postgresql-prepare (pid=unitialized, state=Disabled, type=oneshot, tree=global)
├─scandir@test:setenv@test (pid=unitialized, state=Enabled, type=oneshot, tree=session)
├─scandir@test:svscan@test-log (pid=0, state=Enabled, type=classic, tree=session)
├─scandir@test (pid=unitialized, state=Enabled, type=module, tree=session)
├─boot-user@test:mount-run@test (pid=unitialized, state=Enabled, type=oneshot, tree=session)
├─scandir@obarun:svscan@obarun (pid=4015, state=Enabled, type=classic, tree=session)
├─dbus (pid=3996, state=Enabled, type=classic, tree=global)
├─postgresql (pid=0, state=Disabled, type=classic, tree=session)
├─scandir@test:svscan@test (pid=0, state=Enabled, type=classic, tree=session)
├─consolekit (pid=4022, state=Enabled, type=classic, tree=global)
├─seatd (pid=4023, state=Enabled, type=classic, tree=session)
├─boot-user@obarun (pid=up, state=Enabled, type=module, tree=session)
└─boot-user@test (pid=unitialized, state=Enabled, type=module, tree=session)
Wat-now Also one needs to run command two times to remove extra boot-user@ after starting
That's not normal, it should remove all the components of the module at first invocation, it should be
# 66 remove boot-user@test
remove: info: removed successfully: boot-user@test
remove: info: removed successfully: boot-user@test:mount-run@test
Can you please provide the output of 66 -v5 start scandir@obgreet
? This will give us more information about your crash scandir@obgreet:setenv@obgreet -- exited with signal: 111