Systemcheck returns the following message lately:
WARNING: System ready check (system) Result: Failed.
Debugging information:
Command:
‘sudo systemctl --wait is-system-running’ (same as ‘leaprun system-ready-check’)
result: ‘degraded’
WARNING: systemd ‘system’ units check result: One or more units failed to load.
A possible system issue was detected. There is no need to panic. This is not a serious security problem. However, it may impact other system checks.
Some systemd ‘system’ units may be stuck in a failed, activating, or deactivating state.
Output of ‘leaprun read-systemctl-logs-failed-units-pretty’:
(equivalent to: sudo systemctl --state=failed,activating,deactivating list-units)
########################################
UNIT LOAD ACTIVE SUB DESCRIPTION
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.
1 loaded units listed.
########################################
To check manually:
Open a terminal. (Start Menu → System → Terminal)
Run:
leaprun read-systemctl-logs-failed-units-pretty
If you know what you are doing, feel free to disable this check. Create a file /etc/systemcheck.d/50_user.conf and add:
systemcheck_skip_functions+=" check_services_do "
We’ll need to see why the AppArmor service is failing to know how to help. Please boot into PERSISTENT Mode | SYSMAINT Session, then click “Open Terminal” and run:
sudo journalctl -u apparmor.service
Press Shift+G to move to the bottom of the logs, then share the output here. (You can upload a screenshot of the logs to a file hosting service of your choice and share it here if that’s easiest.)
Pretty sure that’s the issue, as that line in that file is not present on my system, whereas the one in abstractions/tor is present. Did you install anything Tor- or Lyrebird-related recently?
You can probably fix the issue for now by doing the following:
Run sudo nano /etc/apparmor.d/local/system_tor.anondist
Move your cursor to the /usr/bin/lyrebird rix, line
Comment the line out by typing a single # before the rest of the line, so that it reads #/usr/bin/lyrebird rix,
Thank you, that fixed it. I installed lyrebird several months ago following this guide
which advises adding /usr/bin/lyrebird rix.
But this bug popped out for the first time about a week ago. I hope, commenting this out shouldn’t impair anything crucial?
It should be fine if lyrebird continues to work. rix basically says “Tor can launch lyrebird, but lyrebird will be confined with the same AppArmor profile Tor is.” “Pix” basically says “Tor can launch Lyrebird, and if there is a separate profile for lyrebird, it will be used. Otherwise, it will be confined with the same AppArmor profile Tor is.” So it’s potentially a bit more secure.