Sync Updates for Week 26, 2024

kde

I stand corrected:

 $ systemctl status apparmor
[sudo] password for brent:
× apparmor.service - Load AppArmor profiles
     Loaded: loaded (/usr/lib/systemd/system/apparmor.service; disabled; preset: enabled)
    Drop-In: /usr/lib64/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Fri 2024-06-28 13:22:11 MST; 1h 19min ago
    Process: 415 ExecStart=/usr/lib64/apparmor/apparmor.systemd reload (code=exited, status=1/FAILURE)
   Main PID: 415 (code=exited, status=1/FAILURE)
        CPU: 6ms

Jun 28 13:22:11 workstation apparmor.systemd[415]: Error: Unable to find AppArmor initscript functions
Jun 28 13:22:11 workstation systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE
Jun 28 13:22:11 workstation systemd[1]: apparmor.service: Failed with result 'exit-code'.
Jun 28 13:22:11 workstation systemd[1]: Failed to start apparmor.service - Load AppArmor profiles.

my service failed too

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.

sangheeta Stable with Budgie here, same issue.

[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).

Cherry-picked a fix for the apparmor service not starting.

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.

VTMarik I just replace everything unavailable with flatpaks at this point

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 ?

CorvusRuber The fix should be cherry-picked. My eopkg didn't find new packages, so I just got it from https://packages.getsol.us/shannon/a/apparmor/apparmor-3.1.7-32-1-x86_64.eopkg

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

[deleted]
Needed to re-index shannon. Thanks for reporting the issue.

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

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

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.