[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).
Sync Updates for Week 26, 2024
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.
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 ?
[deleted]
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
After Apparmor cherry picked and re-indexed everything is working very well again. Thank you for your speedy and efficient support.
[deleted]
Qlayton Most likely you managed to reinstall it just after the fix got available in Shannon.
- Edited
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.
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!
Appamor fixed now, thanks guys!
- Edited
Hello. Thank you for this huge update and fixing AppArmor issue few hours ago but still have problem with sound. When I check on Setting > Sound, the Output Device is "Dummy Output". Reinstall sof-firmware
still not working for me.
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: active (exited) since Sat 2024-06-29 06:55:49 MST; 2min 6s ago
Process: 414 ExecStart=/usr/lib64/apparmor/apparmor.systemd reload (code=exited, status=0/SUCCE>
Main PID: 414 (code=exited, status=0/SUCCESS)
CPU: 259ms
Jun 29 06:55:57 workstation apparmor.systemd[414]: Restarting AppArmor
Jun 29 06:55:57 workstation apparmor.systemd[414]: Reloading AppArmor profiles
Jun 29 06:55:49 workstation systemd[1]: Finished apparmor.service - Load AppArmor profiles.
Got the new update. It's loaded/active. All better now. Thank you. οΈ
Apparmor update a day latter addressed fail to start problem.
just updated, rebooted, and my wifi and bluetooth are gone. no option to connect to any wireless networks.
also mailspring is gone? a shame, i used and liked that one.
linux-firmware, sof-firmware, and iptables cherry-picked to fix an issue caused by moving files from /lib64/
to /usr/lib64
(in preparation for the upcoming usr-merge) where not all compat symlinks were created. This would cause issues where certain hardware would fail to load the proper firmware files, breaking graphics, wifi/bluetooth, sound, and other devices.
topolojack just updated, rebooted, and my wifi and bluetooth are gone. no option to connect to any wireless networks.
Your issue is most likely resolved by the cherry-picks. Hopefully you can use an ethernet port to update, but if not you can download this file from another device and then put it on a USB or something and install it with sudo eopkg it /path/to/file
topolojack also mailspring is gone? a shame, i used and liked that one.
Mailspring developers are frankly incompetent from a security standpoint. They statically build various libraries into the sync binary that they distribute themselves and there is no way for packagers to override it to use system libraries. If you are using mailspring, you are using a version of OpenSSL that is more than 7 years old (!!!) at this point which I have brought to their attention and they simply do not care about it or your security. We cannot in good conscious allow software with such bad security practices to exist in our package repo. If you personally do not care about using insecure software you can use the flatpak though I would note that I am shortly going to open an issue with Flathub admins to investigate whether or not it should be removed there as well.