Page 1 of 1

libMagickWand-6.Q16HDRI.so.1 is called for but only libMagickWand-6.Q16HDRI.so.2 exists

Posted: 2014-11-14T22:19:50-07:00
by rcrath
running up to date manjaro system (arch based)
imagemagick 6.8.9.8-1
Have an error in the journal saying

Code: Select all

 libMagickWand-6.Q16HDRI.so.1: cannot open shared object file: No such file or directory
when I look at installed files it says that the library installed is libMagickWand-6.Q16HDRI.so.2. rather than so.1.
THis happened in the context of running blueman, which has imagemagick as a dependency.
Is this a problem for imagemagick? Blueman? or the manjaro / arch package maintainers (if that, which package?)

Let me know if more info needed.

EDIT: is this maybe a problem with obex-data-server rather than imagemagick? (see logs below)
THanks.

libMagickWand-6.Q16HDRI.so.1 is called for but only libMagickWand-6.Q16HDRI.so.2 exists

Posted: 2014-11-14T22:22:23-07:00
by rcrath
one more thing....here are the complete lines (three of them) from journalctl:

Code: Select all

Nov 02 22:45:57 zamanjaro org.gnome.Terminal[10692]: ** (gnome-terminal-server:3182): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 02 23:37:27 zamanjaro org.openobex[10692]: /usr/bin/obex-data-server: error while loading shared libraries: libMagickWand-6.Q16HDRI.so.1: cannot open shared object file: No such file or directory
Nov 02 23:41:14 zamanjaro org.blueman.Applet[10692]: ** (blueman-applet:10525): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

SOLVED: Re: libMagickWand-6.Q16HDRI.so.1 is called for but only libMagickWand-6.Q16HDRI.so.2 exists

Posted: 2014-11-25T16:13:54-07:00
by rcrath
solved by updating obex-data-server to 4.6.10.