What's going on?

I used Linux Mint: Debian Edition with Kicksecure CLI installed. Every time I boot up, it says systemd-modules-load.service failed to load 3 times before booting. I searched up here and I enabled Secure Boot, enrolled the MOKs and DKMS or whatever, rebuilt all the packages and it all seemed to work swimmingly but it still says that.

When I run updatecheck it tells me to run systemcheck, and when I run systemcheck this is what appears:

[WARNING] [systemcheck] System ready check (system) Result: Failed.

Debugging information:
Command:
‘sudo systemctl --wait is-system-running’
(same as ‘leaprun system-ready-check’)
result: ‘degraded’
[WARNING] [systemcheck] 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

systemd-modules-load.service loaded failed failed Load Kernel Modules

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 "
[INFO] [systemcheck] Connected to Tor.
[WARNING] [systemcheck] Kicksecure Meta Packages Test Result: No meta package is installed.
Did you accidentally uninstall it?

Make sure any of the following meta packages is installed.

kicksecure-vm-gui-lxqt kicksecure-vm-server kicksecure-baremetal-gui-lxqt kicksecure-baremetal-server

See also: 


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_meta_packages "
[INFO] [systemcheck] Kicksecure is a research project.
[INFO] [systemcheck] Operating system (OS) (Debian) support status: Unsupported (as of 2018-05-31)
Your system is likely vulnerable to malware infection due to missing security updates.
Upgrade to a newer version of Kicksecure as soon as possible. You should limit continued online use of this machine until it is upgraded.
See also: 

[INFO] [systemcheck] user-sysmaint-split-check installation check result: Absent[LINK]
[INFO] [systemcheck] user-sysmaint-split session detection result: USER Session.
[INFO] [systemcheck] Full Disk Encryption (FDE): Absent
See also: 

[INFO] [systemcheck] GRUB bootloader password: Absent
See also: 

[INFO] [systemcheck] Kicksecure Login Security Check (Colors)
:
±------±-------------------------------------+
| Users | Password               GUI Autologin |
±------±-------------------------------------+
| root  | Locked (Absent)        Disabled      |
| user  | Present                Enabled       |
±------±-------------------------------------+

You can adjust these settings using “Manage Passwords” and “Manage GUI Autologin”
in the System Maintenance Panel.
See also:
[LINK]
[LINK]
[INFO] [systemcheck] Secure Boot: Enabled
See also: 

[INFO] [systemcheck] tirdad - TCP ISN CPU Information Leak Protection: Enabled
For details, see: 

[INFO] [systemcheck] Kicksecure APT Repository: Enabled.
When the Kicksecure team releases GIGI updates,
they will be AUTOMATICALLY installed (when you run apt-get dist-upgrade)
along with updated packages from the Debian team. Please read 
 to understand the risk.
If you want to change this, use:
sudo repository-dist
[INFO] [systemcheck] Debian Package Update Check: Checking for software updates via apt-get
 ( Documentation: [LINK])
E: The repository ‘tor+https://deb.kicksecure.com gigi Release’ does not have a Release file.
[WARNING] [systemcheck] Debian Package Update Check Result: Could not check for software updates! (apt-get code: 100)
Please manually check:
(Open a terminal, Start Menu → System → Terminal.)
upgrade-nonroot

I’m confused what’s even going on, what do I do?

What’s the output of systemctl status systemd-modules-load? And what about sudo journalctl -u systemd-modules-load? Note that you may have to reboot into a SYSMAINT session for the latter. While you’re there, try sudo systemctl status systemd-modules-load too since it sometimes prints more logs as root / adm group.

I don’t know much about the meta packages warning though.

There’s quite a bit that looks weird here:

  • systemd-modules-load.service failing is bad, the log output @eternity asked for will help.
  • The meta package test failing is a bug, I’ll make a fix for that.
  • The OS showing up as EOL is probably an LMDE bug.
  • “gigi” is not a release of Debian, but a release of LMDE. The corresponding Debian release is “trixie”. You should replace all instances of “gigi” with “trixie” in apt source lines referring to deb.kicksecure.com. (Keep “gigi” in lines referring to LMDE’s repositories though.)
1 Like

The first command output this:

× systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; stat>
Active: failed (Result: exit-code) since Sun 2026-04-26 09:02:30 BST; 31mi>
Invocation: 669dbdbee5194a688f9e4139fe943f74
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 1965 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited,>
Main PID: 1965 (code=exited, status=1/FAILURE)
Mem peak: 2M
CPU: 17ms

