I’ll need to double check my notes, but the Syscheck notification popup error reports “FDE absent” when booting into Live Mode. My guess is that Live Mode running as a regular USER lacks the necessary privileges to perform the check. I selected FDE and selected LUKS at install. LUKS passphrase is still needed before I get anywhere, so it works. Luks was unlocked long before and I selected FDE in the installer and my files are decrypted so LUKS is present I would think?
Additionally, the Syscheck error notification can be quite annoying when operating in Live Mode as a USER. To get it to go away you have to mask it first in non Live Mode.
I don’t mind it normally poping up for USER in normal mode but for Live Mode I could do without it tbh.
Would it even be possible to disable or mask the service for user in live mode (Not sysmaint), and would it make sense? Avoiding seeing after a new install after booting into user in live mode, while still showing it in normal session for user (they would still have the option to do systemctl --user mask updatecheck.service)
If we apply this would it also prevent the “Live Check Indicator” systray icon (the yellow circle) from appearing or is that unrelated to this?
Is your system fully up-to-date? We fixed this bug some time back, and the fix is in Kicksecure 18’s stable repository, so a normal software update should resolve the issue. (We haven’t published new Kicksecure images with the fix already present yet.)
That’s not a bad idea, and would likely be easy to implement. @Patrick thoughts?
That’s an unrelated tool called “livecheck”. That will still appear as it should even if systemcheck is suppressed in live mode.
What’s the suggestion? No longer autostart systemcheck and/or updatecheck in live mode?
I think the should keep autostarting systemcheck in live mode. Technically it’s not autostarted directly yet. systemcheck gets started conditionally by setup-wizard-dist.
Maybe one day we’d want to (re-)introduce a systemcheck.service systemd unit.
I am not saying we necessarily need to insist on showing a popup. systemcheck could be tailored to be non-intrusive, more suitable in live mode.
Some checks such as Journal Inspection and Diagnostics Logs pointing out “Bad RAM detected” or “self-detected stall on CPU”, which are severe and likely to cause follow-up issues should be reported if found.
In live mode: useful for testing updates. Also otherwise users using live mode a lot or even primarily won’t notice updates being available.
In ISO live mode: to be notified how old an ISO is. Perhaps a newer ISO is available or perhaps the user would even consider to build an updated ISO using derivative-maker.
Now you got me confused as to what I was asking lol I guess maybe not show errors for things that user cant run due to user-sysmaint-split “sudo commands”. Will have to dig into the meat and potatos of what it all does in the wiki/code.
Yeah I think that’s what I was getting at. This thread shouldn’t be high priority just my personal thoughts up installation and use. Like I see smartmontools is bundeled in Kicksecure, not sure which thing its for and if that plays role any checks like you mentioned. Really nice to have it included but it fails for USER on persistent mode despite getting it set for my Sandisk Cruiser (sudo smartctl -d scsi -s on /dev/sda). Failing drives such a pain if you have had them, which I have btw (unrelated to kicksecure). Nice to have it setup if I can with sendmail to send email notifying you your drive is gonna fail. Might be good for documentation on setting that up. Useful for server users despite them having RAID setup, or just a desktop user.