Closed (fixed)
Project:
ImageMagick
Version:
8.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
1 Nov 2016 at 18:44 UTC
Updated:
18 Nov 2016 at 15:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mondrakeHi @kevin671
besides the error message, does the toolkit work? Asking because I've seen other cases where even if the return code of the op sys execution of the ImageMagick command is not zero, there are no evident error messages and the command is actually executed ok.
Does the 'VERSION INFORMATION' box report the ImageMagick version details?
Any more info in the dblog?
You may also want to enable debugging, see #2078943-3: Occasional User error: ImageMagick error 9: No error message, and report back the output you'll get in the dblog.
Comment #3
earelin commentedI have the same message on the log. I have added the -debug All option but no errors are reported. Also I am not able to load the edit style page, the browser is waiting webserver response that does not come. I have check the webserver log and I have no errors, also there are no server load when you try to load the edit style page. I will try to trace what is happening.
Regards,
Xavier
Comment #4
mondrakeAre you running on Windows?
There are a couple of issues there, that are solved in the 8.x-2.x branch but still need to be ported to the 8.x-1.x branch:
#2761205: Unable to configure path for Windows
#2779981: identify() has problems on Windows
Comment #5
earelin commentedThe error in the image styles is related to memcache module. But I am geting that "ImageMagick error 1: No error message." log entry.
Comment #6
mondrakeBut is the toolkit functional? I am also getting that log entry with ImageMagick 6.8.9-9, but only when I open the toolkit configuration form, as a result of running 'convert -list format', but I have no side effects - images get identified and converted correctly.
Comment #7
earelin commentedThe toolkit looks OK.
Comment #8
mondrakeThanks for feedback @earelin.
I start thinking that to avoid confusing messages, we should refrain from logging entries where there is no error message returned from the execution of convert/identify. Or at least log as warning, adding a flag in the configuration screen if we want that. Currently, any time the return code from the execution of convert/identify is different from 0, an entry is logged. That seems too much.
Comment #9
mondrakeComment #10
mondrakeSomething like this (no config option yet)
Comment #11
mondrakeComment #14
mondrakeSo let's do #10 for now, this will help to sort out bug reports between 'errors' (when we have a material error message from ImageMagick) and 'warnings' (when we have a non-zero return code but no error message).
Comment #15
mondrake