Apr 26 09:02:28 debian systemd[1]: Starting systemd-modules-load.service - Load>
Apr 26 09:02:30 debian systemd-modules-load[1965]: Module ‘jitterentropy_rng’ i>
Apr 26 09:02:30 debian systemd-modules-load[1994]: /usr/bin/disabled-filesys-by>
Apr 26 09:02:30 debian systemd-modules-load[1965]: Error running install comman>
Apr 26 09:02:30 debian systemd-modules-load[1965]: Failed to insert module 'ecr>
Apr 26 09:02:30 debian systemd[1]: systemd-modules-load.service: Main process e>
Apr 26 09:02:30 debian systemd[1]: systemd-modules-load.service: Failed with re>
Apr 26 09:02:30 debian systemd[1]: Failed to start systemd-modules-load.service>
lines 1-19/19 (END)

The second command printed out too many lines of text for me to copy and paste to you, but I will paste one chunk:
Apr 25 01:18:10 debian systemd-modules-load[273]: Module ‘jitterentropy_rng’ is>
Apr 25 01:18:11 debian systemd-modules-load[273]: Inserted module ‘tirdad’
Apr 25 01:18:11 debian systemd-modules-load[273]: Inserted module ‘lp’
Apr 25 01:18:11 debian systemd-modules-load[379]: sh: 1: /usr/bin/disabled-file>
Apr 25 01:18:11 debian systemd-modules-load[273]: Inserted module ‘ppdev’
Apr 25 01:18:11 debian systemd-modules-load[273]: Inserted module ‘parport_pc’
Apr 25 01:18:11 debian systemd-modules-load[273]: Error running install command>
Apr 25 01:18:11 debian systemd-modules-load[273]: Failed to insert module 'ecry>
Apr 25 01:18:11 debian systemd-modules-load[273]: Inserted module ‘msr’
Apr 25 01:18:11 debian systemd[1]: systemd-modules-load.service: Main process e>
Apr 25 01:18:11 debian systemd[1]: systemd-modules-load.service: Failed with re>
Apr 25 01:18:11 debian systemd[1]: Failed to start systemd-modules-load.service>
Apr 25 01:18:24 debian systemd-modules-load[1117]: /usr/bin/disabled-filesys-by>
Apr 25 01:18:25 debian systemd[1]: Starting systemd-modules-load.service - Load>
Apr 25 01:18:25 debian systemd-modules-load[1301]: Module ‘jitterentropy_rng’ i>
Apr 25 01:18:25 debian systemd-modules-load[1306]: /usr/bin/disabled-filesys-by>
Apr 25 01:18:25 debian systemd-modules-load[1301]: Error running install comman>
Apr 25 01:18:25 debian systemd-modules-load[1301]: Failed to insert module 'ecr>
Apr 25 01:18:25 debian systemd[1]: systemd-modules-load.service: Main process e>
Apr 25 01:18:25 debian systemd[1]: systemd-modules-load.service: Failed with re>
Apr 25 01:18:25 debian systemd[1]: Failed to start systemd-modules-load.service>
Apr 25 01:18:27 debian systemd[1]: Starting systemd-modules-load.service - Load>
Apr 25 01:18:27 debian systemd-modules-load[1716]: Module ‘jitterentropy_rng’ i>
Apr 25 01:18:27 debian systemd-modules-load[1735]: /usr/bin/disabled-filesys-by>
Apr 25 01:18:27 debian systemd-modules-load[1716]: Error running install comman>
Apr 25 01:18:27 debian systemd-modules-load[1716]: Failed to insert module 'ecr>
Apr 25 01:18:27 debian systemd[1]: systemd-modules-load.service: Main process e>
Apr 25 01:18:27 debian systemd[1]: systemd-modules-load.service: Failed with re>
Apr 25 01:18:27 debian systemd[1]: Failed to start systemd-modules-load.service>
– Boot c61ca587ff5648508f5faabb6ba954de –
Apr 25 01:22:27 debian systemd-modules-load[275]: Module ‘jitterentropy_rng’ is>
Apr 25 01:22:27 debian systemd-modules-load[275]: Inserted module ‘tirdad’
Apr 25 01:22:27 debian systemd-modules-load[275]: Inserted module ‘lp’
Apr 25 01:22:27 debian systemd-modules-load[375]: sh: 1: /usr/bin/disabled-file>
Apr 25 01:22:27 debian systemd-modules-load[275]: Inserted module ‘ppdev’
Apr 25 01:22:27 debian systemd-modules-load[275]: Inserted module ‘parport_pc’
Apr 25 01:22:27 debian systemd-modules-load[275]: Error running install command>
Apr 25 01:22:27 debian systemd-modules-load[275]: Failed to insert module 'ecry>
Apr 25 01:22:27 debian systemd-modules-load[275]: Inserted module ‘msr’
Apr 25 01:22:27 debian systemd[1]: systemd-modules-load.service: Main process e>
Apr 25 01:22:27 debian systemd[1]: systemd-modules-load.service: Failed with re>
Apr 25 01:22:27 debian systemd[1]: Failed to start systemd-modules-load.service>
Apr 25 01:22:48 debian systemd-modules-load[1330]: /usr/bin/disabled-filesys-by>
Apr 25 01:22:49 debian systemd[1]: Starting systemd-modules-load.service - Load>
Apr 25 01:22:49 debian systemd-modules-load[1501]: Module ‘jitterentropy_rng’ i>
Apr 25 01:22:49 debian systemd-modules-load[1509]: /usr/bin/disabled-filesys-by>
Apr 25 01:22:49 debian systemd-modules-load[1501]: Error running install comman>
Apr 25 01:22:49 debian systemd-modules-load[1501]: Failed to insert module 'ecr>
Apr 25 01:22:49 debian systemd[1]: systemd-modules-load.service: Main process e>
Apr 25 01:22:49 debian systemd[1]: systemd-modules-load.service: Failed with re>
Apr 25 01:22:49 debian systemd[1]: Failed to start systemd-modules-load.service>
Apr 25 01:22:50 debian systemd[1]: Starting systemd-modules-load.service - Load>
Apr 25 01:22:51 debian systemd-modules-load[1912]: Module ‘jitterentropy_rng’ i>
Apr 25 01:22:51 debian systemd-modules-load[1947]: /usr/bin/disabled-filesys-by>
Apr 25 01:22:51 debian systemd-modules-load[1912]: Error running install comman>
Apr 25 01:22:51 debian systemd-modules-load[1912]: Failed to insert module 'ecr>
Apr 25 01:22:51 debian systemd[1]: systemd-modules-load.service: Main process e>
Apr 25 01:22:51 debian systemd[1]: systemd-modules-load.service: Failed with re>
Apr 25 01:22:51 debian systemd[1]: Failed to start systemd-modules-load.service>

