Sync Updates for Week 26, 2024

woah, distrobox finally made it in!

SethStorm666 I got an apparmor service failed loading profile on Gnome when starting Solus up. But I can't seems to find it in the logs.

On a fully updated system using the Stable/Default repository?

Same here, apparmor service failed on start up with plasma/stable repo

Staudey

Aye, on stable.

116 packages. did not get apparmor fail message on Budgie...if that's useful for troubleshooting.

elfprince Love this!

xed indistinguishable from gedit whenever I've used it.
the xviewer and xreaders I've used and they were mega-light, not sure they have the features of the budgie defaults we have now but it's been a while. they probably are. Love the deprecations and defualts being re-thought though.

EbonJaeger Our linux-firmware is now compressed using zstd. This should save around 400-500MB on end user systems.

nice.

Apparmor service failed, apparmor.systemd[594]: Error: Unable to find AppArmor initscript functions

But at least Element works now under Wayland, so I'm happy with this update. Keep up the good work.

apparmor fails to start

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

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.

Dudel
sudo eopkg rdb

VTMarik I just replace everything unavailable with flatpaks at this point