Another apparmor service failed on start up with plasma/stable repo.
I tried sudo usysconf run -f which showed all actions as success but after another reboot I am still seeing apparmor service failed.
sudo journalctl -u apparmor Returned a long list with this entry at the bottom.
Jun 28 22:20:40 dell-solus apparmor.systemd[490]: Error: Unable to find AppArmor initscript functions

Any hints on the next step would be gratefully received. Thanks

    Update went super smooth, sad to see Kitematic go though. Just gotta find an alternative I suppose.

      BuzzPCSOS Similar here:
      juin 28 23:56:00 mbp-solus apparmor.systemd[490]: Error: Unable to find AppArmor initscript functions

        [deleted] Probably some combination of the minor mesa update (24.1.1 -> 24.1.2) or the rebuild of element with nodejs 20 (less likely but you never know).

          System error. Program terminated.
          (-30973, 'BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery -- BDB0061 PANIC: Invalid argument')
          Please use 'eopkg help' for general help.
          Use --debug to see a traceback.
          Error in atexit._run_exitfuncs:
          Traceback (most recent call last):
          File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
          func(targs, **kargs)
          File "/usr/lib/python2.7/site-packages/pisi/init.py", line 75, in _cleanup
          filesdb.close()
          File "/usr/lib/python2.7/site-packages/pisi/db/filesdb.py", line 94, in close
          self.filesdb.close()
          File "/usr/lib/python2.7/shelve.py", line 146, in close
          self.sync()
          File "/usr/lib/python2.7/shelve.py", line 173, in sync
          self.dict.sync()
          File "/usr/lib/python2.7/bsddb/init.py", line 347, in sync
          return DeadlockWrap(self.db.sync)
          File "/usr/lib/python2.7/bsddb/dbutils.py", line 68, in DeadlockWrap
          return function(          args, **_kwargs)
          DBRunRecoveryError: (-30973, 'BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery -- BDB0060 PANIC: fatal region error detected; run recovery')
          Error in sys.exitfunc:
          No handlers could be found for logger "pisi"
          System error. Program terminated.
          (-30973, 'BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery -- BDB0060 PANIC: fatal region error detected; run recovery')
          Please use 'eopkg help' for general help.
          Use --debug to see a traceback.

            ReillyBrogan

            Apparmor keeps failing for me, I think the relevant error is this:
            giu 29 07:45:21 corvus-framework apparmor.systemd[35074]: Error: Unable to find AppArmor initscript functions
            Do I need to do something on my part or simply wait for the fix ?

                Hello Everyone,

                Apparmor failed for me too, fixed it when i've uninstall and reinstall it in the software center. no issue after reboot.

                Maybe it can help 🙂

                  After Apparmor cherry picked and re-indexed everything is working very well again. Thank you for your speedy and efficient support.

                  • [deleted]

                  • Post #29

                  Qlayton Most likely you managed to reinstall it just after the fix got available in Shannon.

                    No issues with Plasma after updating.

                    Excited to see Distrobox included so installed it without issues and tried creating one and following error ensued, i did also --image for Fedora 40 and debian from quay and same error. And i don´t know how to proceed or solve this. Let me know if i should create a gh issue with this.

                    pjol@mini-solus ~ $ distrobox create
                    Image registry.fedoraproject.org/fedora-toolbox:39 not found.
                    Do you want to pull the image now? [Y/n]: y
                    Trying to pull registry.fedoraproject.org/fedora-toolbox:39...
                    Getting image source signatures
                    Copying blob 6b90564301bf done |
                    Error: copying system image from manifest list: writing blob: adding layer with blob "sha256:6b90564301bfa1966564eeab4ad3c3031f6408d75c4a8de4126efcaf7e35ca60": processing tar file(potentially insufficient UIDs or GIDs available in user namespace (requested 0:114 for /usr/share/polkit-1/rules.d): Check /etc/subuid and /etc/subgid if configured locally and run "podman system migrate": lchown /usr/share/polkit-1/rules.d: invalid argument): exit status 1
                    pjol@mini-solus ~ $

                    Doing as suggested, podman system migrate does not resolve the issue or give me any error or further message as to what might be going wrong. Also afaict neither /etc/subuid or /etc/subgid exist.

                      Pjol Read this forum thread . It is not as straightforward to use it because Solus doesn't create subgid and subuid file automatically. There is a pending PR for it.

                      • Pjol replied to this.

                          alfisya I have a recollection of reading that thread previously when i looked into Distrobox but i never proceeded with installing it at that time. But now that it is included in the repo i imagined it would be a matter of eopkg it distrobox and off i go.

                          Well this might serve as a good reminder if anyone else stumbles into the same issue.

                          Thanks!