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)
*** This bug has been marked as a duplicate of bug 351433 ***
Please *look for duplicate* before posting a new bug report: This is *very* important, and reminded each time you post a bug report. Since you report bugs quite often (and we thank you for that), you should be well aware on how it works by now. If you choose to ignore that, then we will just spend more time triaging bugs and less time fixing them! At this point, you have three solutions: - Downgrade Hugin, as writen in the original bugreport - Wait (my time is highly limited at the moment, and we are well aware of the issue, as you can see in the original bug report) - Dive into the code and fix it yourself
Fixed with #bug 351433