Issue, update not working

Support
1

kick secure I ran system check. It printed out a page of lines. within that it has a box with root - locked - disabled
user - Absent - enabled
sysmaint - Absent - enabled

then further down it says warning system check can not check for system update

That output means you currently have these accounts/tokens in this state:

  • root: locked/disabled

  • sysmaint: Absent/enabled (not actually present, but the “enabled” flag is showing as enabled—so it’s likelya config state mismatch or just how the checker reports it)

  • user: Absent/enabled (same note)

And the checker can’t verify OS/package updates (“cannot check for system update”).

To get you unstuck, do these quick checks:

  1. Confirm what accounts exist right now

    • Run: getent passwd | egrep '^(root|user|sysmaint):'

    • Run: `getent shadow | egrep ‘^(root|user|sysmaint):’

  2. Check whether “user” is actually missing

    • Run: id user

    • Run: id sysmaint

  3. Look for update-check failure cause

    • If this is Linux: run cat /etc/os-release and check if your system has working repos/clock:

      • date

      • ls /etc/apt/sources.list.d 2>/dev/null || true

      • For Debian/Ubuntu: apt update (or apt-get update)

      • For RHEL/CentOS/Fedora: dnf check-update or yum check-update

If you paste (1) the OS distro (output of /etc/os-release) and (2) the exact command you ran for “system check” plus the first ~30 lines of its output (redact hostnames if needed), I can tell you whether the “Absent/enabled” lines are benign reporting or indicate a broken account/state—and what exact fix to apply.

2

Each message has a link to documentation. Please read it.

3

The software update issue is known, one of the repos we enable by default is currently broken. See:

1 Like
4

TY I found that out the hard way :rofl:. I tried everything and then ended up with a fresh install with it just to come up again. So sorry about bringing that up if someone else did.

Ty @arraybolt3 for your insight, all your insights. Im just trying to get a full understanding of this

1 Like
5

Think it’s a little more of an issue, not caused by the kick secure team.

I have uninstalled this OS a total of 3 times and nothing but nightmares have came. I believe it has to do with Tor. Why am I saying that? because Tor is how this OS works threw. After I reloaded the OS it wouldn’t allow me to install the tor browser and it would keep giving me error 100 when I would try to update. I tried installing brave browser though, and that worked. Yes, Tor was working the first time I installed it

Im very interested in this project still, people like @arraybolt3 have made the time I have invested into it worth it with help.

6

The issue linked above is persistent, it’s not something a reinstall will fix. There are instructions for how to disable the broken repo or work around the repo being broken here:

Eventually the Debian Fast Track maintainers will (likely) fix the issue with their repo and the problem will be automatically resolved at that time.

2 Likes
7

@arraybolt3 Could I give you some xmr?

1 Like
8

Haha, no thanks. I work with Kicksecure under contract. If you want to though, you can always donate to Kicksecure:

(Even if I was an unpaid volunteer, I wouldn’t accept tips, since I don’t want to see the forums become a marketplace of sorts and would rather see donations go to the project.)

1 Like