Wat-now Yes, I have consolekit running. Sharing my output for comparison:
$ sudo 66 status boot-user@ros1
Name : boot-user@ros1
Version : 0.8.0
In tree : session
Status : enabled, up
Type : module
Description : Configure a nested supervision tree for ros1 user
Part of : None
Notify : 0
Max death : 5
Earlier : 0
Source : /usr/share/66/service/boot-user/boot-user@
Live : /run/66/scandir/0/boot-user@ros1
Dependencies : scandir@ros1 scandir@ros1:setenv@ros1 scandir@ros1:svscan@ros1-log consolekit-log dbus-log
ly-log scandir@ros1:svscan@ros1 dbus consolekit ly
Required by : None
Contents : boot-user@ros1:mount-run@ros1
Optional dependencies : None
Start script :
None
Stop script :
None
Environment source : /etc/66/conf/boot-user@ros1/0.8.0
Environment file : environment variables from: /etc/66/conf/boot-user@ros1/0.8.0/.boot-user@ros1
## Uncomment it to use a display manager.
## Can be any display manager as long as the
## corresponding frontend file exist on your system
## e.g sddm,lightdm,...
## It also prepare the .xsession file.
#DISPLAY_MANAGER=sddm
## Uncomment it to use a console tracker.
## Can be any console tracker as long as the
## corresponding frontend file exist on your system
## e.g consolekit,seatd,turnstile,...
#CONSOLE_TRACKER=consolekit
## Create and mount the XDG_RUNTIME directory
## at /run/user/ros1 [yes|no]
XDG_RUNTIME=!yes
## Command to use in your .xinitrc
## to launch your desktop e.g.: openbox-session.
## If commented the .xinitrc file is not configured.
DESKTOP_CMDLINE=!jwm
environment variables from: /etc/66/conf/boot-user@ros1/0.8.0/boot-user@ros1
## Uncomment it to use a display manager.
## Can be any display manager as long as the
## corresponding frontend file exist on your system
## e.g sddm,lightdm,...
## It also prepare the .xsession file.
DISPLAY_MANAGER=ly
## Uncomment it to use a console tracker.
## Can be any console tracker as long as the
## corresponding frontend file exist on your system
## e.g consolekit,seatd,turnstile,...
CONSOLE_TRACKER=consolekit
## Create and mount the XDG_RUNTIME directory
## at /run/user/ros1 [yes|no]
XDG_RUNTIME=!yes
## Command to use in your .xinitrc
## to launch your desktop e.g.: openbox-session.
## If commented the .xinitrc file is not configured.
DESKTOP_CMDLINE=!startplasma-x11
Environment ImportFile : None
StdIn : None
StdOut : None
StdErr : None
Logger name : None
Logger file : None
Also the session tree status last part:
In tree: session
\
├─scandir@ros1:setenv@ros1 (pid=up, state=Enabled, type=oneshot, tree=session)
├─scandir@ros1:svscan@ros1-log (pid=1295, state=Enabled, type=classic, tree=session)
├─scandir@ros1 (pid=up, state=Enabled, type=module, tree=session)
├─boot-user@ros1:mount-run@ros1 (pid=up, state=Enabled, type=oneshot, tree=session)
├─consolekit-log (pid=1292, state=Enabled, type=classic, tree=session)
├─ly-log (pid=1294, state=Enabled, type=classic, tree=session)
├─scandir@ros1:svscan@ros1 (pid=1344, state=Enabled, type=classic, tree=session)
├─consolekit (pid=1303, state=Enabled, type=classic, tree=session)
├─ly (pid=1299, state=Enabled, type=classic, tree=session)
└─boot-user@ros1 (pid=up, state=Enabled, type=module, tree=session)
I have been shifting ly and consolekit back and forth between global and session trees, just in case. Also tried not using boot-user module and employ the ttys 3 and 7 to enable ly; Every time, I have got the file not found error.
By the way, I have been reviewing ly config files and found this comment on /etc/ly/config.ini:
# Session log file path
# This will contain stdout and stderr of Wayland sessions
# By default it's saved in the user's home directory
# Important: due to technical limitations, X11 and shell sessions aren't supported, which
# means you won't get any logs from those sessions.
# If null, no session log will be created
session_log = ly-session.log
Since we are trying to record logs for kwin on X11 sessions, I do not understand the reason behind using ly DM to do so, as X11 sessions are not supported. Can you please explain the logic behind the use of ly in our case?
