Re: Plasma-Workspace Missing Klipper Module (not a separate module- hardcoded)
Reply #3 –
Library not found breaks after an update recovery procedures:
The safest way is to not update until all the packages that are installed on one's system are ready at the same level at the time of the update.
1) If the library update break did occur then manually install the older version with:
# pacman -U </var/cache/pacman/pkg/${package name-previous version}.zst
The Artix repositories will all be synchronized with the new version of the libraries over time. Usually it does not take too long and one can then update normally again.
2) If you cannot wait:
There many ways to go about this. Beware you are now in total control and can make big mistakes if your knowledge is lacking. Be sure to check out the documentation on pacman, makepkg first. One has to know their tools before use to prevent injury to one's system or yourself or both when nothing works.
The simplest way to update a package is to just download the PKGBUILD (plus any extra files in the package) then run:
$ cd ${download folder containing the PKGBUILD (+files if they exist) location}
$ ${editor of choice} PKGBUILD
$ makepkg -i
Always check and verify the PKGBUILD file first before running "makepkg -i". If any other files are present it is a good idea to check them as well.
The package will build and install as a local package.
One can use an AUR helper (many flavours exist). Pick one that allows rebuilding of all packages not just the AUR packages. It is important to be sure to check/verify the PKGBUILD file and any associated files yourself during the process. Note that AUR helpers are not supported by either Artix nor Arch. Well AUR is not supported either so it is all the same.
An advanced way would be to create your own repository for holding your custom packages. The Arch wiki describes how to create a local file repository and how to sign the packages if you want to guarantee that the package has not be modified since the build due to some corruption or malice. One would then list it as their first repository in /etc/pacman.conf so that your custom packages are used by default.
When one builds packages locally and uses then you are in total control and can modify it's PKGBUILD for any custom requirements if you want.
Once the application has been updated/rebuilt and linked with the new version of the library then installed, those running failures of not finding the library will vanish after the update of the system.
Topic: Plasma-Workspace Missing Klipper Module (not a separate module- hardcoded) (Read 921 times)
previous topic - next topic
