LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   ImageMagick > Gwenview > digiKam (https://www.linuxquestions.org/questions/slackware-14/imagemagick-gwenview-digikam-4175601924/)

cwizardone 03-16-2017 11:34 AM

ImageMagick > Gwenview > digiKam
 
Recently I've noticed Gwenview cannot find the kipiplugins which are now part of digiKam, so I re-installed digiKam, but no luck.
So, I ran Gwenview from inside a terminal and when exiting the program it gave a series of errors that said it cannot find each plugin, for example,

Quote:

gwenview(11323) Gwenview::KIPIInterface::loadOnePlugin: Plugin from library "kipiplugin_expoblending" failed to load
gwenview(11323)/KIPI (loading) KIPI::PluginLoader::Info::plugin: Cannot create instance for plugin "RawConverter" ( "kipiplugin_rawconverter" ) with error: "Cannot load library /usr/lib64/kde4/kipiplugin_rawconverter.so: (libMagick++-6.Q16.so.6: cannot open shared object file: No such file or directory)"
So, I tried to run digiKam and the following error was generated,

Quote:

bash-4.4$ digikam
digikam: error while loading shared libraries: libMagick++-6.Q16.so.6: cannot open shared object file: No such file or directory
bash-4.4$
As mentioned, this was after re-installing fresh copies of each program, inclucing ImageMagick.
Any suggestions on how to fix this problem would be greatly appreciated.
Thanks.
:hattip:

montagdude 03-16-2017 11:49 AM

Did you check on your system to make sure libMagick++-6.Q16.so.6 actually exists and is a valid symlink to libMagick++-6.Q16.so.6.0.0? If so, did you make sure you installed the right package for your architecture? It should be in /usr/lib64 for x86_64, for example.

willysr 03-16-2017 08:39 PM

If you are running -current, when imagemagick gets a shared library bumped, you will need to rebuild digiKam to look for the correct library.

cwizardone 03-17-2017 03:39 AM

montagdude,
As willysr pointed out (Thank you, willysr), ImageMagick has had a version bump in -current, so it has "6.Q16.so.7", not "6.Q16.so.6."
As I only install digiKam to get the kipi-plugins, I re-installed a older version of ImageMagick and that took care of the problem.
Thank you for pointing me in the right direction.
:hattip:

willysr 03-17-2017 04:54 AM

I would recommend to rebuilt digiKam instead of downgrading imagemagick, since other packages are being rebuilt against newer imagemagick

montagdude 03-17-2017 06:47 AM

Quote:

Originally Posted by cwizardone (Post 5684639)
montagdude,
As willysr pointed out (Thank you, willysr), ImageMagick has had a version bump in -current, so it has "6.Q16.so.7", not "6.Q16.so.6."
As I only install digiKam to get the kipiplugins, I re-installed a older version of ImageMagick and that took care of the problem.
Thank you for pointing me in the right direction.
:hattip:

Glad I could be somewhat of help. I didn't realize you were running -current.

cwizardone 03-17-2017 06:24 PM

Quote:

Originally Posted by willysr (Post 5684664)
I would recommend to rebuilt digiKam instead of downgrading imagemagick, since other packages are being rebuilt against newer imagemagick

Just tried that, three times, and each time it ended in an "unknown error" at the "plug-in_videoslideshow.moc."

willysr 03-17-2017 07:14 PM

since current now includes ffmpeg, if you have ffmpeg from SBo previously, it would be better to rebuilt ffmpeg, opencv, and then digikam in that order. That will link ffmpeg to the correct deps in your system, opencv will link to the correct ffmpeg, and digiKam will use the correct ffmpeg and opencv.

cwizardone 04-09-2017 03:20 PM

With the recent version bumps the same problem with Gwenview has returned, but this time also includes jasper.
Perhaps, it would just be easier to rebuild Gwenview?
:scratch:


All times are GMT -5. The time now is 01:55 AM.