How would I do that last part?

The output got cut off here because of journalctl’s pager feature. Can you run sudo journalctl | grep 'Failed to insert module' and paste the output of that?

Look at /etc/apt/sources.list and all files under /etc/apt/sources.list.d. If you see a line that looks similar to deb tor+https://deb.kicksecure.com gigi main, or a section that looks similar to:

Types: deb
URIs: tor+https://deb.kicksecure.com
Suites: gigi
Components: main

Change “gigi” to “trixie”. (I’m guessing our distribution morphing tooling is not able to handle the codenames of some Debian derivatives.)

1 Like

Apr 25 01:18:11 debian systemd-modules-load[273]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 01:18:24 debian systemd-modules-load[1106]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 01:18:25 debian systemd-modules-load[1301]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 01:18:27 debian systemd-modules-load[1716]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 01:22:27 debian systemd-modules-load[275]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 01:22:48 debian systemd-modules-load[1320]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 01:22:49 debian systemd-modules-load[1501]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 01:22:51 debian systemd-modules-load[1912]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 02:21:29 debian systemd-modules-load[274]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 02:21:53 debian systemd-modules-load[1345]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 02:21:54 debian systemd-modules-load[1541]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 02:21:56 debian systemd-modules-load[1775]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 08:23:04 debian systemd-modules-load[276]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 08:23:18 debian systemd-modules-load[1135]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 08:23:19 debian systemd-modules-load[1366]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 08:23:21 debian systemd-modules-load[1719]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 08:29:41 debian systemd-modules-load[271]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 08:30:10 debian systemd-modules-load[1527]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 08:30:11 debian systemd-modules-load[1711]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 08:30:13 debian systemd-modules-load[2116]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:00:13 debian systemd-modules-load[277]: Failed to insert module ‘tirdad’: Key was rejected by service
Apr 25 10:00:13 debian systemd-modules-load[277]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:00:23 debian systemd-modules-load[1042]: Failed to insert module ‘tirdad’: Key was rejected by service
Apr 25 10:00:23 debian systemd-modules-load[1042]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:00:24 debian systemd-modules-load[1241]: Failed to insert module ‘tirdad’: Key was rejected by service
Apr 25 10:00:24 debian systemd-modules-load[1241]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:05:42 debian systemd-modules-load[277]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:05:52 debian systemd-modules-load[1026]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:05:52 debian systemd-modules-load[1214]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:05:55 debian systemd-modules-load[1614]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:09:38 debian systemd-modules-load[275]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:09:48 debian systemd-modules-load[1038]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:09:49 debian systemd-modules-load[1221]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 10:09:51 debian systemd-modules-load[1635]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 17:32:38 debian systemd-modules-load[275]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 17:32:53 debian systemd-modules-load[1148]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 17:32:54 debian systemd-modules-load[1396]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 20:51:19 debian systemd-modules-load[277]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 20:51:38 debian systemd-modules-load[1276]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 20:51:39 debian systemd-modules-load[1469]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 21:07:52 debian systemd-modules-load[278]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 21:08:23 debian systemd-modules-load[1745]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 21:08:24 debian systemd-modules-load[1941]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 23:11:20 debian systemd-modules-load[277]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 23:11:39 debian systemd-modules-load[1441]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 23:11:40 debian systemd-modules-load[1636]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 25 23:11:42 debian systemd-modules-load[2035]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 08:02:38 debian systemd-modules-load[276]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 08:02:58 debian systemd-modules-load[1264]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 08:02:59 debian systemd-modules-load[1463]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 08:03:01 debian systemd-modules-load[1918]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 09:02:04 debian systemd-modules-load[277]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 09:02:26 debian systemd-modules-load[1316]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 09:02:27 debian systemd-modules-load[1500]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 09:02:30 debian systemd-modules-load[1965]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 11:51:21 debian systemd-modules-load[274]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 11:51:42 debian systemd-modules-load[1257]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 11:51:43 debian systemd-modules-load[1448]: Failed to insert module ‘ecryptfs’: Invalid argument
Apr 26 11:51:45 debian systemd-modules-load[1908]: Failed to insert module ‘ecryptfs’: Invalid argument

