SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Are libmypaint and mypaint-brushes really bound to xorg or of a such general use for graphic applications, explaining why they are in x/? The Changelog says they were introduced as GIMP dependencies, therefore they would IMHO be in a better place in l/.
From yesterday's update, okular cannot open a pdf:
Invalid plugin factory for "/usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so"
That poppler generator is part of the okular package. How can that plugin factory be invalid?
=-==--=-=
okular-git does not generate such errors.
From yesterday's update, okular cannot open a pdf:
Invalid plugin factory for "/usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so"
That poppler generator is part of the okular package. How can that plugin factory be invalid?
I was able to reproduce by removing the poppler package
Code:
Package: poppler-21.05.0-x86_64-1
Removing...
Removing package: poppler-21.05.0-x86_64-1
15step :: ~ » cd Documents
15step :: ~/Documents » okular 11527.pdf
org.kde.okular.core: Invalid plugin factory for "/usr/lib64/qt5/plugins/okular/generators
/okularGenerator_poppler.so":"Impossible de charger la bibliothèque
/usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so*:
(libpoppler-qt5.so.1: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type)"
From yesterday's update, okular cannot open a pdf:
Invalid plugin factory for "/usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so"
That poppler generator is part of the okular package. How can that plugin factory be invalid?
=-==--=-=
okular-git does not generate such errors.
Do you have Eric's latest poppler-compat installed? Latest Okular works fine here.
15step :: ~/Documents » okular 11527.pdf
org.kde.okular.core: Invalid plugin factory for "/usr/lib64/qt5/plugins/okular/generators
/okularGenerator_poppler.so":"Impossible de charger la bibliothèque
/usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so*:
(libpoppler-qt5.so.1: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type)"
After the May 12 update to mousepad-0.5.5, it runs but produces this warning:
Code:
(mousepad:29323): Mousepad-WARNING **: 14:05:31.737: Failed to open plugin directory '/usr/lib64/mousepad/plugins': Error opening directory “/usr/lib64/mousepad/plugins”: No such file or directory
Creating an empty directory with that name stops the warning, but I think something is supposed to go in there from the 0.5.5 release.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.