[Digikam-devel] [digikam] [Bug 353131] New: HUGIN error "pto2mk" mising with digiKam 13.0 AND "component information" lacks information of HUGIN's components

Axel Krebs axel.krebs at t-online.de
Thu Sep 24 12:21:14 BST 2015


https://bugs.kde.org/show_bug.cgi?id=353131

            Bug ID: 353131
           Summary: HUGIN error "pto2mk" mising with digiKam 13.0    AND
                    "component information" lacks information of HUGIN's
                    components
           Product: digikam
           Version: 4.13.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Workflow
          Assignee: digikam-devel at kde.org
          Reporter: axel.krebs at t-online.de

When trying to panorama stich some pics, I get the (error) message the
(HUGIN-)component "pto2mk" was missing.

If following the named link
<http://hugin.sourceforge.net/tutorials/overview/en.shtml> I can _not_ find the
the module "pto2mk" . Therefore, re-(in-)stall is not possible to overcome this
fault.

Under <http://wiki.panotools.org/Pto2mk> is information indicating that
"pto2mk" is replaced by "hugin-executor" with HUGIN newer than 2014 . 

CITATION:
>> Information: pto2mk is only available up to Hugin 2014.0. In later versions it has be replaced by hugin_executor, which provides more features. <<



Reproducible: Always

Steps to Reproduce:
1. start HUGIN
2. start to process the panorama workflow
3. in overview, the module "pto2mk" is crossed out in red as missing 

Actual Results:  
I can _not_ process panoramas, which is a serious malfunction because of
apparently missing module "pto2mk".

Expected Results:  
1.) user should be able to see HUGIN's actual components as other components in
components (version) information. Only then a users can see immediately the
installed modules (respective versions) 

2.) supposing my installed digiKam version is quite new, there is no visible
change away _from_ "pto2mk" _to_ "hugin_executor". 

ASSUMPTION: there could be a misfit between the versions of digiKam and HUGIN.

(maybe this is the whole problem right here)

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Digikam-devel mailing list