Closed leviska closed 1 month ago
systemctl list-units --type target --state active
UNIT LOAD ACTIVE SUB DESCRIPTION
basic.target loaded active active Basic System
bluetooth.target loaded active active Bluetooth Support
cryptsetup.target loaded active active Local Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
integritysetup.target loaded active active Local Integrity Protected Volumes
local-fs-pre.target loaded active active Preparation for Local File Systems
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User System
network-online.target loaded active active Network is Online
network.target loaded active active Network
nss-lookup.target loaded active active Host and Network Name Lookups
nss-user-lookup.target loaded active active User and Group Name Lookups
paths.target loaded active active Path Units
remote-fs.target loaded active active Remote File Systems
slices.target loaded active active Slice Units
sockets.target loaded active active Socket Units
sound.target loaded active active Sound Card
swap.target loaded active active Swaps
sysinit.target loaded active active System Initialization
time-set.target loaded active active System Time Set
timers.target loaded active active Timer Units
tpm2.target loaded active active Trusted Platform Module
veritysetup.target loaded active active Local Verity Protected Volumes
Legend: LOAD → Reflects whether the unit definition was properly loaded.
ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
SUB → The low-level unit activation state, values depend on unit type.
24 loaded units listed.
systemctl is-active graphical-session.target
inactive
hmmm
Ah that's was system targets Here's users
systemctl list-units --type target --all --user
UNIT LOAD ACTIVE SUB DESCRIPTION
basic.target loaded active active Basic System
● blockdev@dev-nvme0n1p1.target not-found inactive dead blockdev@dev-nvme0n1p1.target
bluetooth.target loaded inactive dead Bluetooth
default.target loaded active active Main User Target
graphical-session.target loaded inactive dead Current graphical user session
paths.target loaded active active Paths
shutdown.target loaded inactive dead Shutdown
sockets.target loaded active active Sockets
sound.target loaded inactive dead Sound Card
timers.target loaded active active Timers
Legend: LOAD → Reflects whether the unit definition was properly loaded.
ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
SUB → The low-level unit activation state, values depend on unit type.
10 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
It seems that the problem is more with "why my desktop environment (cinnamon) doesn't start the graphical-session.target" and not with ringboard exactly
Changing graphical-session.target
to default.target
(as advised by someone on the internet) seems to work!
My config now seems fixed, you can close the issue if you don't want to dive into it
Well that's weird. I'm not sure there's anything I can do to improve this as the graphical session target is supposed to be started with your DE.
Thanks for figuring out the bug!
After boot the servers don't start While writing this I think I found the issue:
Adding
to the
ringboard-server.service
seems to fix enabling, butI didn't test the boot yetafter boot it still doesn't startAll other info:
The services:
There is no logs from this boot (and old logs looks good), meaning that the service just didn't start(?) Starting the services manually works great System: Arch Linux