Only /etc/apt/sources.list.d/derivative.sources had gigi. /etc/apt/sources.list had no text at all.

[INFO] [systemcheck] Kicksecure APT Repository: Enabled.
When the Kicksecure team releases TRIXIE updates,
they will be AUTOMATICALLY installed (when you run apt-get dist-upgrade)
along with updated packages from the Debian team. Please read https://www.kicksecure.com/wiki/Trust to understand the risk.

OK, so you currently have two problems. One is that Secure Boot is now on, so tirdad can’t load. You didn’t have Secure Boot on to begin with, so probably start by turning that off. (Alternatively, try to run through MOK setup again if you want Secure Boot on.)

The other problem is that “ecryptfs” is failing to load for
 some reason. Do you see any relevant error messages in sudo dmesg | grep ecrypt?

1 Like

I turned Secure Boot off:
[ 32.835286] audit: type=1110 audit(1777247280.501:299): pid=3579 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg=‘op=PAM:setcred grantors=pam_wheel,pam_faillock,pam_faillock,pam_permit,pam_permit,pam_ecryptfs,pam_cap acct=“root” exe=“/usr/bin/python3.13” hostname=? addr=? terminal=? res=success’
[ 32.837817] audit: type=1105 audit(1777247280.501:300): pid=3579 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg=‘op=PAM:session_open grantors=pam_permit,pam_umask,pam_unix,pam_umask,pam_tmpdir,pam_ecryptfs acct=“root” exe=“/usr/bin/python3.13” hostname=? addr=? terminal=? res=success’
[ 32.843436] audit: type=1106 audit(1777247280.509:301): pid=3579 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg=‘op=PAM:session_close grantors=pam_permit,pam_umask,pam_unix,pam_umask,pam_tmpdir,pam_ecryptfs acct=“root” exe=“/usr/bin/python3.13” hostname=? addr=? terminal=? res=success’
[ 32.843498] audit: type=1104 audit(1777247280.509:302): pid=3579 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg=‘op=PAM:setcred grantors=pam_wheel,pam_faillock,pam_faillock,pam_permit,pam_permit,pam_ecryptfs acct=“root” exe=“/usr/bin/python3.13” hostname=? addr=? terminal=? res=success’
[ 50.285266] audit: type=1110 audit(1777247336.907:341): pid=4670 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg=‘op=PAM:setcred grantors=pam_wheel,pam_faillock,pam_faillock,pam_permit,pam_permit,pam_ecryptfs,pam_cap acct=“root” exe=“/usr/bin/python3.13” hostname=? addr=? terminal=? res=success’
[ 50.287911] audit: type=1105 audit(1777247336.911:342): pid=4670 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg=‘op=PAM:session_open grantors=pam_permit,pam_umask,pam_unix,pam_umask,pam_tmpdir,pam_ecryptfs acct=“root” exe=“/usr/bin/python3.13” hostname=? addr=? terminal=? res=success’
[ 50.874117] audit: type=1106 audit(1777247337.495:344): pid=4670 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg=‘op=PAM:session_close grantors=pam_permit,pam_umask,pam_unix,pam_umask,pam_tmpdir,pam_ecryptfs acct=“root” exe=“/usr/bin/python3.13” hostname=? addr=? terminal=? res=success’
[ 50.874337] audit: type=1104 audit(1777247337.495:345): pid=4670 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg=‘op=PAM:setcred grantors=pam_wheel,pam_faillock,pam_faillock,pam_permit,pam_permit,pam_ecryptfs acct=“root” exe=“/usr/bin/python3.13” hostname=? addr=? terminal=? res=success’
[ 64.689608] audit: type=1110 audit(1777247351.311:352): pid=4810 uid=1000 auid=1000 ses=2 subj=unconfined msg=‘op=PAM:setcred grantors=pam_wheel,pam_faillock,pam_faillock,pam_permit,pam_permit,pam_ecryptfs,pam_cap acct=“root” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/0 res=success’
[ 64.696641] audit: type=1105 audit(1777247351.319:353): pid=4810 uid=1000 auid=1000 ses=2 subj=unconfined msg=‘op=PAM:session_open grantors=pam_limits,pam_permit,pam_umask,pam_unix,pam_umask,pam_tmpdir,pam_ecryptfs acct=“root” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/0 res=success’
[ 66.062425] audit: type=1106 audit(1777247352.683:354): pid=4810 uid=1000 auid=1000 ses=2 subj=unconfined msg=‘op=PAM:session_close grantors=pam_limits,pam_permit,pam_umask,pam_unix,pam_umask,pam_tmpdir,pam_ecryptfs acct=“root” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/0 res=success’
[ 66.062557] audit: type=1104 audit(1777247352.683:355): pid=4810 uid=1000 auid=1000 ses=2 subj=unconfined msg=‘op=PAM:setcred grantors=pam_wheel,pam_faillock,pam_faillock,pam_permit,pam_permit,pam_ecryptfs acct=“root” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/0 res=success’
[ 78.707277] audit: type=1110 audit(1777247365.331:358): pid=4843 uid=1000 auid=1000 ses=2 subj=unconfined msg=‘op=PAM:setcred grantors=pam_wheel,pam_faillock,pam_faillock,pam_permit,pam_permit,pam_ecryptfs,pam_cap acct=“root” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/0 res=success’
[ 78.714478] audit: type=1105 audit(1777247365.335:359): pid=4843 uid=1000 auid=1000 ses=2 subj=unconfined msg=‘op=PAM:session_open grantors=pam_limits,pam_permit,pam_umask,pam_unix,pam_umask,pam_tmpdir,pam_ecryptfs acct=“root” exe=“/usr/bin/sudo” hostname=? addr=? terminal=/dev/pts/0 res=success’

Hmm, none of those look particularly useful, they’re talking about PAM modules.

To my awareness, this doesn’t occur on vanilla Debian 13, so it’s possible that distribution-morphing LMDE to Kicksecure simply doesn’t work. You might consider switching to vanilla Debian 13 with the Cinnamon desktop environment, then installing kicksecure-baremetal-cli on top of that. Or, alternatively, consider using the Kicksecure ISO directly.

1 Like

Alright, thanks for your help.

1 Like