I did some searching in the OS forums and found this post- https://bbs.archlinux.org/viewtopic.php?id=311058 which suggests the fix requires adding kernel boot options to enable a bunch of options for “lsm”
I went through the process of altering the kernel load options in /etc/default/grub adding-
However (after a reboot) this has no effect. I’m guessing that the lsm module is not actually loaded in the kernel, so passing the options has no effect.
Is there a good “recipe” out there on how to go about this, because i’m kinda wandering around in the dark on this and concerned about breaking something and making my system unbootable.
This seems like a lot of hard work to get a single application to run. Is this something the pacseek installer from AUR could+should do? or at least should there be a README that walks a non-expert user through how to set up the system to allow pacseek to run?
Seems like it. I don’t know anything about the kernel parameters you are using. I do know that i have updated pacseek a few times lately because of some other package issues that have been going on but haven’t had any issues. Someone with more experience with lsm and these security protocols you are attempting to use will have to give some help.
just fyi EOS comes with a checkrebuild command line utility. Some programs will almost always flag (zoom, proton-GE) but still work, so I just keep any eye on anything that isn’t those post-update. I have this alias in my env too alias rebuild="yay -S --rebuildall "which i find nice to have.
One of these days I’m going to modify the update script to do mirrors first and then checkrebuild after, I have a lot of mirrors issues with a poor ISP in this new apartment, and having a post-update report on what might need rebuilding would just be nice.
Yes, I installed pacseek from AUR and it’s been running pretty reliably for several months. It’s just some updates in the last 3-4 weeks that seem to have caused problems.
The first problem, a version dependency on libalpm v15, was fixed when the package was updated to v1.8.5-2
That at least got the program to run, but now it runs into this kernel function dependency issue.
What’s weird is- If I start pacseek in “update” mode as pacseek -u it fails with the error, but I have since realised that if I run plain pacseek and then use the cntrl-Uupdate command, that works ok.
