Bug 152909 - Batch operation "resize" fails saying convert cannot be started correctly
Summary: Batch operation "resize" fails saying convert cannot be started correctly
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Bqm-Resize (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-26 09:07 UTC by krienke
Modified: 2017-07-01 11:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description krienke 2007-11-26 09:07:43 UTC
Version:           0.1.5-beta1 (using KDE KDE 3.5.8)
Installed from:    SuSE RPMs
Compiler:          4.2.1 
OS:                Linux

I am runnign openSuSE 10.3 with digikam 0.9.3 beta3 and kipi-plugins 0.1.5 beta1 (compiled from tar-file). 

Trying to batch resize one or more photos from a resolution of about 3400x5800 to a resolution of x*3000 only specifying one proportion (3000) with resize option cubic (make no difference if I try another option here) I get the error message that convert could not be started. The photo is not resized. The messagebox says:
"Cannot run properly 'convert' program from 'ImageMagick' package"

Running strace I can see that actually convert is called  like this: /opt/kde3/bin/convert -resize 1937x3000 -quality 80 -verbose Image100.jpg

Running this command maually this works fine. 

Initially convert could not be found since it was searched only in /opt/kde3/bin and on my system it is in /usr/bin . Perhaps this is due to the fact that I called configure using --prefix=/opt/kde3/bin when compiling kipi-plugins. Next I places a symbolic ling in /opt/kde3/bin that points to /usr/bin/convert and this leads to the error just described.

There is no debug output to stderr or stdout (compiled using --enable-debug=full).
Comment 1 krienke 2007-11-27 14:27:55 UTC
In between I tried kipiplugins from svn. Here this bug has been fixed already.